Does VBPro run *.exe files after building them, as a test?

[ChrisF]

I have a scenario happening in VBPro v7.2a that I can not reproduce when I do the same steps manually in Visual 2008.

I have a windows foo.exe dependent on bar.dll to run. I also generate a bar.lib file, and never delete the bar.lib file. foo.sln uses the bar.lib during compile time, and bar.dll during run time. (I did not set this up, and can't redo the setup).

I do these steps in VBPro.
- Clean foo.sln and bar.sln, which deletes all generated files except the bar.lib file I mentioned.
- Build foo.exe before building bar.dll

I get a message box that says "foo executable stopped working." or something like that. If I build bar.dll first, I do NOT get the error.

I do NOT get the error if I do these steps manually in VS2008.

I alleviate the issue if I do this in VBPro:
- Clean foo.sln and bar.sln, which deletes all generated files except the bar.lib file I mentioned.
- Build bar.dll
- Build foo.exe

Any clues?

[kinook]

http://www.kinook.com/Forum/showthre...?threadid=4500