If the version info that shows up in the output from heat is something you
provide as an input to your build, you could replace it in heat with
"$(var." or"$(env." entries where you supply those inputs to candle or the
build environment, as appropriate. That would "automate" that part of the
process without resorting to sed.

How do you currently set your assemblies' versions today?

-----Original Message-----
From: Asker Brodersen [mailto:asker.broder...@esri-sgroup.se] 
Sent: Thursday, November 26, 2009 10:33 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Cannot register assembly

I need COM/Interop registration.

Yesterday I harvested my assemblies with HEAT, cleaned up the output and use
that as a separate .wxs. It works, but still requires that I update the
version info for the assemblies manually in the file before a release. Well,
I guess I could use sed to replace the strings to automate it all...

I just don't see why this should be necessary, or maybe it's not?

/Asker


-----Original Message-----
From: Blair [mailto:os...@live.com] 
Sent: den 27 november 2009 02:33
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] Cannot register assembly

What kind of registration do you need? COM/interop registration? Or just the
ability of the two assemblies to find each other when installed into the
same directory?

-----Original Message-----
From: Asker Brodersen [mailto:asker.broder...@esri-sgroup.se] 
Sent: Thursday, November 26, 2009 1:09 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Cannot register assembly

Hi,
I'm trying to have WIX register my assemblies, but when I do the install
they are only copied to the right location, not registered. What's the
correct way of doing this, I don't want them in the GAC?
This is what I'm doing (two different attempts):

<Component Id='ArcMeldisDrift' Guid='5B079754-C848-4E08-B2F6-D41D07D08F90'>
  <File Source='..\build\Release\ArcMeldisDrift.dll' Assembly='.net'
AssemblyApplication='ArcMeldisDrift.dll'
AssemblyManifest='ArcMeldisDrift.dll' KeyPath='yes'/>
</Component>
<Component Id='ArcMeldisFiler' Guid='EE384F8D-F35F-42c2-A112-2D246F768670'>
  <File Id='ArcMeldisFiler' Name='ArcMeldisFiler.dll'
Source='..\build\Release\ArcMeldisFiler.dll' Assembly='.net'
AssemblyApplication='ArcMeldisFiler' AssemblyManifest='ArcMeldisFiler'
DiskId='1' KeyPath='yes'/>
</Component>

Looking around the net I've seen several older postings from people using
Heat to extract info from the dll:s and manually populating the registry.
Surely this shouldn't be necessary?, and that would break automation as it
would need to be re-done for every assembly version update.

Regards,
Asker


----------------------------------------------------------------------------
--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus
on 
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


----------------------------------------------------------------------------
--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus
on 
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

----------------------------------------------------------------------------
--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus
on 
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Reply via email to