Hi Sebastian,
Thank you for your reply.
The snippet is:
Directory Id=TARGETDIR Name=SourceDir
Directory Id=APPLICATIONFOLDER Name=ViewPoint6
Some other folders...
Directory Id=SQL Name=SQL
Component Id=SQLFolder
Hi,
Have you tried to changing the IDs and Guids of the SQL folder and files?
Are there some other folder/files/components with the same Ids? (Should give
compiler warnings). Otherwise I'm pretty much in the dark about this. Maybe
the verbose log of the msi file can help.
Best regards,
Hi Sebastian,
Thanks for your tip. I tried to change the Ids and GUIDs for that weird folder.
And the problem is resolved! It can be copied to the defined the path.
It is really weird. But the problem is fixed by this way.
Cheers!
Chunyan
-Ursprüngliche Nachricht-
Von: Sebastian
Good morning all,
What a wonderful day it is here, a perfect day for some more installer
coding. Today's issue (along with yesterdays 2 issue that are still
driving me crazy) is whitespace, I have a maskededit control that takes
a numeric input as I need to force the user to input numbers only.
Hi All,
We need to install a MMC (Microsoft Management Console) snap-in on target
machine.. We have several products... So a if MMC is installed by some other
product on a machine we should not try to install it again...
I have wrote the below custom action to install the MMC
CustomAction
Hello,
Unfortunally it seems that only using a Custom Action can resolve Trimming
and most string manipulation issues. Fastest way would be a small vbscript
to change the property value.
Oh, we have some nice weather here too. Greetings from southern Germany. :-)
Best regards,
Sebastian Brand
In your installer, you should have it create the registry settings for
the snap-in instead of calling InstallUtil. Wix 2.0 has a schema
extension to do this. Then, you put the MMC in its own component that
is shared by both products. The Windows Installer will automatically
do reference counting
Thanks Brant Gurganus.
Can you provide some examples ... I am using WIX 3.0...
Thanks
Ranganatha
On Tue, Sep 29, 2009 at 5:36 PM, Brant Gurganus br...@gurganus.name wrote:
In your installer, you should have it create the registry settings for
the snap-in instead of calling InstallUtil. Wix
I'm in the process of migrating an installer that used to be built with Wise to
an MSI built with Wix.
I'd like for the new installer to detect and automatically remove old versions
of the product if present. Is there an easy way to do this? As far as I can
tell RemoveExistingProducts and the
Hello,
I'd recommend to following:
First, use a RegistrySearch or FileSearch to find the existing product
and installation path. The found value is stored in a Property.
Then, if that property is set (=old version exists), show a dialog to warn
the user. On that dialog run a Custom Action that
Thanks, that's very helpful.
Joakim Hårsman
Head of development, Profdoc Care
+46-8 440 93 78
http://www.profdoc.se
-Ursprungligt meddelande-
Från: Sebastian Brand (Instyler Software) [mailto:wix+us...@instyler.com]
Skickat: den 29 september 2009 15:23
Till: 'General discussion for
Darn it, and there is no other way to force users to enter numbers only
other than to use a masked input? Pretty poor that is, although all of
the things this installer needs to do should really be done by some sort
of configuration tool :(
Simon
Date: Tue, 29 Sep 2009 13:57:46 +0200
From:
Finally got it. There was probably a number of things, but it finally started
working when I
changed vs:helpf...@name to the name of the HxS file, minus the extension.
Rob
Rob Hamflett wrote:
Hello,
I'm trying to get some documents registered with Visual Studio but I'm not
having much
This sounds pretty harsh imho. :) I think it is indeed allowed to set
*user* settings during a per-user installation and even All-Users or
Default-User settings in a per-machine setting. If I remember
correctly, Microsoft Office is using the Pinning feature in the 2010
version as well.
That talks about how to prevent pinning as well as how to control
grouping. It isn't talking about how to make an application pinned.
Brant Gurganus
http://gurganus.name/brant
On Tue, Sep 29, 2009 at 9:52 AM, Gareth gmor...@serif.com wrote:
This blog suggests it should be possible. But I've
You'll have to stick with a custom action for that. To read a text
file, I'd just use VBScript to read the text file ( fso.OpenTextFile
(...).ReadAll ) and store it in a property (if it's a short text).
Otherwise it depends on your purpose.
Best regards,
Sebastian Brand
Deployment
Not sure of the terminology here, but if your checks are in the LaunchCondition
table, they execute in an indeterminate order:
Ref: http://msdn.microsoft.com/en-us/library/aa369752(VS.85).aspx
Specifically,
You cannot guarantee the order in which the launch conditions are
evaluated by
There is a crude native C++ custom action here (
http://wixml.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=263) called
Property Loader. It allows you to read and replace text in a text file.
However, it doesn't support rollback.
Thanks,
Brian Rogers
Intelligence removes complexity. - Me
Hi there.
I'm trying to create an installer that is divided into 3 features:
Framework, Client, Server. The first one is mandatory (and invisible)
the latter two can be combined or not according to the users choice.
Server contains a web application among others, like this:
iis:WebSite
They aren't using pinning, they are using the jump list capabilities.
That's different.
Besides, there was never a programmatic interface for adding to the
quick launch items. It just happened that the backing store for those
items was easy to reverse engineer.
Brant Gurganus
I ran into the same issue with our installer. If you include an IIS
element in the installer it always seems to want to configure it.
They way I got around it was to write a VBS script that cracks open the
MSI database after it is built and modifies the ConfigureIIS action to
be Conditioned to
You should set SKIPCONFIGUREIIS property to 1 in order to skip IIS
configuration steps. Thus, when your IIS-related feature is not selected by
user, set the SKIPCONFIGUREIIS property to 1. This will ignore any IIS-related
elements in your code.
Hope this helps.
-- Yan
I need to find out once the installer finishes running (which installs
the Crystal reports basic runtime) whether the Crystal reports Basic
runtime for VS 2008 was installed or not in? how do I achieve that in
WIX or custom action?
Thnx
khan
I'm still on WiX 2.0 and am not seeing this property there. Am I missing
something or is this only in WiX 3.x?
-Original Message-
From: Yan Sklyarenko [mailto:y...@sitecore.net]
Sent: Tuesday, September 29, 2009 12:08 PM
To: General discussion for Windows Installer XML toolset.
Subject:
So far you are following the component rules, but there is a known issue
regarding early removal in major upgrades and fusion/win32-sxs/gac
installations: http://support.microsoft.com/kb/905238.
You need to move the placement of the RemoveExistingProducts action to a late
placement. See
I checked the v2 final source and it is also in there, so it should work. I
didn't find it in the help file of either release, however.
-Original Message-
From: Chad Petersen [mailto:chad.peter...@harlandfs.com]
Sent: Tuesday, September 29, 2009 12:48 PM
To: General discussion for
26 matches
Mail list logo
