FWIW I created a Release config for wixstdba by copying the Debug config and
then making obvious changes like removing _DEBUG and DEBUG symbols and
turning on optimization. It appears to work fine with the limited testing I
did.
--
View this message in context:
http://windows-installer-xml-wix-to
Rob, your response inspired me to modify wixstdba to add the logging feature
I wanted. I was able to do this and removed the need for custom actions in
my MSI's and forcing all my XP users to upgrade to Windows Installer 4.5.
I've posted the code change to wixstdba below for comments and criticism.
0. If your product does not need the .NET Framework then by all means do
not install it just to write a managed BA. You can just as easily (assuming
you are already writing native code ) write a native BA, just like
wixstdba.
1. I don't necessarily agree. We added support for creating managed BA's
I was aware that "The mba (Managed Bootstrapper Application) can install the
.NET
Framework *before* your managed BA comes up. That's actually howthe WiX
toolset works. Install it on a machine with out .NET Framework and it will
first install .NET Framework then launch the custom BA. " There is
res
1. The mba (Managed Bootstrapper Application) can install the .NET
Framework *before* your managed BA comes up. That's actually howthe WiX
toolset works. Install it on a machine with out .NET Framework and it will
first install .NET Framework then launch the custom BA.
However, I must say, I don't
In reply to Rob's points:
1. I knew about the Burn log file Variables and link on the failure page.
Since I'm new to both Windows Installer and WiX, I was hoping to avoid the
need to write my own bootstrapper just to control logging. I may be
installing to XP machines without .Net installed so I w
1. Burn provides Variables to the paths to all log files, including it's
own log file. For example, the wixstdba code uses the Variable to provide a
link on the failure page. Your BA could do other things.
Note: the log filenames from a Bundle are designed to be pretty
self-explanatory and are sto
I've found a number of topics about log file location and some topics about
logging detail levels by searching the mail list and the bug tracker. I still
don't know how to get logging working the way I want so here we go again.
The Windows Installer properties that interact with logging are
Msi
8 matches
Mail list logo
