Hmm. That's very curious. The reason for this error message was that VB6
could not find ANY copy of cvtres.exe -- I don't know how it could have
vanished. However, I copied the version I mentioned earlier from
....\VC98\Bin to ...\VB98, alongside Link.exe, and the error went away.
Unfortunately, it was replaced by a second error:
fatal error CVT1107: MyApp.obj is corrupt. However, the compiler and
linker appeared to have run with no errors. Could this be a bug in
either of THEM?
Re: Microsoft and trust ... If everytime someone posts to the wrong group due to the naming issue, they then take it upon themselves to use that as a soapbox for bashing .net, then it's reasonable for people who use and like both VB6 and VB7+ to speak up against that. ... If I know the answer I will post it: I'm not going to make the person go through un-necessary delays because some folks don't want to see it. ... |> Tried 2008 as well and just don't see any reason to convert. ... Why do we not give such warnings?... (microsoft.public.vb.general.discussion)
Re: VB.NET Discussion ... >Then I took a large, to me, VB6 project and let VB2005 do it's thing. ... That reason is that it is now far ... >> It would be extremely foolish to do so and akin to being deaf and ... >> walking down the railroad track assuming that, ... (microsoft.public.vb.general.discussion)
Re: Hows dot.net doing nowadays? ... There are things that VB6 will forever be better suited for than a .NET app.... why is it that 8 of 10 .Notters will quote something out of context so they can twist its meaning? ... If some one is moving to .NET, or if the reason some one changing ANY platform is simply because it's the fashionable thing to do for the week, then it's a bad decision. ... (microsoft.public.vb.general.discussion)
Re: VB.NET Discussion ... Then I took a large, to me, VB6 project and let VB2005 do it's thing. ... That reason is that it is now far ... >>recommend against upgrading to .Net unless there is a compelling reason ... >>that's not a problem with .Net, it is a problem with those programmers.... (microsoft.public.vb.general.discussion)
Re: Hows dot.net doing nowadays? ...VB6 is alive and well. ... Our app doesn't scale well. ... If some one is moving to .NET, or if the reason some one changing ANY ... (microsoft.public.vb.general.discussion)
