Has anyone else seen this error? I did find something similar on a forum for Genome an
Object-relational mapping product.

Forum Question:

“I am getting the following error in the same environment

"Could not get dependencies for project reference 'XXX.mapping' "

I added my .mapping project as a reference in a web service. It compiles
and runs perfectly but I keep seeing this error. "XXX.mapping.dll" is
properly copied to my /bin folder. Any suggestion?”

Answer:

“It seems that Visual Studio's web projects using some special behavior
on the referenced projects that the Genome schema project (the code-base
is also from MS) does not support.

We have investigated this issue but could not find a solution for that.
However, based on our experience the problem does not cause any
misbehavior. Please let us know if you experience any problem regarding
this reference.

We hope that one of the upcoming custom project code-base of the Visual
Studio SDK will solve this issue.”

Although I can’t seem to find the source of this error, my test site seems to execute without any other indications of a problem, i.e. like the problem above “However, based on our experience the problem does not cause any misbehavior.”

This occurred after an upgrade. I’ll set up a fresh test site for DNN 4.5.1 and report the results here. I always have a problem when things aren’t perfectly aesthetically pleasing (we all have our faults). If anyone can enlighten me on this matter, please do so.

Thanks,
G.M.

When I first started developing I was plauged with errors like this...   specifically when I was using third party modules, it ussually had to do with one third party module looking for a specific version of the dnn dll, or ONE old version somewhere in one of your bin directories.

After 3 months of struggling with this all the time, moving back and forth from production to test, upgrading dnn versions, etc..  I finally figured it out:

Don't use the source version of DNN.  If you HAVE to use the source version of DNN, use it without any modules but the one you're developing...  everything seems to work if you have the source of EVERY module loaded in your solution.

These days I just have a second solution setup with the source that i use as read-only reference only when needed.  I never modify the source - any time i need to do something tricky that seems like it would require change the source, i can ussually create and HTTP module to intercept some aspect of whats happening and change it....   You don't want to change the source anyhow - it makes upgrading versions a 4 day project instead of a 4 hour project.

I hope this advice saves you some time, I wasted weeks of time to being stuck on the idea that I wanted to do my development with the source project - just in case i needed to do some debugging...  that 'just in case' doesn't actually happen now that I develop with the install distributable.