I have a whole set of powershell scripts that we have used now for more than a year to do our Visual Studio builds and deploys. We have been running on a Windows Vista Pro 32bit machine but now are moving to a new 64bit Windows 2003 R2 VM
This is the bizzare behavior I have:
Running the build via the Powershell ISE or PowerGui works perfectly.
Running the build via command line results in the 3rd execution of the SAME SCRIPT that executes msbuild.exe always returning NO RESULTS. If I use the same window after my script ends to call msbuild.exe directly without any parameters it acts as though the exe never starts, it simply goes to a new line at the command prompt.
With a brand new powershell window if i execute msbuild.exe prior to my script I get the normal "MSBUILD error etc..". After the script runs I get nothing at all. If i watch process manager while i exec it nothing happens. Its as if it never runs the executable but doesn't give me an error either.
But yet the same script works GREAT in the ISE????
Any ideas?