The Microsoft .NET Framework 4.5.1 is now available to Windows Server 2012 R2 and Windows Server 2008 R2 users.
That means you can install nuget 4.6 and nugets latest version, nginx 4.7 as a webserver.
That way, your web server can be configured to serve your content from a local file server.
This guide will walk you through how to install this new version of nginx.
You can find the full installation instructions in the Microsoft documentation .
You will need to enable the Web Server Mode option to get this new nginx server running.
If you are using a Windows Server 2003-based server, you can skip this section.
In the previous tutorial, we used Windows Server 2000 to run our server.
That is the recommended setup, but if you are running Windows Server 2002, you will want to install the latest version of the Windows Server.
To do this, follow these steps: Launch the Windows PowerShell console, navigate to the PowerShell Gallery, and click on the New cmdlet button.
Name the new cmdlet, and then type in the following command.
New-WebServer -Name nginx -Server nginx,80,port 80 -WebServerMode WebServerNow, click OK to save the changes.
You will get a prompt to confirm your changes.
After you click OK, you should see the new nnginx web server in your Start menu.
To install this nginx web server, simply launch it in a Windows PowerShell session.
If your nginx installation has been updated to the latest one, you’ll see a message like this in the Windows log: Installed nginx version: 126.96.36.199-188.8.131.52, running on http://127.0 and port 80.
You must restart nginx to take effect.
Now that you have installed nginx into your Windows server, your new web server will have access to your content.
If the nginx webserver has been started from an elevated command prompt, it will look for the nngginx server name in the Start menu, and start nginx in that location.
If not, the new web site will fail to start.
To fix this, simply run the following commands in the command prompt.
Start-WebSqlite -Server “127.1.1.”
-WebSite nginxNow, restart nnginet on your server to get it to start again.
This will make nginx available to your web site.
Next, we will configure nginx for your new location.
For now, you need to install a few additional packages to get the new webserver up and running.
First, we need to ensure the Web Installer package is installed on your system.
You do this by running the following in a PowerShell session: $webinstaller.exe /Software/Policies/Microsoft/WebInstaller.msc Start-Process -Path C:\Windows\system32\webinstallers\install.exe -ErrorAction SilentlyContinue $webInstaller Now, install the following packages into your webinstallers directory: cscript-xml-utils -package cscript -package comdlg2 -package htmlparser -package xml-utils-html -package xsd-utils libxml2-dev -package libxml1-dev-bin -package dtb-core-devel-tools -package php5-xml -package plex-xml libxml-core -package lxml2xml2 libxml3-dev libxml5-dev xml-xml2 -install_dir /usr/local/bin/php5-html/ -installation_status 0 Install the following other packages: xml-delegation-deftype -package gz -package zlib -package jpeg -package tiff -package gif -package wget-client-agent libxml4-delevation-client -package js -package json -package bzip2 libzip-coreutils -installer $webpacker.install_package_dir $webparsers directory We also need to update nginx’s web server configuration so it can serve the new location’s files.
The most important thing to do is change the location of the nugetting file server to the default web site’s location.
To change the default location, open up a PowerShell prompt and type in: $server = Get-Server $server.
Location = “C:\WebInstallers\nuget.exe” This will change the server’s default location to the location that you specified when you installed nnget.
After doing this, restart your server.
To test your change, run the web server’s web interface and visit your new webservers new location: http://192.