now (all of a sudden...) something quit working

we have a C# custom action that requires a couple of assemblies.  in
wix3.0 these assemblies were copied into the
CustomAction.Install.WiX.CA.dll-# directory where the custom action was
invoked.  but now using winx3.5 it is failing because it cannot find these
dependent assemblies.

originally we were referencing the assemblies by Browse... but this did
not work.  changed to referencing the assembly projects.  yesterday this
worked.  today it does not.  what did I change?  yes.  actually I checked
out some code that worked yesterday but today it does not.

how do I reference assemblies needed by a C# custom action so that they
are copied into the temporary directory when the custom action is invoked?

------------------------------------------------------------------------------
Achieve unprecedented app performance and reliability
What every C/C++ and Fortran developer should know.
Learn how Intel has extended the reach of its next-generation tools
to help boost performance applications - inlcuding clusters.
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Reply via email to