CODEWITHSUNDEEP
asp.netvisual-studio-2015
TDeoodfig
TDeoodfig

Reputation: 119

Visual Studio looks for dll in the wrong directory

I am getting an error of "Could not load file or assembly 'Microsoft.AI.Web' or one of its dependencies" in the browser of my asp.net app. Microsoft.AI.Web is from Microsoft.ApplicationInsights.Web NuGet package.

I noticed this: 

LOG: Appbase = file:///D:/Source/Workspaces/AppName/Branches/Main/Application/WT/
LOG: Initial PrivatePath = D:\Source\Workspaces\AppName\Branches\Main\Application\WT\bin

the dll in question is located at D:\Source\Workspaces\AppName\Branches\Main\Application\packages\Microsoft.ApplicationInsights.Web.2.4.1\lib\net45\Microsoft.AI.Web.dll

As for personal dll's -- In the project-->properties-->build-->output path--> I have it set as "..\Any\Debug\". When I build the project the DLL's populate there.

I checked References and code in .csproj file and all the dll are located where I specified to.

I am not sure why it's trying to look at the bin file of the project when I told the output is somewhere else AND to look for the dlls in that same folder(through references and .csproj file). How do I make it so that VS will look for the dlls in the folder path I want instead of "WT\bin"?

When I change my project output path to "bin", it can detect the dll's there EVEN though the path of the dll remains the same( D:\Source\Workspaces\AppName\Branches\Main\Application\packages\Microsoft.ApplicationInsights.Web.2.4.1\lib\net45\Microsoft.AI.Web.dll).

Upvotes: 2

Views: 2444

Answers (2)

Serj Sagan
Serj Sagan

Reputation: 30247

Although this is a really old post, since Google takes me to it for my query, here's the solution. The issue ended up being related to the Solution and Project Build Configuration. In Visual Studio you can select the Build Configuration here (typically just Debug and Release for a new project):

Visual Studio Build Configuration Selector

For the projects that are putting the DLL in the wrong folder, make sure that the correct Configuration is selected. This is where my issue was, however you may also want to try selecting a different Build Configuration, even creating a new one. Selecting the correct Build checkmarks is also important, in general they should be selected for all Projects needed to run your Solution.

Upvotes: 0

Ctznkane525
Ctznkane525

Reputation: 7465

Since it's a Microsoft strong signed DLL, add it to the server's GAC.

If you place it in the GAC, it'll find the file automatically. Another plus there is that if you need it for another project deployed on the same server, you don't need to deploy it again.

Here's some information on how to install a DLL into the GAC on the server machine, assuming gacutil is not installed there. Look at the accepted answer, not the question. Drag and drop a DLL to the GAC ("assembly") in windows server 2008 .net 4.0

Copy gacutil.exe and gacutil.exe config from your machine to the server's C:\Windows\Microsoft.NET\Framework\v4.0.30319

Then run on the server: "C:\Windows\Microsoft.NET\Framework\v4.0.30319\gacutil.exe" /i "PATH TO YOUR DLL"

Upvotes: 1

Related Questions