I am trying to use a merge module for msvcr71.dll since its strongly
recommended to use merge models for re-distributing c runtime libraries.
But i want to copy this msvcr71.dll to 2 different folders on installation.
But using the same merge module reference twice would cause the same file to
be
Doesn't the merge module install the file to the Windows system folder? If
that's the case then you
shouldn't need to install the file anywhere else.
Rob
On 14/01/2010 09:16, ricky sundrani wrote:
I am trying to use a merge module for msvcr71.dll since its strongly
recommended to use merge
Hi,
Is it Possible to configure DCOM component security issues?
Thanks,
Leo Kushnir
http://blogs.microsoft.co.il/blogs/leokushnir/
--
Throughout its 18-year history, RSA Conference consistently attracts the
world's
Yep, my mistake. Was looking at a package in InstEd! at the time
forgot about Itanium platform support as it still shows only AMD64 for
the x64 platform where as Orca has both AMD64 x64 IIRC (haven't
had it installed in a long time so I might be wrong).
Palbinder Sandher
Software Deployment
Directory Id=TARGETDIR Name=SourceDir
Merge
Id=msvcr71dllLanguage=1033DiskId=1SourceFile=My_MSM.msm /
/Directory
FeatureId=ProductFeature1Title=MergeMod321Level=1
MergeRefId=msvcr71dll/
/Feature
That is all you should Ricky need assuming you're using the VC++ 7 merge
The merge module i am using is installing the msvcr71.dll in the directory
where i am puttin the reference to the merge module.
Using the above code ,it installed it in Folder1. So maybe i am not using
the correct msm.
I'l look into it,
Thanks
On Thu, Jan 14, 2010 at 5:16 PM, Pally Sandher
Supoosing the MSM is some custom msm with one just one component and one
file.
like
Directory..
Component
File
File/
Component/
Directory/..
Now if i use the above code then too i can't use it.
Merge Modules are for code re-usability, But using the same merege module
twice within the
The following string format was not expected by the external UI message
logger: The Windows Installer Service could not be accessed. This can
occur if you are running Windows in safe mode, or if the Windows
Installer is not correctly installed. Contact your support personnel for
assistance..
Until Burn is feature complete I'd recommend looking at dotnetinstaller
(http://dotnetinstaller.codeplex.com/). Been using it for a while now
it's quite easy to configure build in my experience.
Palbinder Sandher
Software Deployment IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 141 945
Not sure if it is that straight forward. I think the reason we keep punting
this feature is the dependencies heat.exe has on the Wix core project (
http://sourceforge.net/tracker/index.php?func=detailaid=2012626group_id=105970atid=642717
).
Brian Rogers
Intelligence removes complexity. - Me
Yes, please file a bug. This is a good thing to track.
Thanks,
Brian Rogers
Intelligence removes complexity. - Me
http://blogs.msdn.com/icumove -- NEW
On Wed, Jan 13, 2010 at 5:28 PM, Bob Arnson b...@joyofsetup.com wrote:
On 1/13/2010 4:35 PM, Neil Sleightholm wrote:
I think there is a bug
Regarding the ICE38 errors, it sounds like the directory your Component
is under is a per-user location. Try moving the Component to a
per-machine location like SystemFolder (even though you're not writing
any actual files or folders to the location in your Component) if it's
not there already. If
Are you sure about that WinSxS location? I believe the 7.1 merge modules will
install the Dlls in the user's application folder. I don't think they went
WinSxS until Visual Studio 2005.
Phil Wilson
-Original Message-
From: Pally Sandher [mailto:pally.sand...@iesve.com]
Sent:
That worked perfectly. Thanks very much!
Directory Name=SystemFolder Id=SystemFolder
Component Permanent=yes Id=ProgramRegUpdate Guid=...
RegistryValue Root='HKLM'
Key=SYSTEM\CurrentControlSet\Control\Print\Providers
Type='integer' Action='write' Name=EventLog Value='7' /
There is a link:
http://support.microsoft.com/default.aspx/kb/326922.
What is currently being followed for msvcr71.dll ? WinSxS or application
folder. ?
Also if someone could please help me with the merge module code..
About using the same merge module in the code twice in order to distribute
it
Does/will the UI for Burn allow me to let the user select products they wish
to install? For instance, if we distribute SQLExpress with our sysrem, can
I allow the user to select installing both or one of the components?
Also, is Burn mature enough to start using for a new new project?
Hi all,
I've got a app that is written in .NET. To function correctly it needs to
access the registry. On a 32 bit system this is trivial. On a 64 bit system it
needs to be run as a 64 bit app (installed in Program Files) in order to access
these bits of the registry.
But the .NET code
Hello all. :)
I'm new to this list and have been reading for a couple of days now.
Seems you folks deal with some pretty complex issues surrounding WiX so
if you know of a more appropriate venue for my n00b questions, please
just let me know. :)
Before I jump in with my questions, here's a
We have an automated build that runs continually. We'd like each MSI produced
to behave as a major upgrade so that we can apply any newer MSI on a target
environment easily. Our build process fixes the first two parts of our version
numbers to predetermined values and allows the remaining two
Well there is no currently, they are what they are, and that kb article says:
For Msvcr70.dll or for Msvcr71.dll, you should install the CRT DLL into your
application program files directory. You should not install these files into
the Windows system directories. For Msvcr80.dll and for
I would think that as long as the ProductVersion, the ProductCode and the
PackageCode changes and the Upgrade table contains the versions to be upgraded
in the Min/Max version fields, it should act as a Major Upgrade.
Matt Walker
Installation Development
200 Kelly Road | Quakertown, PA 18951
I'm sorry my search skills are failing here; I'm sure this is a common
question.
Is there a way to conditionally set the InstallScope attribute based on
passing a property in on the command line?
--
Throughout its
Done:
http://sourceforge.net/tracker/?func=detailaid=2932337group_id=105970;
atid=642714
Neil
-Original Message-
From: Brian Rogers [mailto:rogers.br...@gmail.com]
Sent: 14 January 2010 16:55
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Heat Bug
Welcome!
1) You will need separate 32 and 64-bit installers.
2) Starting from scratch will definitely be easier :)
3) If you're starting from scratch, just don't add a UI.
Hope that helps get you started..
On Fri, Jan 15, 2010 at 6:07 AM, Vern Graner v...@txis.com wrote:
Hello all. :)
So, I've got this code that lets me know if certain databases are installed or
not:
function CheckDatabase(serverProperty, databaseProperty, checkProperty) {
var serverName = Session.Property(serverProperty);
var connectionString = Provider=SQLOLEDB;Data Source= + serverName +
I'm getting the following error from light:
error LGHT0204: ICE61: Upgrade.VersionMax 3.3.34567.0 format is wrong
The ProductVersion Property documentation
http://msdn.microsoft.com/en-us/library/aa370859(VS.85).aspx tells me that
the first three fields have the following maximums: 255, 255,
Have you tried it without the .0 at the end?
Best regards,
Sebastian Brand
sebast...@instyler.com
Geisenfelder Str. 53a
85053 Ingolstadt, Germany
EU VAT ID: DE219712370
Phone: +49 841 4544567
www.instyler.com - Instyler Setup: Create WiX-based MSI installations,
elegantly.
www.traveladdin.com -
just a hunch, can it be that the ICE is (wrongly) using a signed 16-number
for the third field?
On Fri, Jan 15, 2010 at 5:22 AM, Castro, Edwin G. (Hillsboro)
edwin.cas...@fiserv.com wrote:
I'm getting the following error from light:
error LGHT0204: ICE61: Upgrade.VersionMax 3.3.34567.0
Reposting this question :
Is it possible to use the same merge module twice in the same source file.
Directory Id=TARGETDIR Name=SourceDir
Directory Id=ProgramFilesFolder
Directory Id=MergeModuleSample Name=Merge Module Sample
Directory Id=INSTALLDIR Name=Merge Mod32
Just tried building with 3.3.32767.0 and with 3.3.32768.0.
3.3.32767.0: No errors
3.3.32768.0: error LGHT0204: ICE61: Upgrade.VersionMax 3.3.32768.0 format is
wrong
Looks like an incorrectly implemented ICE. Can I exclude ICE61?
Edwin G. Castro
Software Developer - Staff
Electronic Banking
FYI: I found that light.exe has a -sice:ICE argument.
Are the ICE distributed by WiX owned by WiX? Do I need to add a WiX bug?
Edwin G. Castro
Software Developer - Staff
Electronic Banking Services
Fiserv
Office: 503-746-0643
Fax: 503-617-0291
www.fiserv.com
Please consider the environment
Hi All,
I have created an installer with Wix for one of our products. It works
very well and in general I am happy with it.
However there is one small niggle that I haven't been able to solve
myself - when installing (I always do major upgrades) the installer
detects a file in use by another one
32 matches
Mail list logo
