Hi All,
As menioned in a previous mail out, I was wondering if there was any
comunity support on SQL Server Reporting Services (SSRS). In our
organisation Reporting Servies forms a pretty big part of the picture of
our products and so a deployment method is required for these artefacts.
Idealy w
Thanks for your answer. Yes I am getting the browse dialog, asking for
the msi file that was used to install the software. So that's the
exepected behavior.
Andreas Hellwig
Wilson, Phil schrieb:
> MSI doesn't cache the entire MSI file - it discards the embedded CAB file -
> so to check or rei
Alex Goryuk wrote:
> Can someone point me to the following English strings?
>1. !(loc.msierrXmlConfigFailedRead)
>2. !(loc.msierrXmlConfigFailedOpen)
>3. !(loc.msierrXmlConfigFailedSelect)
>4. !(loc.msierrXmlConfigFailedSave)
>
They're provided in WixUtilExtension. You need to p
Ryan O'Neill wrote:
> The problem is that I want to ensure that the Spooler service is running
> before I do any printer manipulation as some of the API calls need that
> service running. I don't know how to have two sets of StartService.
>
You can't -- actions can be scheduled only once. Gener
Demented Devil wrote:
> Now banging my head against the wall - for some reason my embedded wixlib is
> not being attached to the msi file being compiled even though my extension
> dll is being used (ie: I've got a GroupEx table in my MSI as expected but
> the custom action fragments are missing - w
Wouter Demuynck wrote:
>
> http://schemas.microsoft.com/wix/2006/wi";>
>
>
>
>
>
>
One possibility is that the !(wix.id) uses aren't enough to reference
the WixVariable definitions in the library. Try this: Add a Property to
the li
I learned a few years back not to change my upgrade code, unfortunately a
little too late. The good news is that I only changed it once. My current
WiX source is:
...
And what I'm seeing is that version 3.0.0.1 and later is being upgraded
properly, but prior ver
I have followed the example as given here.
http://www.dalun.com/wix/05.22.2007.htm
I have the path of .net assembly coming from the configuration xml.
but when I concatenate as follows I get an error.
-
Check o
I wanted to make an upgrade package. my code is given below.
i still get the message when running the msi "another version of this
product is already installed" with an OK button.
-
Check out t
Hi,
I posted this last week, but now I've discovered some more information and
hopefully someone will be able to help now :)
I've created a fairly straightforward installer apart from some CustomActions
and one custom dialog.
The first installation goes fine, and the uninstallation appears to (
Ah, I see that now. I saw your reply and realized the part of the question
that I missed. I've actually done a lot with persisting data across sessions
over the years as I am not a beleiver in `configuration data is a pain`. :-)
I've even been known to tie into custom AD schema extensions to
>> maybe I'm missing something but the constructor choices for the
>> CustomActionData class could probably be a little better. The
>> CustomActionData property is always `CustomActionData` so maybe there should
>> be an overload that takes the session class as an argument and automatically
>>
It would have helpe if I read the entire question. :-)
For persisting Data I take a multiple step approach that allows considering all
the modes an install will run including interactive with custom dialogs for
setting values and silent installs for passing values in. The idea is the
priority
Session.CustomActionData is primarily meant for passing data from immediate to
deferred CAs.
DTF doesn't currently provide a built-in mechanism for persisting state across
install sessions, though that might be a nice feature to add.
For now you'll need to stash the data either in a registry ke
If you wire up an installer class CA in VDPROJ and edit the resultant MSI in
Orca you'll see that you are actually getting 2 CA's for each CA. Was is a
Type 51 CA that's setting a property with the same name as the second deferred
CA. This is the serialization of properties that the installc
I have inherited some WIX code (ie I am a newbie) and have moved the managed
custom action over to DTF (which is very nice BTW).
Previously the CA did something along these lines:
public class MyInstaller : System.Configuration.Install.Installer
{
public override void Install(Sys
Can some one explain how file version numbers relate to patches? My
original file version number is 5.10.1040.08 and the new file version
number is 5.10.1040.09 and the patch did not make any changes. If I
change my new file version number to 5.10.1041 the changes take. This
is confusing to me s
Hi,
I have design question for community.
My application has one common dll (common.dll) and two exe
applications, where both of them depend on this common dll.
Could someone suggest me when I need use minor/major upgrade/patch for
each scenario that follows:
1) My group release new version e
Or you can use the fact that your newly created element does not have attribute
yet:
//ParentNode/ChildNodes/ChildNode[\[]not(@Name)[\]]
Alex
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ryan Perlman
Sent: Monday, June 16, 2008 11:12 AM
To: Gener
I've contacted Bart.. He happens to work just one building over from me. We're
going to meet this week to discuss possible future collaboration on LINQ to MSI.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Christopher
Painter
Sent: Saturday, June 14, 2
You could also use XmlConfig.
>From an xpath point of view you can use something like so in your XmlSetting2
>which would get you the 3rd child element.
"//ParentNode/ChildNodes/ChildNode[\[]3[\]]
Ryan
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
Hi,
Can someone point me to the following English strings?
1. !(loc.msierrXmlConfigFailedRead)
2. !(loc.msierrXmlConfigFailedOpen)
3. !(loc.msierrXmlConfigFailedSelect)
4. !(loc.msierrXmlConfigFailedSave)
Apparently they are only translated into en-US, as part of
WixUtilExtension.dll,
Steps 1 and 2 can be done in the custom action scheduled before AppSearch.
Step 3 can be done by AppSearch.
Alex
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Natxo Mateos
Sent: Monday, June 16, 2008 5:04 AM
To: wix-users@lists.sourceforge.net
Subjec
>Can you explain what you mean by "proper GUIDs"?
>I wasn't aware that Votive was generating bad GUIDs.
GUID data type (http://msdn.microsoft.com/en-us/library/aa368767(VS.85).aspx)
requires GUIDs to be all upper-case:
" Note that utilities such as GUIDGEN can generate GUIDs containing lowercase
Definitely. I've seen this issue come up more than a few times There seems to
be a common perception that binaries generated with different versions of
Visual Studio C++ can all use the same version of the runtime support, but
starting with VS.NET they're all unique.
Phil Wilson
-Original
This has been answered on the mailing list before. Search for "Removing
Install to Run From Network Feature Option". This happens when a
feature only has sub-features and not components.
-Brian Simoneau
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Da
MSI doesn't cache the entire MSI file - it discards the embedded CAB file - so
to check or reinstall files it needs access to the original installation source.
However, you should be seeing a browse dialog asking for the source. If you're
not getting a browse dialog, that message you're seeing i
Update regarding #4: CA build behavior relating to GAC assemblies should be
much better after a fix in the latest build 3.0.42140.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jason Ginchereau
Sent: Monday, June 09, 2008 10:15 AM
To: General discussion
I've got a set of features that I moved under a new parent feature, and the new
parent feature has a pair of options that A) don't make sense and B) I don't
want... but I don't see how to disable them in the v3 schema. They only appear
for the parent feature when it has children; other features
Try: msiexec /a package.msi TARGETDIR=C:\users\volker\test\
Jim
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Volker
Enderlein
Sent: Monday, June 16, 2008 2:59 AM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] How to forc
Hi,
I have a little problem with the installer I'm developing. It seems to
be impossible to repair the installation without the original msi file.
If I delete the msi file, repairing allways ends with the error "The
feature you are trying to use is on a network resource that is
unavailable.".
Hi!
I have a question about manipulating XML-files. I want to create a new
element inside an existing node, after the element is created I want to set
some attributes on it.
My problem is that there already exists elements of the kind I want to add,
how can I make the setValue action work on th
Fredrik Grohn-4 wrote:
>
> There is a custom action library to do COM+ registration in WiX. For v2
> see the PubCA schema:
> http://wix.sourceforge.net/manual-wix2/pubca_xsd_index.htm
>
> I am on the road, so I don't have an example ready to send, but if you
> search the list archive there sho
The first thing you might want to check is it linked statically or
dynamically to the VC80 runtime libraries. Changing to Visual Studio 2005
most likely introduced a dependency for you because of the C runtime
changes. If you don't want to link statically to the CRT, you could also
use a bootstra
Hi,
I've got one question related to properties. There is no other way to
store and manipulate strings than using properties?
I have to implement the next sequence:
1. Access the registry
2. Use the value read to construct another string
3. Access to the key calculated in (2)
Th
Hi,
I've coded a simple dll (where I do a registry search) to be used as a
Custom Action. If I compile it with Visual Studio 2002, all works
propertly, and during the installation, the dll is called. But if I try
to use the VS 2005 compiler, the installer fails, displaying a message
where aler
Hi,
I think I know whereabouts you have a problem but I can't give you precise
instructions. I suspect that what is happening is that your installdir and
other properties only get set in the UI sequence, without a UI then the
target directory is not set and you get it installed to the root.
You c
Hi Markus,
thank you for your hint, I already discovered this when testing the
package and found the solution you described after a long search.
Cheers Volker
Markus Wagner wrote:
> Hi Volker,
>
> If you use a custom action to set a directory with a property value you have
> to ensure that you
Hi NG,
I am using the examples from the wix tutorial. When I try to perform an
administrative install with such a package without UI ( msiexec /a
package.msi INSTALLDIR=C:\users\volker\test\) it does not install to
this given folder. Instead the package is installed to a location where
my root
Hi all,
I am installing a printer driver and would like to cycle the Spooler service
after an install. This is not a problem as I understand how to use the
StartServices and StopServices scheduling elements in
InstallExecuteSequence.
The problem is that I want to ensure that the Spooler ser
Yes, I am getting the following error:
The WiX variable !(wix.ProductName) is unknown. Please ensure the
variable is declared on the command line for light.exe, via a
WixVariable element, or inline using the syntax !(wix.ProductName=some
value which doesn't contain parenthesis).
I'm using the pr
41 matches
Mail list logo
