I'm in a similar situation with close to 30,000 files to deploy of which
perhaps 50 - 100 are DLL's, EXE, OCX etc.
I've ended up grouping files together in a component, (with the exception of
DLL's etc) sometimes up to 5,000 or 6,000 in one component. I also forced a
version number for each
Interesting
Windows 8 say's (ocsetup /? ) OCSETUP has been deprecated. Please update your
scripts to use DISM.exe to add or remove optional components from your system.
I see this being a serious problem in deploying software timeously, before I
could just install the .NET Framework, now
I think this probably sums it up, fail deployment until the .NET Framework 3.5
is installed, or deploy without it and rely on the shim prompting for
installation.
http://msdn.microsoft.com/en-us/library/windows/hardware/hh975396.aspx
Neil
I have an installation which has the .NET Framework 3.5 etc. as prerequisites.
In the past I've been able to install the .NET Framework by calling the
redistributable package.
What is the correct approach for Windows 8?
Most of my target market does not have internet connectivity. IT
After the discovery of the variable WixStdbaThemeXml from this mailing list I
set about looking at my own corporate theme. In my main wxs I set these two
variables:
WixVariable Id=WixStdbaLogo Value=Background.bmp /
WixVariable Id=WixStdbaThemeXml
=myfile.dll)
If I do have to create my own bootstrapper dll has someone got a simple example
anywhere.
I'm so close to finishing this test project..and I want to start on the
real thing!
Neil
Neil Hayes
Software Development Specialist | SYSPRO - South Africa
Phone: +27 (0) 11 461 1000 | Fax: +27 (0
6 matches
Mail list logo