.NET 3.0 and 3.5 in Windows Server 2008 R2 Server Core


Much like .NET 2.0 in Server Core, .NET 3.0 and 3.5 are also subsets of functionality. Included are:


·         Windows Communication Framework (WCF)


·         Windows Workflow Framework (WF)


·         LINQ


The only functionality not included is the Windows Presentation Framework (WPF).


.NET 3.0 and 3.5 functionality is installed with a single package:


·         Start /w ocsetup NetFx3-ServerCore


If 32bit support is needed you first need to install WoW64 and then .NET 2.0 WoW64 support, the following assume the above command has already been run:


·         Start /w ocsetup ServerCore-WOW64


·         Start /w ocsetup NetFx3-ServerCore-WOW64


 


Comments (4)

  1. Anonymous says:

    こんにちは。(やはり、ブログに書いておくことにしました . . .) ご存じの通り Server Core は、Windows Server 2008 R2 で .NET 開発者にとっても無関係なものではなくなりました。いままでは

  2. Anonymous says:

    Now that .NET is available in R2, does that mean ServerManagerCmd.exe will also be available?

    Or, if it’s not, is Routing & Remote Access Services a supported role on R2?  The inability to set up site-to-site VPNs between Server Core machines is extremely frustrating.

  3. Andrew

    It appears that a reboot is required after the "start /w ocsetup ServerCore-WOW64" command. There was no prompt in the console indicating this was required and the c:windowslogscbscbs.log was 0 bytes in size. I ran the command multiple times to no avail. "oclist | findstr /i wow" showed NOT installed. But during shutdown portion of the reboot I could see some updates were done (as per status messages) and after reboot cbs.log was a little over 1MB and oclist showed WOW64 support as installed.

    Perhaps consider updating the blog entry so that others that dont read the comments dont waste time.

    M@

  4. is it supported on windows server core 2008 x86 says:

    Hi, I can’t even see the feature name on oclist output Dism not available and the comman to install it returns an error
    is there a workaround to install .net 3.0? thanks for the reply