15,892,005 members
Sign in
Sign in
Email
Password
Forgot your password?
Sign in with
home
articles
Browse Topics
>
Latest Articles
Top Articles
Posting/Update Guidelines
Article Help Forum
Submit an article or tip
Import GitHub Project
Import your Blog
quick answers
Q&A
Ask a Question
View Unanswered Questions
View All Questions
View C# questions
View C++ questions
View Javascript questions
View Visual Basic questions
View Python questions
discussions
forums
CodeProject.AI Server
All Message Boards...
Application Lifecycle
>
Running a Business
Sales / Marketing
Collaboration / Beta Testing
Work Issues
Design and Architecture
Artificial Intelligence
ASP.NET
JavaScript
Internet of Things
C / C++ / MFC
>
ATL / WTL / STL
Managed C++/CLI
C#
Free Tools
Objective-C and Swift
Database
Hardware & Devices
>
System Admin
Hosting and Servers
Java
Linux Programming
Python
.NET (Core and Framework)
Android
iOS
Mobile
WPF
Visual Basic
Web Development
Site Bugs / Suggestions
Spam and Abuse Watch
features
features
Competitions
News
The Insider Newsletter
The Daily Build Newsletter
Newsletter archive
Surveys
CodeProject Stuff
community
lounge
Who's Who
Most Valuable Professionals
The Lounge
The CodeProject Blog
Where I Am: Member Photos
The Insider News
The Weird & The Wonderful
help
?
What is 'CodeProject'?
General FAQ
Ask a Question
Bugs and Suggestions
Article Help Forum
About Us
Search within:
Articles
Quick Answers
Messages
Comments by wwwx (Top 5 by date)
wwwx
5-Sep-20 0:33am
View
If the code fail, in my case it's due to the DLL path I use is not latest, can check if the dll path is point to newest dll exactly.
wwwx
5-Sep-20 0:33am
View
If the code fail, in my case it's due to the DLL path I use is not latest, can check if the dll path is point to newest dll exactly.
wwwx
19-Mar-17 21:44pm
View
IT WORKS!
wwwx
28-Feb-17 21:25pm
View
I test and have to set the file Property > [Build Action] to [Content] then will work, if set [Build Action] as [Resource] seems not work
reference image
http://i.imgur.com/zwtVB3V.png
wwwx
19-Dec-16 4:22am
View
THANK YOU SOOOOOOOOOOO MUUUUUCHH!!!
I was trapped into this queer circles and trying lots of actions with no effect, your answer save me...
My answer to this probelem is, your total project folder path or file path is too long, just shorten some folder name and it'll be solved.
For example, I have my project path "E:\XXXX\Program\YYY\ZZZZZZ\ooo-ooooooooo_oooooooo_xxxxxxxxxx_zzz" will get this problem,
but I shorten it to "E:\XXXX\Program\YYY\ZZZZZZ\ooo_zzz" the the problem just disappear.
I'm unsatisfied with that why visual studio don't just show error message with "the folder path too long", but show this relativvely useless message to throw me into the queer circle such as push me to try to the direction of think it as some dll has problem or replace some dll.
the last time I met into a similar problem is that, just because there's space in the folder name nthen the project build failed, and just remove the space all is well.