Hi ludin,
After take a look at the similar threads in MSDN.
The folllowing thread might be helpful for you.
Please note the marked answer.
<copied>
Problem solved after playing around with the project references.
It seems there was one project reference that caused the error to appear. That project in question used three different names: one for the assembly name (.exe), one for its source code root, and yet another one for the name of the project itself. The referenced project itself compiles.
Apparently VS.NET could not resolve the project reference under these circumstances. After correcting this, everything would compile smooth.
</copied>
Best regards,
Kristin
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click HERE to participate the survey.
No comments:
Post a Comment