dll in that location, regardless of what mode you're currently in (Debug or Release).
dll that is located in the /Release folder, then Visual Studio will always look for the. When you say you deleted references to those projects and re-added them, how did you re-add them, exactly? Did you use the "Browse" tab in the "Add Reference" dialog in Visual Studio? Or, did you use the "Projects" tab (which lists neighboring projects in your solution)?Įdit: If you use the "Browse" tab, and manually add the reference to your. It disappeared only after I reinstalled Windows :( For those who met this problem: I couldn't solve it in an easy way. Why does it search for referenced projects in Release folders when I always use Debug mode? I tried to delete references to those projects and read them, but in some time I start getting these errors again. I made a good search over the Internet and found a few people with a similar problem, but there was no solution, or at least no working solution. Why? I tried to search for reference to "Release\projectX.dll" inside all solution files, and I found one in ResolveAssemblyReference.cache file. But when I try to run the main project - sometimes it gives me a few errors, all of which are "Metadata file '.\Release\projectX.dll' could not be found" - and, look, it says about RELEASE folder, though current mode is Debug. The current build mode is Debug and all projects' configurations are set to Debug. I have a solution with several projects in it. Metadata file '.\Release\project.dll' could not be found in Visual Studio Recently I started to get this message randomly:
0 kommentar(er)
