Click here to Skip to main content
14,878,805 members
Please Sign up or sign in to vote.
1.00/5 (1 vote)
See more:
Using Visual Studio Community 2015 and Visual Basic, I get build errors that it can't find a library. It indicates two of my DLLs and only half of the path. The other half of the path is in another error message with no mention of the DLL. It's a fairly large project with a lot of references, but this only happens on two of them.

For example,

could not find library 'C:\Users\BSmith\Documents\Visual Studio pro'
could not find library 'jects\custom controls\source code\obj\CustomProj.dll'

Thanks.
Posted
Comments
ZurdoDev 31-Dec-15 18:37pm
   
Did you manually edit the project file? Sounds like the .proj file is messed up.
Member 12238213 1-Jan-16 12:25pm
   
I did not edit it, and I looked at it with a text editor. The path to the two DLLs looks correct.

1 solution

Problem solved. The path's that I described above are representative of the problem but are not the actual paths because the real paths include some customer proprietary names. If I could show the actual path names the answer might have been obvious.

The real paths include a comma in one of the folder names. That's my bad for creating the folder that way in the first place but now it's too late to change.

The break in the path names that forces it into two lines and two error messages occurs at the comma. In the real error messages the comma is not displayed and that should have been a clue to me also.

I copied the two DLLs into a new folder ahead of the one with the comma, made a new reference, and all is good.

This is a tiny bit cumbersome for me because one of the DLLs is also from my own VB code, so now I have to remember to copy the DLL from the source folder to my new folder whenever I make a change to that code. But unless there is a way to get the compiler to not puke on the comma, I'll just have to live with that extra housekeeping.

Interestingly, my entire project includes that folder with the comma in the path, and these are the only two problems related to it.
   

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

  Print Answers RSS
Top Experts
Last 24hrsThis month



CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900