I did try setting that property and I'm sure it would have worked fine if the
necessary dependencies had already been installed in the GAC.
I think the issue was that the .NET COM+ library has dependencies on the
GAC'd components and that the "commit" to the GAC doesn't occur until the
MSI has f
The answer, heat. You're allowed to say I told you so.
:)
Sincerely,
Adam
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Q-Error-using-ComPlusAssemblyDependency-to-register-a-NET-COM-assembly-tp5951460p5969344.html
Sent from the wix-users mailing
I think I've worked out what the issue is... its just the solution which is
causing issues!
I'm trying to install a .NET application which has a .NET COM+ component. Of
course, the COM+ component wont register until the assemblies it depends
upon are present in the GAC which doesn't seem to happe
3 matches
Mail list logo