Lots of beginning questions here. Apologies if all have been answered before
but I'm burnt out on day 3 of very slow progress. I'm experiencing some
learning-difficulties with WiX. Thus far, I've completed a wxs-file for our
Windows Forms application that creates the installation directories,
help-files, pictures, and other junk. I've got the .NET 4.5 "launch condition"
in place, and all other properties are set. At this point, I'm where I'm
supposed to add all the exes and dlls. I'd much liked a tutorial from inside
Visual Studio that explains whether I should do "Add Reference" in the
Setup-project and point to my startup exe, or whether I'm supposed to do
something else. I'm fumbling around in the dark, and found this heat.exe. Ran
it against my application directory. This created a file that was well over 1
MB in size. Our application has 25+ projects, multitude of references, and
satellite assemblies for localization to 20 languages. Looking into the file
created by heat.exe, I was surprised and perplexed to find class-references,
like this to a custom CultureInfo-class in my "Localization.dll"-file:
<RegistryValue Root="HKCR"
Key="CLSID\{DB040F7E-5C7F-3735-BFBE-736D9FC76AB9}\InprocServer32\1.3.0.0"
Name="Class" Value="Localization.CultureInfoMoldova" Type="string"
Action="write" /> I'm definitely wondering why and if that's necessary. The
next thing that arose was that I discovered that it refers to versions of each
DLL. This is good, but it means I'm going to have to make this process
completely automated. There's no way I can keep up with manual upkeep of all
the version-changes. At this stage, I Googled my way to discovering there's
something called "MsBuild HeatDirectory", but I've not found a dummy-tutorial
on where and how to get it into my project. Moreover, I still don't know
whether I should do "Add Reference" to my EXE and DLLs or not. I'd appreciate
any answers to my curious questions and pointers on how to get that
HeatDirectory going. Please keep in mind I in spite of my long experience with
.NET feel like a complete tool and dummy with WiX. I am using Visual Studio
2010 and .NET 4.0. Once the WiX is completed, I am going to migrate it to
Visual Studio 2012 and .NET 4.5. I can't go to VS 2012 immediately as I need to
be able to provide a Windows Installer for our testing team, and 2010 gets that
job done while I slowly migrate to WiX. Best Regards, Tom
------------------------------------------------------------------------------
Try New Relic Now & We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, & servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr
_______________________________________________
WiX-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wix-users
