The design of the 'old' install would have to be changed to check for the
existence of the the new install, which is probably not feasible. I am not
aware of anything that can be done in this situation. It is part of the
price that is paid in transitioning from one design to a different design.
The extension DLL that you get from Neil's site is for Wix 3.7. It is not
needed if you are using Wix 3.8, as Neil integrated this very handy
functionality into wix 3.8 (and later).
I found that I always had to go back to the source for the wix I was using
(in your case wix 3.8.) and get th
Also, I would suggest that before you try to extend the UI, get you
bootstrapper working so that you can select either package from the command
line. Something like this (winging it without testing):
http://schemas.microsoft.com/wix/2006/wi";
xmlns:bal="http://schemas.microsoft.com/wi
I think it depends on the requirements of your application. For me I have
six different driver projects which I author from a single project (each)
and build either as a x64 or a x86 MSI package in my automated build script.
I use the same UpgradeCode for the two packages. In my Burn bundle I ch
In general, in your bundle you can define a Variable element as a string and
as Overridable=yes. Then pass the contents of the string variable to the
MSI using MsiProperty. The WixStdBA will pass command line entries that it
does not parse through to the BA.
Bundle.exe SomeVariable=M
In the wix toolset source download, at src\tools\WixTasks\wix200x.targets ,
in browsing through that file (and other similar .targets files) it lists
the various MSBuild Targets which can be "redefined". So when I was trying
to understand the wix build process I created a simple
EndPointsSequenceT
For the advice to be relevant you would need to post a snippet of code
related to your component. Mine looks like:
Also I found that Product/@Manufacture must match the name of the
Manufacture as defined in the INF file, and Package/@Manufacture can be
different.
--
View this message i
I used to do something similar to what you are doing, and also had issues
with build sequencing. In my case the wixlib had wxs code and was marked as
an x86 project. The msi project was a dual platform project in which I used
preprocessor to switch between building a x86 or a x64 project. It all
I have been for some time using an empty PayloadGroupRef to pull a Fragment
into my Bundle (when the items in the Fragment don't already have a xxxRef
object which could be used). I picked this idea up from some example posted
in this list and it seems to work pretty good. However today I came ac
While reading through the engine.cpp (and related) code, I modified my
implementation to provide a text file in the payload group, so that there
was nothing ambiguous (as there may have been by using the empty
PayloadGroup). (I also discovered the usefulness of reviewing the
bundle-manifest.xml fi
Interesting. Thanks for all your efforts!
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/PayloadGroupRef-to-import-fragments-Bundle-fails-tp7596356p7596364.html
Sent from the wix-users mailing list archive at Nabble.com.
I get this error when the output file (bundle.exe, msipackage.msi, or
library.wixlib, depending on the type of project) is open in another
process, like Orca. So for me it is not random. Is your build process
trying to do something with the prior version of the output file, as the
project is bein
I have been using:
Install when the variable is less than 5.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/V-C-2013-redist-detection-tp7596368p7596370.html
Sent from the wix-users mailing list archive at Nabble.com.
---
I have been using:
or
when it is detected as installed the variable is set to 5, so I install if
less than 5. Seems to work for me.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/V-C-2013-redist-detection-tp7596368p7596369.html
Sent from the
Bob; Thanks for the advice. Sorry for posting incorrect x64 code in the
first post.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/V-C-2013-redist-detection-tp7596368p7596376.html
Sent from the wix-users mailing list archive at Nabble.com.
I am using wix 3.9.721 and vs2013 (or vs2010).
When I build a project (without making any changes to the source files:
In the case of a MSI project there is no change to the output file.
In the case of a Bundle, the output file is updated, the ProductId changes,
but the version is the same as th
FYI
http://www.edugeek.net/forums/windows-7/140586-possible-issue-kb2918614-causing-overlapped-i-o-operation-progress-errors.html
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/SECREPAIR-CryptAcquireContext-Could-not-create-the-default-key-contai
Is the Component transitive. If not the condition is only evaluate when
product is installed.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Repairing-permanent-files-tp7596405p7596432.html
Sent from the wix-users mailing list archive at Nabble.c
Sign your bundle with an Authenticode Certificate. My antivirus also deletes
any unsigned executable, even one that I just completed. While there is an
option to release the bundle from quarantine, it still deleted it. It's not
really a Wix issue. Some antivirus scanners are also owned by the f
About a year ago, while using Wix 3.8 RTM and VS2010, building the default
bootstrapper project with minimal changes to define the manufacture and add
a MsiPackage to the chain, resulted in the Bundle.exe being deleted within
seconds of being compiled by Samantec Endpoint Connection. A False-posit
This thread also talks about issues with the August 12th Updates:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/SECREPAIR-CryptAcquireContext-Could-not-create-the-default-key-container-td7596414.html
--
View this message in context:
http://windows-installer-xml-wix-toolset.68755
Here is a tutorial on using a mba:
http://bryanpjohnston.com/2012/09/28/custom-wix-managed-bootstrapper-application/
The WixBA is used in the wixtoolset setup. So unlike the WixStdBA, it is
not packaged as a module that can be included in your project. It is
specific to the needs of the Wixtools
Microsoft has acknowledged some of the issues related to the August 12th
Update, and in "some" cases advised folks to uninstall certain of the
updates in the August 12th release. I did not see any specific instruction
from Microsoft about this particular KB. I suspect it would be best to
contact
Just to clarify I don't have any connection to Microsoft or any expertise on
the subject. Just passing on observations gleaned from Googling.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Issues-with-Wix-Installer-per-user-minor-upgrade-tp759644
This may also be helpful
http://www.wrightfully.com/part-1-of-writing-your-own-net-based-installer-with-wix-overview/
And there is a book on the wixtoolset.org site which I think has information
on mba development.
--
View this message in context:
http://windows-installer-xml-wix-toolset.68755
If you go to https://github.com/wixtoolset/wix3 and click on Download you
will get a zip which has a name of wix-.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Cannot-view-RootView-xaml-file-in-visual-studio-2010-tp7596500p7596574.html
Sent from
If I collect a password in my mba, I am wondering what the best way is to
pass it down to the MSI. I considered calling the win32 Crypt API to store
the password (and then have the MSI retrieve the password from the store),
but if a mba should not change the system, what is a secure way to pass th
Thanks Rob, very much. I had the Bundle/@Variable hidden but missed the
Product/@Property. Thanks again.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-to-MSI-Secure-password-Best-Parctice-tp7596576p7596578.html
Sent from the wix-users mail
Thank you. I will look at that. I have not actually done any of the mba
implementation yet as I have been focused on the underlying Bundle/MSI
behavior, and getting the ServiceInstall and XmlConfig pieces figured out.
--
View this message in context:
http://windows-installer-xml-wix-toolset.6
You might want to look at this recent thread.
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/V-C-2013-redist-detection-td7596368.html#a7596373
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-FileSearch-in-64-bit-system-folder-t
Review this (one of several) threads:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/SECREPAIR-CryptAcquireContext-Could-not-create-the-default-key-container-td7596414.html
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Has-KB291861
We also target 2012R2 with Burn setups and the message "System restore
disabled, system restore point not created." is common in successful logs
with no other failures.
I notice that you have posted this message multiple times. Maybe you could
collect more details or post a complete failure log
I am not an expert and am still learning this topic, but I think it boils
down to:
In the "main" bundle preemptively add a line like:
In the future add-on, update, or patch, (as indicated) add this to tell it
that it is related to the main product.
I also set Bundle/@Tag to a unique string in
Rob's advice was to use a "Related Bundle" , which would involve creating a
bundle.exe for each "addon", and using the RelatedBundle element in each
Bundle to establish the relationships. If you use 'Related Bundles' Burn
does a lot of work for you tracking not only the install but the uninstall
p
I would appreciate advice on deploying applications that support multiple
cultures. I am using a Bundle with many none-UI MSI packages for various
applications in my product 'suite' (bundle.exe). I currently build the MSI
packages and use the process described below to embed language transforms
i
This thread might help.
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Suppress-options-in-bundle-td7586507.html
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/How-to-disable-Options-button-on-Bootstrapper-tp7596895p7596897.html
Sen
>>I think Bob would say use language packs.
I am a little confused by this comment. The translated strings in the
current .mst are for things like localizing various MSI error messages
(down-version and CA) and to localize descriptions related to installed
shortcuts and services (on Windows reso
Thank you for the assistance.
Phill
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Deploying-multiple-cultures-using-Burn-MSI-s-Wix-3-9-issue-tp7596896p7596918.html
Sent from the wix-users mailing list archive at Nabble.com.
-
For cases where the package should not be uninstalled use
XxxPackage/@Permanent='yes'.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/32-bit-vs-64-bit-prerequisites-and-DetectCondition-and-InstallCondition-tp7596909p7596919.html
Sent from the wix-
I did not tackle this issue yet, but I also need to come up with a way to
generate a build report (or design documentation). I was thinking that one
piece of this, as it relates to bundles, might be to try and make use of
info in the bundle manifest file, which I noticed in the temporary folder,
w
Tobias, that is the approach which I use, embedding the language transforms
and setting MsiProperty TRANSFORMS=:langid.mst. I thought that I had tested
this successfully several months back when using Wix 3.8, but now I am see
two problems documented above. Once installed, say with the German
:10
My understanding of MSBuild is that it will only fire a Target once.
http://msdn.microsoft.com/en-us/library/ms171462.aspx
So I create a Target with a custom name and place a HeatDirectoy task in
that target. Then I repeat that process creating a custom named Target to
include each HeatDirectory
The Chain is evaluated from top to bottom when doing an 'Install', and in
reverse order (from bottom to top) when doing an uninstall. Typically I
just let Burn manage these details.
Yes you can create a custom BA (or with WixStdBA use a BAFunctions.dll) and
override the various Plan (and other ev
That is what I use (and I also use /norestart). I don't have MSUs, just
MSIs, but they now uninstall consistently. Many months ago when I first
implemented this I saw situations where the packages were not removed. I
think that happened when I tried to call the cached version of the bundle
(usin
The chm for the Component element implies that you are correct, but warns
against doing that, as I understand it.
"If KeyPath is not set to 'yes' for the Component or for a child Registry
value or File, WiX will look at the child elements under the Component in
sequential order and try to automati
Using a Burn driven MSIs, without using language transforms, results in MSI
packages, of the same name, in a culture named folder tree. I have also
been evaluating using external cabs for the common files. From what I have
reviewed the cab gets created in the MSI output folder (or subfolder below
If you are using a Burn based bootstraper, it generates log files in the
users temp folder (%temp%) using the msi package name, which I believe you
could override in an mba, but I have not had the need to do that.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.
Regarding the general issue of long build cycles, I found that I could
decrease the build time by making sure that each MSI project will
incrementally build. The use of wixlibs for code common to MSI packages and
common to bundles also helped the build process. I make sure that the
bundle is buil
Use the Binary element.
The wix source download has the source for several wixExtensions, and
studing the structure and appraoch taken to create those extensions was
helpful as I moved my IS projects to WiX. Also there is the WiX contrib
project (https://wixcontrib.codeplex.com/) which was helpfu
I would take the last approach. The other suggestions are not viable so far
as I am aware. I have a 3rd party msi for which I chain a pre3rdParty msi
and a post3rdparty msi for similar reasons, so it is certainly possible to
do your last suggestion, depending on your details.
--
View this mes
I tried to create a transform, but in my situation I ran into the limitation
that a transform can only modify information in persisted tables.
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/torch-create-transform-td7594463.html#a7594624
--
View this message in context:
http://w
Interesting. Thanks for the suggestion. I will look into it.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Using-external-cab-for-multiple-language-msi-packages-tp7596991p7597117.html
Sent from the wix-users mailing list archive at Nabble.com.
Phill Hogland wrote
> I'd do it this way: Set cab cache path to a common directory then let
> wix.targets do its thing. Then assemble a new image you use to build the
> bundle from.
Bob;
I am currently using in each MSI project the following:
cabs
True
along with:
Hi Bob and group;
Using Media/@Layout I achived a folder structure like this:
Release\cabs\mycab.cab
Release\culture1\mymsi.msi
Release\culture2\mymsi.msi
The cab is being signed by the MSBuild SignCab target but then I get
Insignia error INSG0258 cab file not found in culture2 folder.
Also whe
Hey Bob, thanks a lot for responding to that old post. I finally understood
what you were saying and got it working. I was tripping over an impression
I had inferred from other threads to the effect that the msi file name could
not/should not be changed after it was signed. I was also getting co
I am looking for advice on how to use Lux and Nit. I have read the chm docs
and the two posts to Joy of Setups. I have also reviewed the sample
projects in the source and looked at the lux related targets in the source
code. I have tried several approaches to using Lux without success, so I
crea
I stripped everything out of my 'product' project except what was necessary
to do only the first test in the Simple sample.
Since building in VS2013 with the Target "Test" fired after the Target
"Build" results in the invalid SQL error in Nit, I create
I recently implemented a very similar authoring and I do not have any problem
doing a Repair. The one difference I noticed is that I am using
StartControl/@Remove='uninstall'. I have not tried to set it to 'both' but
removing the service while doing an install does not seem to be what I would
wan
Te report of Nit failing, above, is when I added the 'Test' target to my main
project without adding any Lux specific commands. So while the verbose
MSBuild log that I posted showed that it tried to collect the UnitTest wxs
and compile them, it did not run the linker and produce a different MSI
pa
I see that I still have the -ext WixUtilExtension on the above candle
command. I removed it but Light still fails saying that 'User' Table is
not defined. I can't find anything else in my project related to the User
table. When I first started this project I added a reference to my PkgLib
in wh
IIRC that is the message which you define in the
MajorUpgrade/@DowngradeErrorMessage in the msi package.
There are other options to MajorUpgrade which do not display a message if
you do not want a down version to fail.
--
View this message in context:
http://windows-installer-xml-wix-toolset
I don't know if this comment relates to your concern, but, after some
experimentation, I have interpreted the last paragraph in Remarks, at the
following link to indicate that my Icon/@Id should be formated with an
extension which is the same as the file which the shortcut targets. So even
though
I have a chain of Burn driven MSIs. I implemented a MSILOGGINGVALUE property
(and related variable which Burn initializes and the mba overrides). If the
MSILOGGINGVALUE property is provided to the package I do a conditional
SetProperty action on MsiLogging, scheduled after LaunchConditions. But
Thank you for the feedback John and Bob. I appreciate it.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Use-of-MsiLogging-in-Burn-driven-MSI-tp7597242p7597253.html
Sent from the wix-users mailing list archive at Nabble.com.
Thanks for the info.
I started over with a new VS2013 msi setup template project. I added code,
essentially from Rob's remember property pattern post, and then used the
same command line file I shared earlier. I now get further down the path
successfully producing the xxx_test.msi (and not seein
I would appreciate advice on how to make our Burn driven MSI downloads more
reliable. I have a Burn/mba driven multiple MSIs (100+), most of which have
external cabs. Most testing of this of this setup results in successful
installation although one remote tester is reporting a high download fail
Thank you for the information.
What are the drawbacks or risks of using bits:// protocol?
We target Windows 7/WS2008R2 and later with MSI ver 500, using WiX 3.9.1006.
I changed the 90 Mb cab file to use the bits:// protocol and I have not been
able to reproduce the failure in my tests since that
The msi package has to target either x64 or x86 and directories used in the
package need to derive from a MSI defined root folder which has correct
bitness. You can use Burn to chain x64 MSI package to install native files
with a x86 MSI package to install the 32 bit code. (In my case the driver
Thanks, I have been using Fiddler, and have not seen any of the payload
download activity.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Addressing-download-failures-in-Burn-driven-MSI-tp7597272p7597332.html
Sent from the wix-users mailing list a
I have noticed that when I use -?, -h, or -help with my mba bundle, these
parameters are stripped by Burn prior to returning
Bootstrapper.Command.GetCommandLineArgs(). Yet using these switches with
burn.exe or with my bundle.exe does not result in displaying a list of the
built-in command line swi
Thanks for the resource. I found that I can use
Environment.GetCommandLineArgs to get the -? switch.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-GetCommandLineArgs-tp7597351p7597354.html
Sent from the wix-users mailing list archive at Nab
Thanks
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-GetCommandLineArgs-tp7597351p7597360.html
Sent from the wix-users mailing list archive at Nabble.com.
--
Compre
Thank you. Maybe this is a different topic, but what is a pseudobundle and a
passthrough, as in Command.Passthrough object? pseudobundle.cpp talks about
passing the command line to a passthrough bundle.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble
I have continued to research this issue (between local network disruptions).
While I have done many experiments to try and understand a rare download
failure of a 90mb payload cab file, I have focused on Rob's comment about
Burn's use of http being reliable 'with retries' (in contrast to BITS). I
I have both issues figured out, by adding retry/TryAgain processing to
CacheAcquireComplete, CacheVerifyComplete, and CachePackageComplete.
Thanks for the assistance.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Addressing-download-failures-i
There are many factors and opinions on this issue.
I try to make sure that my MSI projects can build incrementally (if nothing
was changed).
I use MSBuild command line scripts (customized with ITask and Targets) to do
most builds, rather than VS (used for development debugging)
I minimize use of
http://www.youtube.com/watch?v=JLXwwqHhvvA
3.9.1006 is RC (4 I think)
http://wixtoolset.org/releases/v3-9-1006-0/
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Re-Auto-Updater-tp7597527p7597531.html
Sent from the wix-users mailing list archive a
I have noticed recent discussion among the devs about Compression level and
setting the level to -dcl:none for debug and -dcl:high (or some other
setting) for Release builds. I also read through as many posts about
compression as I could find in the archives and generally on Google. I have
experi
Running scripts is not recommended and using InstallService should be avoided
from what I hear. (I am relatively new and don't claim to be an expert.)
I would look at the script and figure out what it is doing, then use the
equivalent wix elements to install the service. Something like this:
The video provides information about the plan to release wix 3.9 on halloween
weekend (if there are no significant issues raised).
I assumed you are talking about the work that Jacob did to implement the
download behavior, which has been in the wix source Setup\WixBA
UpdateViewModel, since at le
Is the discussion possibly confusing the use of the HarvestDirectory target
(called in the Wix build process) and the HarvestDirectory task (which I
also call from a custom target which the BeforeBuild target depends on, as
some blogs suggest)?
--
View this message in context:
http://windows-in
The following link was helpful to me:
http://stackoverflow.com/questions/2772452/how-to-associate-application-with-existing-file-types-using-wix-installer/2808320#2808320
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Ways-to-Initiate-Self-Repair-
Specifically I add the following to the same component as my to get the file associations to be advertised.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Ways-to-Initiate-Self-
Brian the Wix documentation defines both a "HeatDirectory Target" and a
"HeatDirectory Task". I have only used the "HeatDirectory Task" (from
within BeforeBuild) in part because I call the task more than once to get
different source folder trees.
When doing a wix build with VS logging set to Diag
I use something like this (without the condition, but that could be added, in
which case I would also make the component transitive):
http://schemas.microsoft.com/wix/2006/wi"; />
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.n
When a file association is created, and the app is installed properly, in the
case of the Open verb, when a user double clicks on a file with that
extension, the shell launches the registered application and opens the file.
If the file association is advertised, and the application is not installe
No. It smells wrong but that is what you need to do for a per-machine
installation.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/perMachine-optional-shortcut-creation-tp7597616p7597621.html
Sent from the wix-users mailing list archive at Nabble
I did a little more research into this observation (that using -dcl:none and
-dcl:high (or low, or no switch) all produces the exact same size output
files (msi and related external cab files)). Since these experments were in
part prompted by reading Bob's blog and the dev's discussions
(http://ww
Based on the following document (and probably other pots to the forum, long
ago) I had implemented cab reuse.
http://wixtoolset.org/documentation/manual/v3/howtos/general/optimizing_builds.html
The cause of the problem detailed in this thread is that I had defined a
single cab cache path without c
I do not think that the files were different, since I did a "debug" build,
and then a "release" build as soon as the debug build was finished (without
any change to the source tree). Even though the Release build was set to
use high compression, it reused the cab file (when the path is set to a
co
Well I guess my last observation is not correct when I both delete the cabs
folder and the bin and obj folders. The property in an imported target is
used by msbuild launched on the command line to build a project (without
defining the properties using the /p switch).
--
View this message in co
Would it be a better approach to define a wixlib for the 'library' files and
use the wixlib in each msi package which requires the library, so that each
msi package is atomic from msi's perspective? Then on-demand install of
advertised features would be complete.
--
View this message in contex
I would look at the WixStandardBootstrapperApplication in the wix source
code.
src\ext\BalExtension\wixstdba
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Guidelines-Tutorial-for-Bootstrapper-in-native-C-tp7597671p7597677.html
Sent from the wix-u
I also congratulate everyone for the wix 3.9 release.
In my decades of working with Installshield, it would create a backup of the
project file, but more times than not also introduced breaking changes that
prevented my projects from compiling until I tracked down all of the
changes.
In my work w
I have large DVD size setups authored in Installscript, which I am converting
to wix. I have moved most of the applications to individual msi packages,
batch built in seven languages, with external cabs. These packages are used
in multiple bundles for different types of product configurations (cl
It seems to me like the roll of burn and msiexec as it is related to the
MajorUpgrade element is confused in this and related threads. AFAIK candle
compiles the MajorUpgrade element and the MajorUpgrade/@Schedule into the
msi package which is parsed by msiexec at installed time without any
involve
I agree with Jacob's recommendation that writing a mba to display your UX and
hide or don't implement the UX in each msi (or exe prereq like VC) is much
prefered. This approach works great and is much better than fighting the
intended design of burn. The wix source includes a good example (though
Regarding using BAFunctions.dll for DelayStart, it has been about a year
since I used that feature and then abandoned that code in favor of creating
a WPF managed BA (which I would also recommend, but you could use any UX
framework - MFC, WCF, Java?). But as I recall the basic steps are:
1) Define
The wix elements use the msi standard tables for things like installing
services and registry entries. This provides a better user experience,
including rollback support, in contrast to calling an open ended external
process like myservice.exe --install. Most of the information needed is in
the l
I also deploy both x86 and x64 packages in my bundle. To clarify the use of
preprocessor statements in your code snippet would cause the pre-compiler to
include only one of the two code fragments at compile time. Probably not
what you want.
You can create two separate MSI projects for you applic
401 - 500 of 790 matches
Mail list logo
