Click here to Skip to main content
15,881,882 members

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.