Note that it's pretty conventional, and should look like a typical. Select ".NET Framework 3.0" and make a new "WCF Service" take a look at the web.config. If you go into Visual Studio and File | New | Project (or Web Site), take note of the drop down in the upper right corner. They are 2.0 apps using the 2.0 compilers and 2.0 CLR. Your 2.0 apps still run on a system with 3.0 installed. NET 3.0 doesn't fundamentally change your system in any way you should fear.
#How to get pool studio 2.0 for mac windows
Instead, it's three major new libraries: WCF (Windows Communication Foundation née Indigo), WPF (Windows Presentation Foundation née Avalon) and Windows Workflow or WF.īottom line: Installing. NET 3.0 didn't mean new compilers or a new CLR. That's where, along with the GAC (Global Assembly Cache) all the libraries and compilers you know and love live. NET is in %windir%\Microsoft.NET\Framework\v7. Additional fundamentally new functionality has to be named something. I didn't initially like the naming, because I assumed that each major version of the Framework meant a new CLR, but it's growing on me as I understand it more. This is where marketing and reality part ways. Here's an explanation of why this is confusing, and hopefully by the end, it won't be confusing anymore. NET 3.5 in the list and it's not there, and they freak out, rightfully so. A question that comes up a lot is this: How do I tell my IIS Application or Virtual Directory to use ASP.NET 3.5 rather than ASP.NET 2.0?įolks often go into the IIS6 or IIS7 manager and setup an AppPool and see a properties dialog like this, and when the pull down the option, they often expect to see.