Some Assembly Required
-
Ok this is very strange. I had an application I wrote for a client and compiled it on my machine and it would run just fine. When the client would try the program the application would crash immeaditly. I added error traps all over the place in order to trap this elusive error, no luck, It still crashed! Used the ILDASM tool to see what the Manifest of the application uses and behold it uses an old version of a critical dll. So, I check gakutil and only the most recent versions of the dll are in the cache. I scan my system for the old dll and can't find anything. Decide to burn one of my support instances and the Microsoft Guy is at a loss.* I create 2 new virtual machines with clean versions of XP / Office and all the Patches etc.
- I install VS 2005 on one of them.
- I copy the old exe to the new test virtual machine and click on it. Boom. It crashes imeaditly.
- Next, I copy the source code to the machine with VS 2005 on it and don't change the code in anyway and just recompile it.
- The new EXE runs on the virtual development machine.
- I copy the EXE to the virtual test machine and it works there too.
- Getting excited, I copy it to my physical machine and it works!
The moral of the story is, keep your dev machine very clean and don't install anything new on it. Now I need to rebuild my physical machine or just do all development in the virtual machine. Matthew Hazlett Sometimes I miss the simpler DOS days of Borland Turbo Pascal (but not very often).
-
Ok this is very strange. I had an application I wrote for a client and compiled it on my machine and it would run just fine. When the client would try the program the application would crash immeaditly. I added error traps all over the place in order to trap this elusive error, no luck, It still crashed! Used the ILDASM tool to see what the Manifest of the application uses and behold it uses an old version of a critical dll. So, I check gakutil and only the most recent versions of the dll are in the cache. I scan my system for the old dll and can't find anything. Decide to burn one of my support instances and the Microsoft Guy is at a loss.* I create 2 new virtual machines with clean versions of XP / Office and all the Patches etc.
- I install VS 2005 on one of them.
- I copy the old exe to the new test virtual machine and click on it. Boom. It crashes imeaditly.
- Next, I copy the source code to the machine with VS 2005 on it and don't change the code in anyway and just recompile it.
- The new EXE runs on the virtual development machine.
- I copy the EXE to the virtual test machine and it works there too.
- Getting excited, I copy it to my physical machine and it works!
The moral of the story is, keep your dev machine very clean and don't install anything new on it. Now I need to rebuild my physical machine or just do all development in the virtual machine. Matthew Hazlett Sometimes I miss the simpler DOS days of Borland Turbo Pascal (but not very often).
-
Ok this is very strange. I had an application I wrote for a client and compiled it on my machine and it would run just fine. When the client would try the program the application would crash immeaditly. I added error traps all over the place in order to trap this elusive error, no luck, It still crashed! Used the ILDASM tool to see what the Manifest of the application uses and behold it uses an old version of a critical dll. So, I check gakutil and only the most recent versions of the dll are in the cache. I scan my system for the old dll and can't find anything. Decide to burn one of my support instances and the Microsoft Guy is at a loss.* I create 2 new virtual machines with clean versions of XP / Office and all the Patches etc.
- I install VS 2005 on one of them.
- I copy the old exe to the new test virtual machine and click on it. Boom. It crashes imeaditly.
- Next, I copy the source code to the machine with VS 2005 on it and don't change the code in anyway and just recompile it.
- The new EXE runs on the virtual development machine.
- I copy the EXE to the virtual test machine and it works there too.
- Getting excited, I copy it to my physical machine and it works!
The moral of the story is, keep your dev machine very clean and don't install anything new on it. Now I need to rebuild my physical machine or just do all development in the virtual machine. Matthew Hazlett Sometimes I miss the simpler DOS days of Borland Turbo Pascal (but not very often).
If I had a powerful enough machine I would always do my dev on a virtual machine. I've run into similar problems in the past and also into problems where I had knowingly changed a dll/setting one day in order to get some non-dev related app running and then the next day run into an dev, spend hours tearing my hair out (ask Paul - I'm nearly bald) and just not make the connection between the two actions. Keeping a clean dev machine can save a lot of headaches. Regards, Brian Dela :-) Blog^ Co-author of The Outlook Answer Book... Go on, order^ it today!