Repair NuGet Package for Website

I am trying to use NuGet package recovery using VS2010 + Visual Sourcesafe . It works partly for me. Where does this happen: NuGet does not receive the missing packages

enter image description here

My Solution2 has an asp.net site [Project1 in the image above] where another nuget package is installed. Now another developer opens solution2 through VS2010, automatic recovery works for library projects in Solution1. It receives all the missing packages for the library projects referenced in this solution2, and I see them in the Solution1 / packages folder.

But for the Website, he says that external dlls, i.e. missing. I think the problem is that the website does not have a .csproj file, and therefore it does not know that things need to be restored. ( http://nuget.codeplex.com/workitem/1663 )

Partially do this:

  • Added /repositories.config packages for website solution ( What is the solution folder in visual studio )

  • Another developer goes to VSS and retrieves this package folder manually. Now, when he creates the solution, the package manager console requests recovery, that is, it has a Restore button. When you click on it, AjaxControlToolkit will appear.

Questions: - Is the above approach the only and most accessible for websites?

  • When a developer clicks the Restore button, he brings packages for the library also to Solution1 / packages along with packages for nuget. Any reason why he would do it?

Any ideas on the above issues?

+4
visual-sourcesafe visual-studio visual-studio-2010 nuget
source share
2 answers

To add the solution-level packages folder using repositories.config in VS Solution Explorer, I created the Solution folder and added repositories.config.

This created the packages folder in SourceSafe when I registered the solution.

I also found a person pointing the same here .

Update: I think the new nuget is restoring packages. But one more trick for nuget to add dll to the bin folder for registering .refresh files for AjaxControlToolkit and its dependent packages.

+1
source share

In your link, nuget does not support websites. If you really need to use Nuget, and let them face it, they do everything, then, in my opinion, the best approach is to switch your website to a web application, after which the visual studio will create a csproj file for you, in which details nuget packages that are contained in the project. NTN

+3
source share

All Articles