Managing Nuget packages

Question

0.00/5 (No votes)

See more:

Hello everyone,

I have the following situation: I am currently working on 2 projects. The first one uses EF6, the second one EF4. When i open the SLN file, VS prompts me to downgrade the reference, and i need to either update or downgrade the references. Every time this mean connecting to the NUGET servers and waiting for it to download. Is there a way to store or detach each reference for each projects? Or am i getting this whole issue wrong? Thank you for your answers.

Posted 17-Mar-14 8:33am

NvsYazilim

Add a Solution

Comments

Sergey Alexandrovich Kryukov 17-Mar-14 16:02pm

It sounds so wrong... Not trying to answer the whole question: what prevents you from having two different solutions? Are the two projects depend on each other? If they are, using different Nuget versions would be a very bad option. Why not upgrading both projects to the latest version permanently?
—SA

NvsYazilim 31-Mar-14 7:30am

Hi Sergey, was out for a couple of days sorry. The issue is not with the same projects, but different projects. For example a ERP project, and a News Website. Hence, the projects are not dependent to each other. Regarding the upgrade, for large project this allways seems to create problems (for example EF dbcontext), hence upgrading is not an option either (altough preferrable as you say). Maybe i should elaborate, are there a way to save nugets locally, and load them from there in a user friendly way?

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)