If you have an ASP.NET Web Site project project (one who does not have the proper project file .csproj or .vpproj, and this is just a folder with files), then when you add the package with NuGet, it makes * .dll. refresh in the Bin directory to reference the package DLL in the parent package folder.
For example, if you run "install-package elmah" from the package manager console, then Elmah is placed in the packages folder in the project solution directory, and the Elmah.dll.refresh file is placed in the Bin folder of the project.
When I create a project locally, Visual Studio automatically inserts the DLL referenced by the update file. The site and Elmah are working correctly. I do not have the Elmah.dll file, which is located in the Bin directory of the project installed in the source control (only in the update file and in the package folder).
However, I use web deployment projects to precompile the site and perform web.config substitutions for deployments. When the solution is constructed in this way, Elmah.dll is not automatically pulled into the Bin directory of the website project and the website is not working properly due to the missing DLL.
How is NuGet intended to be used in this scenario? I suppose to check the Elmah.dll file in the bin directory?
Derek morrison
source share