c# - Resolving multiple conflicting versions of System.Web.Mvc when using NuGet as package source -


I have a project to find several versions of the same assembly. System.Web.Mvc For example:

Image Details Here Enter

I want to make sure that our MVC projects will never get the old code from anywhere except the Nugget formulas.

I know that this is not a good idea to go about removing disputed versions from the system because many applications can be based on them. For example, it was found in a C: \ Program Files (x86)

update:

Since we are using NuGet , I changed it:

Project & gt; Properties & gt; Build & gt; Output & gt; Output path: to C: \ temp \ drop

in each project (we also have some portable area classroom library projects) and then < P> Project & gt; Properties & gt; The reference path was added and the C: \ temp \ drop

and the problem went away.

Is this the right way to go about this or this I am just opening another on the insects here?

Checking the assembly binding and related, it is quite good:

Check it also.

The strongly nominated Legislations for GAC, a complete hierarchy that is used to find the assembly in the first place, in your case you are using a strong Nominated Legislative Assembly. As explained in the article, you should be able to direct your application to the right assembly version on runtime

Comments

Popular posts from this blog

java - ImportError: No module named py4j.java_gateway -

python - Receiving "KeyError" after decoding json result from url -

.net - Creating a new Queue Manager and Queue in Websphere MQ (using C#) -