Heat simply calls the ::DllRegisterServer() entry point and captures the data. The DLL must be writing different values on different OSs.
On Wed, Oct 24, 2012 at 9:59 AM, john.burak <john.bu...@telvent.com> wrote: > Hi, > > We recently automated Heat on our COM-registered libraries. I ran it on > the > same DLLs on a 64-bit machine and a 32-bit machine and noticed a couple > differences in the .wxs output. Heat on the 32-bit machine added > ProxyStubClassId32 attributes to the <Interface> elements, and added > ThreadingModel="apartment" to some of the <Class> elements. > > Is there a reason the generated source-code should differ when built on a > 32 > vs 64 bit machine, or is it just a Heat quirk? It seems like the generated > code should ideally be the same. > > Thanks! > > - John Burak > > > > -- > View this message in context: > http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Differences-in-Heat-output-when-run-on-32-vs-64-bit-build-machine-tp7581551.html > Sent from the wix-users mailing list archive at Nabble.com. > > > ------------------------------------------------------------------------------ > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics > Download AppDynamics Lite for free today: > http://p.sf.net/sfu/appdyn_sfd2d_oct > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
