Sunday, 15 April 2012

visual studio - How to make sure nuget assemblies are added by package rather than only reference to DLL file? -



visual studio - How to make sure nuget assemblies are added by package rather than only reference to DLL file? -

i have noticed many times developers tend reference assemblies straight browsing .dll file under .\packages folder (installed project) , adding project references instead of installing nuget bundle on project. in case, though compiles, nuget bundle manager not know referenced assembly package, , updating bundle solution-wide not update references in project. if doing service oriented architecture each piece of feature in application separate project in solution, have hundred of projects, , managing references become nightmare. there way prevent developers referencing assemblies straight if belong nuget package? illustration there msbuild task verify references bundle assemblies require bundle installed on project?

if team uses resharper, have plugin help this:

http://blog.jetbrains.com/dotnet/2012/11/20/add-packages-not-references-a-nuget-plugin-for-resharper/

i'm guessing issue caused people using resharper without it, since default vs won't know include dll resharper find , reference (and not update bundle config without plugin)

also used having people using nuget @ solution level, not project level. forcefulness people update nuget packages across solution, , not leave v 1.1.1.0 on project , v 1.1.2.0 on project b.

visual-studio msbuild nuget nuget-package

No comments:

Post a Comment