VS2010 C＃在构建期间缺少项目dll

Question

I have problem with build in VS2010. I´m trying to develop small Prism, MVVM application.

I added new project "Toolbar" to my solution "MyApp" and during the build I get following error (propably project´s dll is not created for some reason):

Error 2 Could not load referenced assembly "C:\\net\\projects\\MyApp\\MyApp.Modules.Toolbar\\bin\\Debug\\MyApp.Modules.Toolbar.dll".

Caught a FileNotFoundException saying "Could not load file or assembly 'C:\\net\\projects\\MyApp\\MyApp.Modules.Toolbar\\bin\\Debug\\MyApp.Modules.Toolbar.dll' or one of its dependencies. The system cannot find the file specified.".

C:\\net\\projects\\MyApp\\MyApp\\ResGen MyApp

I´m quite new to VS2010 and C# so I really don´t know what happend, wheter project dll is missing because of some mistake in source code or why this can even happend? I also don´t know how to find such a mistake in source code, because VS shows up only the error mentioned above. Dependenies of the project should be ok i guess, file MyApp.Modules.Toolbar.dll really doesn´t exist in any folder on my hdd.

Answer 1

问题是在工具栏项目的xaml中定义的错误类名（UserControl x：Class =“BAD CLASS HERE”）。

Answer 2

After many googles for a similar problem where I had at one time toyed with using open office in a .net project and then all my aspx pages had the blue squiggely line saying cli_uno couldn't be found which was referenced no where and in none of my project or lib files.

I deleted all the bin folders, a dll referencing it was hiding in one of them and making vs2010 freak out.

I realize this isn't the exact solution to the above but there isn't much out there for this error and it is a head scratcher and deleting all the bin folders worked for me so it's something to try.

Answer 3

You provide too litle information, so I'll ask some questions (and some possible fixes):

1. Is the file at the specified path to begin with?
2. If not, is there a project you need to build to create the dll?
3. If there is such project, does it build the .dll where yours is looking for it -- if not, you either need to copy it by hand or set up a post-build process to do the copy automatically after each build
4. If there is no such project, do you have the .dll itself somewhere. If yes, you need to copy it to the correct location.
5. If the .dll is at the correct location, is there some protection preventing the other project to access it?