How NuGet packages are referenced from a class library?

Question

0.00/5 (No votes)

See more:

I have projects A (web application) and B (Class library).

Project B is added as a reference to project A. Now, Project B contains some NuGet packages.

On my machine, when I run project A it is working fine without any errors. But when the same project is loaded on a different machine, It gives the missing NuGet package dll error for the Nuget package from the class library.

My project is built with .NET framework 4.8 in Visual studio 2022.

What I have tried:

1. Delete bin/obj and package folder and rebuild the project A which has the reference of project b.

Posted 19-Oct-22 20:55pm

Ravi-from-India

Updated 19-Oct-22 22:35pm

v2

Add a Solution

Comments

Richard MacCutchan 20-Oct-22 3:32am

How did you install it on the different machine?

Ravi-from-India 20-Oct-22 4:34am

I have installed Nuget packages using Nuget package manager only in project b and then I have added the reference of project b in project A.

Richard MacCutchan 20-Oct-22 4:41am

That was not my question. I meant how you installed the completed application in the different machine.

Ravi-from-India 20-Oct-22 4:44am

It's a web application and we are checking in the local machine only. Basically, I have committed my changes for project b and project an in my branch and other dev checked out it.

On my machine, I don't need to install the Nuget package separately on project A, but on the other dev's machine, when he runs the same code from my branch it is showing a missing dll reference.

Richard MacCutchan 20-Oct-22 4:47am

That suggests that the other dev needs to add the Nuget packages, which are probably not part of the committed code. You should be able to check this yourself by inspecting the location that you commit to.

Ravi-from-India 20-Oct-22 4:56am

I have committed the package.config file with project b. so when other dev checked out my branch and restore the Nuget package, they are getting it available in the class library project. I.e. project B.

Richard MacCutchan 20-Oct-22 5:19am

Then there is something still missing from the committed code. But there is no way anyone here can guess what that could be.

Dave Kreskowiak 20-Oct-22 9:30am

You STILL haven't answered the question. How did you package up and install the web application on the other machine?

Richard Deeming 20-Oct-22 4:24am

Try right-clicking on the solution and selecting "Restore NuGet packages".

If that doesn't work, check the output window for errors.

Ravi-from-India 20-Oct-22 4:34am

Yes, tried this. Didn't work.

Richard Deeming 20-Oct-22 4:35am

So as I said, check the output window for errors.

Ravi-from-India 20-Oct-22 4:37am

While building a project, it doesn't give any errors. But when I run my project it crashes and throws an exception that a certain Dll is not found. Are you missing any references or assembly?

Richard Deeming 20-Oct-22 4:40am

Run the "restore NuGet packages" and check the Visual Studio output window for errors.

Just repeating the fact that the application crashes at runtime tells us nothing, and leaves you in the dark trying to guess what the problem is. You need to get the actual error details in order to resolve the problem.

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)