Google has created a thing called “adword quality”.
Now let us go back in time when dinosaurs wrote .BAT files and find out how they should have done it in PowerShell
Well, dunno, but it sometimes needs to be deleted to get a VS2003 compile to work.
It lives at:
PropertyGroup = Variable declarations
Task= Statement/Method Invocation
Import = Reference/Include/Using statement
Target = Code Bock/Subroutine
Control of Flow
Code runs once. So if a project has 10 dependencies that need to be compiled, and other projects depend on some subset of those, they won’t be rebuilt. I think this is what makes a build script different from an ordinary script, like a ps or bat file.
Why would we want to? All truly difficult questions will at first immediately ellict dismissals and unhelpfully overly simple advice.
Why not just move to 2.0? Upgrading to 2.0 usually is effortless, unless: your organization has burdensome rules about doing anything, like upgrading to 2.0.
Msbuild’s location varies depending on version.
There isn’t a 1.1 version.
Msbuild is considered unusable without extending it, http://msbuildtasks.tigris.org/, the community built tasks.
MSBuild files can be edited with MS-Build SideKick, (14 day trial $55 single user license).