Not really. I doubt it's actually VBP itself causing this -- the Make VS.NET action ultimately invokes the VS.NET command-line compiler to perform an actual compile. If you check the 'Show command-line' on the Options tab, build, then copy and paste the devenv.com command-line from the build output to a Command Prompt and run it there, you should get the same behavior. You could then open a support incident with Microsoft to determine why it's doing that.
|