Circular Reference in Merge Module Search Path

moWhite · Joined: 08 Nov 2007 Posts: 1

I use a post build event to copy my merge modules to the c:\Program
Files\Common Files\Merge Modules\ folder. I add this to the search
path in each merge module project.

I'm getting circular references to the wrong merge module.

EDR.dll >>> EDR.msm
EDR.Geo.dll, includes reference to EDR.dll and 3rdParty.dll >>> EDR.Geo.msm,
picks up EDR.msm and 3rdParty.dll
EDR.Geo.Win.dll, includes EDR.Geo.dll >>> EDR.Geo.Win.msm, picks up EDR.msm
and EDR.Geo.dll

Second time I build, EDR.Geo.dll picks up EDR.Geo.Win.msm for the
3rdParty.dll stuff. This screws up EDR.Geo.msm so EDR.Geo.Win.msm does not
contain the correct files.

Does this make sense? Why don't the dependancies work with the search path?
Have I designed this wrong?

Richard

Archived from group: microsoft>public>vb>deployment

DAO 3.5 Merge Module I am looking for a DAO 3.5 merge mdoule. I searched the mdsn web site and found barely anything on DAO 3.5. I know it is out dated but the app I am using it still needs it. I have found this link:

merge modules depend on themselves? I find that when I create a merge module for Visual Basic output in Visual Studio Installer, the dependencies include the merge module project's own merge module. Is this to be expected or have I inadvertently created a circular reference? This is true of

I can NOT figure out what merge modules to include, to distr I have this program I've been working for quite a while. It works just fine, on my machine. (I'm using Visual Studio .NET 2003 with Crystal Reports 9.) When I attempt to run the application on a user's machine, it ALWAYS fails to bring up the Crystal R

How to detect wich dlls and merge modules to deploy Hello, We are reviewing our setup of a larger at the moment. At the moment we are deploying a lot of dlls to the target system. The dlls have been detected by visual studio 6 to be necessary for our application. This has been 4 years ag

Error IDS_IIS_ObjectNotFound (Object/Module not found) Hi, We have an application aleady working on windows 2000 and NT server. We are planning to transafer these servers to Windows 2003. The application developed in vb6.0 and backend using access 2000 database, around 4 years these applications are working i