Building with .Net 3.0 will require .Net 2.0 SDK – level 200
Here’s a bit of info that I’ve glossed over for some time. I always have Visual Studio installed with building projects with .net 2.0 and 3.0, and VS bundles the SDK. On my current project, we have a graphics designer who works on html and css, but we have a local build that even he uses. Everything is automated. The designer doesn’t have VS 2005 installed, and when we started using WCF in .Net 3.0 for some web service calls, his build (and the CCNet box) started breaking. Before .Net 3.0 libraries were used, all that was needed to build our app was the .Net Framework 2.0.
.Net FX 2.0 includes MSBuild.exe, so all was well. Using some stuff from WCF causes some other tools to be called, so now the .Net 2.0 SDK is required on the build (CCNet) box as well as the designer’s box.
What a jacked-up name: .Net 3.0, but be sure to mark “2.0” in IIS!!
That really was a piss-poor decision on Microsof’s part. .Net 3.0 and (what’s being touted as) 3.5 both run on CLR v2? Way to go marketing, and high-fives to whichever tech guys didnt dissuade them.
What’s the requirement for WCF that needs the .NET SDK? I have a couple of .NET 3.0 apps at work (using WCF and WF) but the SDK is not installed on the client’s machines.
@Javier,
I need the .Net 2.0 SDK on machines that need to build the .Net 3.0 app (CruiseControl.net server, etc).
I don’t need the SDK on production servers or client machines.