Moving my project from VS 2003 to VS 2005
-
Hello there Until today, I have been using VS 2003 / VC ++ without any problems for several years Installed VS 2005 on my WinXP-SP2 machine (left all the default folders as suggested), then applied SP1 of VS 2005 without any problems… Then, converted my project to the new IDE using the wizard – no errors or any messages, seemed all OK: BUT 1) Decided first to build an ANSI RELEASE version, all seemed OK except the application looks wrong, the tree control fails to create, the dialog background colouring is NOT there, all the buttons on my dialog do NOT process any messages, so to quit the screen I had to use ALT + F4, nothing else would work. 2) Attempting to build and debug an ANSI DEBUG version of my program, it seems the IDE can’t locate the VC DEBUG DLL’s and I had to copy those into my application folder… Strange – I thought the IDE should “Know” where these are located… mfc80d.dll mfcm80d.dll msvcm80d.dll msvcp80d.dll msvcr80d.dll 3) Attempting to build a UNICODE DEBUG of my program, I get this error LINK : fatal error LNK1181: cannot open input file 'lsvc8u.lib' Searching for the file on my PC returns ZERO results, there is no such file on my machine, I did performed a complete install of VS 2005, and am not expecting anything to be missing… 4) On exiting my application, I get a crash with the message f:\sp\vctools...", I have no idea where is the “f:” drive designation coming from since I don’t have such a drive mapping on my PC Looking at the Call stack, I get a “Strange” list – which I am sure my Application DOES NOT execute, so I figure somwhere there must be a corruption of sorts for this to come up. Looking at the bottom of the list, Ther is a call to a function MKGetFaxDateandTime() which I am sure it is NOT called anywhere. Anyone has such experince??? Cheers Alex
-
Hello there Until today, I have been using VS 2003 / VC ++ without any problems for several years Installed VS 2005 on my WinXP-SP2 machine (left all the default folders as suggested), then applied SP1 of VS 2005 without any problems… Then, converted my project to the new IDE using the wizard – no errors or any messages, seemed all OK: BUT 1) Decided first to build an ANSI RELEASE version, all seemed OK except the application looks wrong, the tree control fails to create, the dialog background colouring is NOT there, all the buttons on my dialog do NOT process any messages, so to quit the screen I had to use ALT + F4, nothing else would work. 2) Attempting to build and debug an ANSI DEBUG version of my program, it seems the IDE can’t locate the VC DEBUG DLL’s and I had to copy those into my application folder… Strange – I thought the IDE should “Know” where these are located… mfc80d.dll mfcm80d.dll msvcm80d.dll msvcp80d.dll msvcr80d.dll 3) Attempting to build a UNICODE DEBUG of my program, I get this error LINK : fatal error LNK1181: cannot open input file 'lsvc8u.lib' Searching for the file on my PC returns ZERO results, there is no such file on my machine, I did performed a complete install of VS 2005, and am not expecting anything to be missing… 4) On exiting my application, I get a crash with the message f:\sp\vctools...", I have no idea where is the “f:” drive designation coming from since I don’t have such a drive mapping on my PC Looking at the Call stack, I get a “Strange” list – which I am sure my Application DOES NOT execute, so I figure somwhere there must be a corruption of sorts for this to come up. Looking at the bottom of the list, Ther is a call to a function MKGetFaxDateandTime() which I am sure it is NOT called anywhere. Anyone has such experince??? Cheers Alex
1. maybe a bug in the SP, my advise: try a VS Installation without the SP :suss: 2. you are right, I have solved this shocking behavoir with adding these dlls explicit to the manifest X| 3. the file is missing, -> 1. (User installation and activate all) 4. I thinks the guys at Microsoft have hardcoded these pathes, sometimes this happens This is the "normal" strange behaviour of the VS. Conclusion: Shit happens all over the world. :rolleyes:
Greetings from Germany
-
1. maybe a bug in the SP, my advise: try a VS Installation without the SP :suss: 2. you are right, I have solved this shocking behavoir with adding these dlls explicit to the manifest X| 3. the file is missing, -> 1. (User installation and activate all) 4. I thinks the guys at Microsoft have hardcoded these pathes, sometimes this happens This is the "normal" strange behaviour of the VS. Conclusion: Shit happens all over the world. :rolleyes:
Greetings from Germany
Hello there Germany Firstly, I had all this B4 loading SP1, I loaded it with the hope it will resolve the issues.... BUT, as you can see - it didn't! What do you mean by "User Installation" , where is that ? Is this during the install? If so, that will mean that I have to uninstall VS? Thanks for your feedback Alex from Down-Under / Australia
-
Hello there Germany Firstly, I had all this B4 loading SP1, I loaded it with the hope it will resolve the issues.... BUT, as you can see - it didn't! What do you mean by "User Installation" , where is that ? Is this during the install? If so, that will mean that I have to uninstall VS? Thanks for your feedback Alex from Down-Under / Australia
If the problem where before the SP, then it is another problem. 1. Your first point can of course be a bug in your code. Often helps if a collegue or mate looks at it. 2. I have added some lines in my manifest. Look in your Build directory there are some and you got to include the dll entries. I have done this so without the xml-Tags !!!: dependency dependentAssembly assemblyIdentity type='win32' name='Microsoft.VC80.DebugCRT' version='8.0.50727.42' processorArchitecture='x86' publicKeyToken='1fc8b3b9a1e18e3b' dependentAssembly the same for: assemblyIdentity type='win32' name='Microsoft.VC80.DebugMFC' version='8.0.50727.42' processorArchitecture='x86' publicKeyToken='1fc8b3b9a1e18e3b' IJW, I dont really understand it why I have to do it 3. A user reinstall "could" fix, look careful for all options to be activated 4. this seems to be a bug, -> 1. -- modified at 3:42 Friday 12th January, 2007
Greetings from Germany
-
If the problem where before the SP, then it is another problem. 1. Your first point can of course be a bug in your code. Often helps if a collegue or mate looks at it. 2. I have added some lines in my manifest. Look in your Build directory there are some and you got to include the dll entries. I have done this so without the xml-Tags !!!: dependency dependentAssembly assemblyIdentity type='win32' name='Microsoft.VC80.DebugCRT' version='8.0.50727.42' processorArchitecture='x86' publicKeyToken='1fc8b3b9a1e18e3b' dependentAssembly the same for: assemblyIdentity type='win32' name='Microsoft.VC80.DebugMFC' version='8.0.50727.42' processorArchitecture='x86' publicKeyToken='1fc8b3b9a1e18e3b' IJW, I dont really understand it why I have to do it 3. A user reinstall "could" fix, look careful for all options to be activated 4. this seems to be a bug, -> 1. -- modified at 3:42 Friday 12th January, 2007
Greetings from Germany
Hello again There seems to be a section missing in your response to me??? Please look in it and see Can you please email me directly to alex.evans@iinet.net.au 1) What you did, AND 2) Your manifest Much appreciated Alex
-
Hello there Until today, I have been using VS 2003 / VC ++ without any problems for several years Installed VS 2005 on my WinXP-SP2 machine (left all the default folders as suggested), then applied SP1 of VS 2005 without any problems… Then, converted my project to the new IDE using the wizard – no errors or any messages, seemed all OK: BUT 1) Decided first to build an ANSI RELEASE version, all seemed OK except the application looks wrong, the tree control fails to create, the dialog background colouring is NOT there, all the buttons on my dialog do NOT process any messages, so to quit the screen I had to use ALT + F4, nothing else would work. 2) Attempting to build and debug an ANSI DEBUG version of my program, it seems the IDE can’t locate the VC DEBUG DLL’s and I had to copy those into my application folder… Strange – I thought the IDE should “Know” where these are located… mfc80d.dll mfcm80d.dll msvcm80d.dll msvcp80d.dll msvcr80d.dll 3) Attempting to build a UNICODE DEBUG of my program, I get this error LINK : fatal error LNK1181: cannot open input file 'lsvc8u.lib' Searching for the file on my PC returns ZERO results, there is no such file on my machine, I did performed a complete install of VS 2005, and am not expecting anything to be missing… 4) On exiting my application, I get a crash with the message f:\sp\vctools...", I have no idea where is the “f:” drive designation coming from since I don’t have such a drive mapping on my PC Looking at the Call stack, I get a “Strange” list – which I am sure my Application DOES NOT execute, so I figure somwhere there must be a corruption of sorts for this to come up. Looking at the bottom of the list, Ther is a call to a function MKGetFaxDateandTime() which I am sure it is NOT called anywhere. Anyone has such experince??? Cheers Alex