Geek asks and answers

Creating two C ++ applications that use the same DLL in 2010

I have applications A and B, both use dll D.
A, B and D are C ++ projects in version 2010.

A.sln and B.sln are decision files that create applications A and B.
Both A and B have a reference to dll D.

Expected places for applications and dll (subject to Debug creation):
A / Debug / A.exe
A / Debug / D.dll
B / Debug / b.exe
B / Debug / D.dll

Here comes the strange part: when I rebuild (or even clean up) solution B, it is somehow a remote A / Debug / D.dll file, although both applications are in no way connected.

Is there a way to instruct vs to only delete D.dll under B when rebuilding B?

+3
source share
3 answers

What is the clue path for solving B Link to D?

If your hint path points to solution A, this is your problem. Delete the link, copy D.dll from anywhere to the Solution B folder, and then rebuild the link using this path, not the solution path A.

+2
source

Did you create a project by copying *.vcprojand renaming several things? If so, then you probably came across a GUID used to identify the project. (This is a rare problem in a number of development stores.)

Microsoft GUID, Windows , , "" . ( , *.sln "", , , , , , "", .)

, GUID, / ( , ) GUID, " " (, DLL, EXE, .NET ..). GUID " " , , ().

Microsoft GUID : http://msdn.microsoft.com/en-us/library/hb23x61k%28v=vs.80%29.aspx

... , , :

http://onlinecoder.blogspot.com/2009/09/visual-studio-projects-project-type.html

"GUID " GUID-, , .

+1

What about solution A? What happens when you rebuild it? Does the DLL delete?

If not, check:

  • Project D is part of decision A (or not).
  • Project dependencies on D, A.
  • Links and related linker settings.

If there is inconsistency with decisions A, B; you need to apply the same thing in solution A.

+1
source

More articles:


All Articles