C# user control library solution

Question

0.00/5 (No votes)

See more:

I wrote a User control library project. when i try to test it i get the following message :
System.ArgumentException: 'Assembly 'C:\Users\raymo\OneDrive\Documents\Visual Studio 2017\Projects\C#%5CModels%5CModels%5Cobj%5CDebug%5CModels.dll' could not be found. Ensure the path is correct.'
how can i eleminate it.

What I have tried:

I have not such a experience, i don't know what to do.

Posted 24-Jun-17 18:37pm

Member 12687352

Updated 24-Jun-17 18:56pm

Add a Solution

1 solution

Add a Solution

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)

OriginalGriff · Answer 1 · 2017-06-24T18:56:00

The "%5C" parts of the path are "encoding characters" which have replaced the actual character with it's hexadecimal equivalent. In this case, the "%5C" is replacing backslash characters '\' which means the path should be:

C:\Users\raymo\OneDrive\Documents\Visual Studio 2017\Projects\C#\Models\Models\obj\Debug\Models.dll

So start by looking at where the "bad" path is coming from, and when you are getting it: if necessary do a file search in Windows Explorer to find where that string is referenced (You may need to use "Advanced options...FileContents" to locate it.

Once you've found it, you can start looking at how an encoded path got in there ... but we can't help you do any of that - we have no access to your system.

As a final "Nuclear" option, create a brand new solution, add new projects, and add your files to that slowly until either the problem occurs, or you get a working complete solution.