Printable View
Hi :wave:
I'm getting the following error when i compile my program
Error: The dependency 'Common, Version=1.0.2021.24982, Culture=neutral' in project 'MyProj' cannot be copied to the run directory because it would conflict with dependency 'Common, Version=1.0.2021.27968, Culture=neutral'.
How do I Fix This???
Thanx
Cranzy
:eek2:
Do you have two copies of the framework on your machine? Are you porting from one to another?
Looks like you're trying to overwrite a dependancy with an older version.
No.
I have 1 copy ... It is a program which launches a dll ... and in those dlls it loads another dll?
any ideas?
Ok ... I can explain the situation.
Let's say i have a dll - called MAINDLL
now .. i have another dll DLL1 which has a reference to MAINDLL.
now .. i have another dll DLL2 which has a reference to MAINDLL.
My main program .. refrences DLL1 and DLL2 ... ... this is when i get the WARNING.!!
plz help
Not really sure, but is dll1 and dll2 referencing the same stuff in maindll? Maybe dll2 can't use certain functions since dll1 is using them? But then again, i'm not sure if those two dll get different instance of maindll.
This is just a versioning error which you can get if your references aren't setup correctly. If you're using a multi-project solution, you need to set your project dependencies in order to get the correct build order. From what you're saying, you need to build MAIN.DLL, then DLL1, then DLL2 and finally your application.Quote:
Originally Posted by Cranzy
Yip .. that is it ...
I worked out the dependencies and compiled them in the right order .. then my main program compiled successfully.
Now ... if i change something in the dll which gets used by both dlls ... that means i have to recompile everything ..
is there a command line (which i can run from start -> run) which compiles a solution ???
You can use devenv from the command line but you need to setup environmental variables. There's a bat file for that (Programs>Microsoft Visual Studio.Net>Visual Studio .Net tools>Visual Studio .Net Command Prompt). Once you start a command session with that, issue a "devenv /?" command and check out the command line parameters. devenv works like a charm for simple projects (solutions with one project only). With multi-project solutions it may throw errors.