I have followed the instructions to setup and host my own NuGet feed. I am running the web application on a Windows 2012 (IIS 8.5) box.
I build and
I have one answer not mentioned in either of the posts I've found. If you name your project Nuget.Server, even though publishing will work in IIS, ninject will fail to set up the package list route because it will try to load the wrong DLL and error out.
Here are some other possible answers:
Possible Answers 1
Possible Answers 2
I noticed that you get the 404 error when you try to upload fairly large nuget packages. I upped the maxAllowedContentLength
and it helped.
<system.webServer>
<security>
<requestFiltering>
<requestLimits maxAllowedContentLength="31457280"/>
</requestFiltering>
</security>
</system.webServer>
I was having this problem today. Actually what I need to do is this in Global.asax:
void Application_Start(object sender, EventArgs e)
{
NuGetRoutes.Start();
}
The NuGet.config file in either %APPDATA%\NuGet or $(SolutionDir).nuget may be referring to unexpected "active source" URLs. For example, the nuget.exe brought by the TFS build agent install might be aware of NuGet v2 protocol only while the URLs refer to v3 protocol. Or the custom NuGet server URL might be missing from NuGet.config.