The Class element's ForeignServer or Server attribute was not found; one of
these is required.
Hello all,
I have looked around online and found some developers have run into this. I
have not been able to find a solution to get around this error.
I am harvesting a directory using the Pre-build E
Added -scom and got around the issue. :)
J
On Fri, Aug 9, 2013 at 11:21 AM, Jeremiahf wrote:
> The Class element's ForeignServer or Server attribute was not found; one
> of these is required.
>
>
> Hello all,
>
> I have looked around online and found some develope
a stable RC that is. :)
On Wed, Sep 11, 2013 at 3:10 PM, Jeremiahf wrote:
> Just Curious. There are some fixes I have read about that I could
> utilize.. E.g. "The CustomAction element needs a HideTarget as well.
> That'd be a bug in the
> WiX toolset." -RM
>
&
Just Curious. There are some fixes I have read about that I could utilize..
E.g. "The CustomAction element needs a HideTarget as well. That'd be a bug
in the
WiX toolset." -RM
There are some custom actions that I have that contain passwords in plain
text and I cannot get to not display in plain t
Hello all,
I have been trying to find information or an example to filter/exclude a
particular folder in a directory that is getting harvested by heat. I
currently am using -t Filter.xslt within the heat command line to exclude
certain binaries from being harvested successfully. However, instead o
ble-wix-plan/
>
>
> On Wed, Sep 11, 2013 at 1:18 PM, Jeremiahf wrote:
>
> > a stable RC that is. :)
> >
> >
> > On Wed, Sep 11, 2013 at 3:10 PM, Jeremiahf wrote:
> >
> > > Just Curious. There are some fixes I have read about that I could
> >
Just a note you cannot do a repair of WIX when trying to resolve the issue.
I have had a similar issue and had to uninstall WIX and reinstall WIX on
top of VS 2012.
Order of installation.
1. VS2012
2. WIX 3.x
On Mon, Oct 21, 2013 at 1:37 PM, John Cooper wrote:
> Inline it (brutal) or put it o
Are you using a UI?
On Wed, Jan 22, 2014 at 10:56 AM, Brian Enderle wrote:
> Is there a way using 'MajorUpgrade' to prompt the user with a message
> (either in the installer window or via a pop-up window) that running this
> installer will remove previous versions of this product and let the us
Why not right click on the DB, tasks and generate in MS? What version of
SQL?
On Thu, Jan 23, 2014 at 10:52 AM, Levi Wilson wrote:
> I am using a to create our database schema. I exported the
> schema using RedGate. The file is 10MB (I know, I know...). Everything
> works as expected, but duri
On Thu, Jan 23, 2014 at 9:47 AM, C B wrote:
> During an installation or major upgrade, if a user has pinned the
> application to their task bar, then after the installation has completed,
> the taskbar shortcut is removed from "\AppData\Roaming\Microsoft\Internet
> Explorer\Quick Launch\User
n
>
>
> On Thu, Jan 23, 2014 at 11:57 AM, Jeremiahf wrote:
>
> > Are you using a UI?
> >
> >
> > On Wed, Jan 22, 2014 at 10:56 AM, Brian Enderle
> wrote:
> >
> > > Is there a way using 'MajorUpgrade' to prompt the user with a message
I always do it in the Pre-build event command line. My example.
"$(WIX)bin\heat.exe" dir "$(ProjectDir)..\folder\files" -dr INSTALLLOCATION
-cg someGroup -gg -sf -srd -svb6 -var "var.somevar" -out
"$(ProjectDir)someGroup.wxs"
On Thu, Jan 23, 2014 at 1:38 AM, Graham Allwood wrote:
> Hi,
>
> I ha
Are you using
InstallPrivileges="elevated"
InstallScope="perMachine"/>
in
On Fri, Jan 24, 2014 at 4:12 PM, Scott Palmer wrote:
> Can someone show me code that can successfully do it?
>
> I tried:
>
>ExeCommand='[SystemFolder]cmd.exe /K mklink /D mylink
Interesting... does it not work with removing the quotes from
"[$(var.linkDest)]"' ? btw... I copied your line and there is an extra '
after "[$(var.linkDest)]". I pasted it in notepad and saw it more clear.
Check this out.
http://www.windows7home.net/how-to-create-symbolic-link-in-windows-7/
us
Guess I misunderstood the question.
On Thu, Jan 23, 2014 at 6:40 PM, Nicolás Alvarez
wrote:
> "Permanent" would make it stay after an uninstall too, which is
> probably not wanted.
>
> --
> Nicolás
>
> 2014/1/23 Jeremiahf :
> > Permanent="yes"&g
Has anyone had luck with this?
I have tried using Hidden, HideTarget and I still see the password in my
logs. Is this still a bug in windows installer?
Thanks in advance,
--
Get 100% visibility into Java/.NET code wi
t;
> This is how I use my password controls:
> Y="152" Property="WEBAPPPOOL_PASSWORD" Password="yes" TabSkip="no" />
>
> Logfile:
> MSI (c) (70:1C) [14:50:59:778]: PROPERTY CHANGE: Adding
> WEBAPPPOOL_PASSWORD property. Its value is
I made to make those extensions hide the data
> passed to them, such as my password.
>
> -----Original Message-
> From: Jeremiahf [mailto:jeremi...@gmail.com]
> Sent: Thursday, May 02, 2013 2:38 PM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-
area and see if that works... (also
> commenting out your custom action to set the property
>
> Steve
>
> -Original Message-
> From: Jeremiahf [mailto:jeremi...@gmail.com]
> Sent: May-02-13 6:29 PM
> To: General discussion for Windows Installer XML toolset.
> Subj
Are you sure this is correct?
$(var.ProjectDir)..\..\
How many folders are you actually backing out then back into and are they
located in your Project Directory?
J
On Thu, May 2, 2013 at 6:05 PM, Prosch, Greg wrote:
> For the burn code below I am getting the following error message:
>
> warn
In visual studio under build you need to define a preprocessor variable
that points to the location of the root directory. Example:
DatabaseDir=..\Folder.
Then under build events you need to write a Pre-build Event command line to
have heat generate the wxs file every time you make a build.
Example
le get account passwords from a MSI dialog and
> store it in a property such as MYPASSWORD, and then pass it to a custom
> action that uses it.
>
> However, you're using managed code custom actions, and it seems from the
> log that the (DTF?) code just does its own logging into th
password actually being logged by the custom
> action itself?
>
>
> On Fri, May 3, 2013 at 3:53 PM, Jeremiahf wrote:
>
> > Steven,
> >
> > "Tried adding: HideTarget="yes" that didn't help" Indeed!
> >
> > I'm even tried to remove
Sorry, it was a very long day.
Have you tried running the installer as administrator?
On Sat, May 4, 2013 at 1:25 AM, - Arzola - wrote:
> Yes. As seen below, the installer is detecting that the required .net
> framework 4.0 is already present with no need to install.
>
> [063C:11BC][2013-05-0
previously posted as:
> ===
> Action start 17:26:56: InstallFinalize.
> SFXCA: Extracting custom action to temporary directory:
> C:\WINDOWS\Installer\MSI1045.tmp-\
> SFXCA: Binding to CLR version v2.0.50727 Calling custom action
> Databa
ce so you can find the session.Log() entry that
> was logging your secrets.
>
> So you have the source and you found it. Great. Now you know how to do
> it the other way if you ever need to one day.
> --
> *From*: "Jeremiahf"
> *Sent*:
Hello,
The funny thing is that it crossed my mind. "Rebooting fixes everything"
ha! Glad to hear it worked out for you.
J
On Tue, May 7, 2013 at 10:59 AM, - Arzola - wrote:
> Hi Jeremiah. I appreciate your replies.
> Turns out the client was able to install after rebooting and logging in as
ot Windows
> Installer logging data, it is the custom action code.
>
> Phil
>
>
> -Original Message-
> From: Jeremiahf [mailto:jeremi...@gmail.com]
> Sent: Friday, May 03, 2013 3:54 PM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-us
I had the same issue with 3.6. My solution was to completely uninstall WIX
and re-install it.
On Wed, May 8, 2013 at 10:05 AM, Joe Barker wrote:
> Hi,
>
>
> I have WiX 3.7 installed, and recently upgraded to VS2012; since the
> upgrade to 2012, I can't open the Installer solution I'm using. I t
http://wix.sourceforge.net/manual-wix3/wix_xsd_installexecutesequence.htm
Hope this is what you need.
Thanks,
J
On Wed, May 8, 2013 at 10:11 AM, Nick Miller wrote:
> Hi All,
>
> I was wondering if there is some documentation somewhere that details the
> execute sequence that burn goes through
Make sure the file version # is updated in file version under assembly info
within assembly info if you are using VS 2010 and above. Also, use Orca to
view the properties of an MSI installer.
J
On Fri, May 10, 2013 at 8:55 PM, Candy Chiu wrote:
> Hi,
>
> I ran into an issue that one of dll's i
Are you using the CloseApplication element?
http://wix.sourceforge.net/manual-wix3/util_xsd_closeapplication.htm
J
On Wed, May 15, 2013 at 2:40 AM, Saeed, Rehan wrote:
> When closing my application it prompts users to save any unsaved
> information. When installing a new version of my appli
I always use InstallPrivileges="elevated" under Package id.
J
On Thu, May 16, 2013 at 10:45 AM, Tom - wrote:
> And the directory in question is Program Files\Manufacturer\Product, which
> translates to "C:\Program Files (x86)\SupersecretCompany\My Product Name".
> The error message says "log o
Hi Jacob,
True, I left that one out InstallScope="perMachine"/> I include that as
well under InstallPrivileges="elevated" under Package element.
J
On Thu, May 16, 2013 at 10:52 AM, Hoover, Jacob
wrote:
> Ensure it's a per-machine installation package
> (Product/Package/@InstallPrivileges='elev
Are you not referencing SampleGroup.wxs?
J
On Fri, May 17, 2013 at 8:55 AM, BGINFO4X wrote:
> Hello everyone,
>
> I'm a new to WIX and I'm a little lost.
>
> I want to create a .msi file from my project (with lots of files and
> folders), so I use HEAT.
> Heat works as exepcted an
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Guid="240BFA0F-8BF2-45AB-A1CB-
Here is the configuration I use in product.wxs
and remove the older version in my InstallExecuteSequence.
J
On Fri, May 17, 2013 at 4:19 PM, Rizwan Zahid wrote:
> Hi,
>
> I created following bootstrapper ,it install perfectly. now I am looking
It sounds like your dev system is pretty out of shape. If you installed VS
after WIX then you have to completely uninstall WIX and reinstall WIX. A
repair will not fix it.
Best of luck
On Mon, Mar 17, 2014 at 8:11 AM, Phill Hogland wrote:
> I have used heat.exe in Wix 3.7 and Wix 3.8, so I do
Hi all,
I have been looking everywhere to find the answer to this question. Does
WIX Bootstrapper support the use of an xml config file or answer file to
obtain the chain of packages to install? I have seen bootstrapper.confg
files and some other information but I feel like I am going down rabbit
content, up the bootstrapper version number and re-compile every time any
> of the bundles change.
>
> This is a good thing as it ensures cohesion of release content.
>
> -Original Message-
> From: Jeremiahf [mailto:jeremi...@gmail.com]
> Sent: Thursday, April 03, 2014 2:12 PM
Isn't configruationfile case sensitive?
I have run it like this from command line.
SQLEXPRWT_x64_ENU.exe
/CONFIGURATIONFILE="C:\somepath\anotherpath\ConfigurationFile.INI"
If you use that don't forget to replace " with "
You might also want to make sure your configuration file looks like this.
Are you using elevated InstallPrivileges and PerMachine in your package ID?
InstallPrivileges="elevated"
InstallScope="perMachine"/>
Also,
Did you set any components in your original installer to PatchIgnore="yes"?
I haven't necessarily done patches but I do set
Instal
Oh and see if you can enable verbose logging through SCCM to see what else
may be going on.
/l*v logname.log
On Tue, Apr 15, 2014 at 5:55 PM, Jeremiahf wrote:
> Are you using elevated InstallPrivileges and PerMachine in your package ID?
>
> InstallPrivileges=
you can also use /qn (quiet no ui)
On Fri, Apr 25, 2014 at 12:58 PM, Jeremiahf wrote:
> Restart Options
> /norestart
> Do not restart after the installation is complete
> /promptrestart
> Prompts the user for restart if necessary
> /forcerestart
> Always resta
Restart Options
/norestart
Do not restart after the installation is complete
/promptrestart
Prompts the user for restart if necessary
/forcerestart
Always restart the computer after installation
On Fri, Apr 25, 2014 at 12:21 PM, wrote:
> Do I have to have created a proper ServiceControl *before
Hello,
I know you said the installer prompts for elevated but do you have this?
InstallPrivileges="elevated"
InstallScope="perMachine"/>
In the package ID section in your product.wxs file.
On Mon, Apr 28, 2014 at 5:46 PM, wrote:
> Dit mailadres is niet meer in gebruik. Mai
change.
>
> > -Original Message-
> > From: Jeremiahf [mailto:jeremi...@gmail.com]
> > Sent: 29 April 2014 00:31
> > To: General discussion about the WiX toolset.
> > Subject: Re: [WiX-users] Installer runs OK via msiexec but fails when
> > double-clicked
&g
Try this
On Mon, Apr 28, 2014 at 1:18 AM, Satbir Singh wrote:
> I am working with WiX from last 5 month with no issues. Recently, i am in
> need to have "StartIn" property in App Desktop shortcut. By default, its
> empty.
>
> I am workin
Oh and Reference the Desktop directory in your directory structure...
Sorry,
J
On Tue, Apr 29, 2014 at 5:17 PM, Jeremiahf wrote:
> Try this
>
>
>
> Name="Shortcutname"
>Description="Shortcutname&q
Off the top of my head you can use conditions to install either.
On Thu, Apr 24, 2014 at 10:55 AM, wrote:
>
> I have a service that outputs some definitions to an Excel file. As such,
> I need to always add this folder on install:
>
> C:\Windows\system32\config\systemprofile\desktop
>
> Whe
2.
3.
4. **
On Wed, Apr 30, 2014 at 1:17 AM, Satbir Singh wrote:
> Hi Guys,
> I tried what Jeremiahf said but that didn't worked too.
> Here<http://pastebin.com/W8C6njgv>I have added a demo of my installer
>
You could use a custom action to do this.
cmd /c "sc config RemoteRegistry start= auto"
Then use a condition like NOT Installed to run the CA only when the
installer has not been installed on the target machine.
On Thu, May 22, 2014 at 9:55 AM, David Welton <
david.wel...@uk.thalesgroup.com> w
Is anyone aware that b.ras...@leonit.nl is auto responding that the email
account he is responding from says that the email address is no longer
being used? Just letting the admins know.
On Mon, May 19, 2014 at 10:08 AM, wrote:
> Dit mailadres is niet meer in gebruik. Mail kan je voortaan st
This may be extra info but I use a config.wxi file and set the values in
there and just reference them with variables like below.
However, you should probably set your values like below except you don't
have to use variables. Just set the values that you need applied.
Then you can use p
FYI there is not an attachment.
This is how I used to do it before my requirements changed...
will upgrade 1.1.1.1 to 1.1.2.1 and not allow a downgrade.
keep the Upgradecode static and the product/Package Ids to "*"
I use a config.wxi file that I include into product.wxs then reference the
valu
Meant maybe try to explain why you are getting downgrading between builds
with no errors - from 2.3.4.6 to 2.3.4.2 Got ahead of myself.
J
On Mon, Jun 2, 2014 at 3:15 PM, Jeremiahf wrote:
> FYI there is not an attachment.
>
> This is how I used to do it before my requirement
I'm assuming you have this in your value in your MsiPackage chain?
DisplayInternalUI="yes"
On Thu, Jun 5, 2014 at 12:10 PM, Tunney, Stephen
wrote:
> Does anyone know how I can fix this? We are hitting this with an internal
> UI is being displayed on the screen. Doesn't look too good :(
>
> S
Should be fine. I haven't had any problems.
On Wed, Jun 18, 2014 at 7:38 AM, neslekkim wrote:
> anyone?, or is it perfectly ok to store this in hkcu for perMachine
> installs?
>
>
>
>
> --
> View this message in context:
> http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Problem-wi
What was the previous installer?
On Fri, Jun 20, 2014 at 9:32 AM, Phill Hogland wrote:
> The update behavior of msiexec and the UpdateCode property are specific to
> MSI based technology. It would not know about other technologies like
> InstallJammer.
>
>
>
> --
> View this message in context
Sorry, I misunderstood as I am not familiar with InstallerJammer.
I did find this though.
http://stackoverflow.com/questions/14334012/how-can-perform-a-silent-uninstall-with-installjammer
Again, I'm not familiar with InstallerJammer and I'm assuming it doesn't
use WindowsInstaller???
Since you
**If it uses windows installer that is**
Since you can have only have one install/uninstall at one time on a windows
machine this might not work if you try to uninstall during your new install.
On Fri, Jun 20, 2014 at 2:41 PM, Jeremiahf wrote:
> Sorry, I misunderstood as I am not famil
You have the check the registry.
Here is my example but with .NET 4.0
On Thu, Jul 10, 2014 at 1:49 PM, TimM wrote:
> I have seen many WiX articles on detecting .NET 4.5 or greater and I have
> implemented the recommended entires, but my install will
Hello everyone,
Has anyone had experience in detecting for V C++ 2013 dependency in their
installer? It's doesn't appear to be as easy as it used to be...
Thank you in Advance,
J
--
"They may forget what you said but they will never forget how you made them
feel." -- Anonymous
--
Thanks guys but I need to detect if it is installed through an msi and not
a bootstrapper. It also has to be the x86 version.
I was trying to detect it through the registry as I have done for previous
versions of V C++ Redists. Any idea's?
Sorry for the lack of info in my initial email.
Thank you
andle this even though the application getting
installed depends on it?
On Fri, Aug 15, 2014 at 10:56 AM, Jeremiahf wrote:
> Thanks guys but I need to detect if it is installed through an msi and not
> a bootstrapper. It also has to be the x86 version.
> I was trying to detect it throug
Have you tried putting conditions in your ?
http://alekdavis.blogspot.com/2013/05/wix-woes-what-is-your-installer-doing.html
- NOT Installed OR REINSTALL
InstallUninstallRepairModifyUpgradeINSTALLEDFALSETRUEFALSETRUETRUEREINSTALL
TRUEFALSETRUEFALSEFALSEREMOVE="ALL"FALSETRUEFALSETRUETRUE
U
Change your level to 2
On Fri, Sep 12, 2014 at 1:44 PM, Tony wrote:
> Assuming we are using the WixUI_FeatureTree UI sequence, how can I define
> my features (multi-level) such that none of them are selected for
> installation by default?
>
> This works, but I wonder if it is a poor choice...(se
Hello,
I have an installer that writes "default" property values to an XML config
file every time the installer runs . I have a new requirement that does not
allow me to "hardcode/set" those default property values within the
installer but just install the config file and only update the config fi
What feature? Did you try looking in the registry?
On Fri, Sep 12, 2014 at 6:15 AM, neslekkim wrote:
> Ensuring that it's there should not be the same as you install it :)
>
> Anyway, I need to detect if this feature is installed, so i can abort the
> install if it's missing, It's easy to detect
Also the command line parameters do update the config file. Just wanted to
be clear that the XML config file should only be written to when a command
line parameter is used.
Thanks again for any assistance.
J
On Wed, Sep 17, 2014 at 2:17 PM, Jeremiahf wrote:
> Hello,
>
> I have an
31 172 65 02 65 www.stabiplan.nl www.stabiplan.nl/disclaimer
> -Original Message-
> From: Jeremiahf [mailto:jeremi...@gmail.com]
> Sent: woensdag 17 september 2014 23:14
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] XMLConfig updates
Do you mean the assembly name is MyAppSetup by default? Set the assembly
name to what you want in the project properties.
On Wed, Sep 24, 2014 at 11:06 AM, newuser2014
wrote:
> Hi,
>
> When I use wix to generate an msi for MyApp, the generated msi is named
> MyAppSetup.msi. Is there anyway I co
Good call! :)
On Thu, Sep 25, 2014 at 12:34 PM, sampat magi wrote:
> Hi,
> I am really interested to learn Wix Installer to author our product
> installer. We are planning to move from InstallShield to WiX,
>
> Regards
> Sampat
>
>
So you are trying to harvest it with heat as a single file? I'm not sure I
follow. Can you give a little more info?
From "If I integrate that fragment into my main-wxs-file and build the
solution" it sounds like you are trying to include it as a component but
not have it in a harvesty group wxs fi
Also, what if it executed silently with no UI then it wouldn't be executed
either.
On Tue, Sep 30, 2014 at 11:44 AM, Pavan Konduru
wrote:
> How will the installer know to run the CA, if you don't want to tie it to
> a button event but want to run it when a dialog is shown?
>
>
> -Original Me
Why not add another custom action that removes the user from the group and
only execute on the condition of Uninstall?
On Sun, Oct 5, 2014 at 2:19 PM, Bob Arnson wrote:
> On 05-Oct-14 01:58, Nick Ramirez wrote:
> > I was afraid that setting RemoveOnUninstall to "yes" or not putting it
> there
>
Sorry, Thought you were trying to remove the user from the group on
uninstall.
On Mon, Oct 6, 2014 at 10:42 AM, Nick Ramirez wrote:
> No need to make my own custom action. I've found that the WiX extension
> from
> the Community MSI Extensions project has an element for adding an existing
> user
Try this:
add the CustomAction to your installexecutesequence
(NOT
UPGRADINGPRODUCTCODE) AND (REMOVE="ALL")
Hope that helps.
J
On Tue, Oct 7, 2014 at 9:57 PM, Nick Ramirez wrote:
> Jeremiahf wrote
> > Sorry, Thought you were trying to remove the user from the gro
simply.
>
> _
> Short replies here. Complete answers over there:
> http://www.firegiant.com/
>
>
>
> -Original Message-
> From: Jeremiahf [mailto:jeremi...@gmail.com]
> Sent: Wednesday, October 8, 2014 5:36 AM
> To: General discussion about the WiX
I have run my installers on xp with that version number of 200 and it was
fine.
XP w/ SP3
Someone correct me if I am wrong but shouldn't both of these be unique?
(I'm not saying this is the problem.)
On Tue, Oct 21, 2014 at 4:43 PM, Christopher Fraser wrote:
> On 21/10/14 22:18, John C
You didn't happen to have it open in orca when you ran the installer did
you?
On Tue, Oct 21, 2014 at 5:14 PM, Christopher Fraser wrote:
> I'm using WiX 3.8 and I don't use .Net (in this, at least).
>
> On 21/10/14 23:09, Carter Young wrote:
> > What Version of WiX are you using and if your App
Here is the condition you can use
http://wixtoolset.org/documentation/manual/v3/howtos/redistributables_and_install_checks/block_install_on_os.html
Here is the link to diff. OS versions.
http://msdn.microsoft.com/library/aa370556.aspx
On Tue, Oct 21, 2014 at 3:56 PM, Baris Caglar wrot
Are you creating the database with the installer?
On Tue, Nov 4, 2014 at 7:21 AM, Bala wrote:
> HI All,
>
>
>
> The exact error in log file
>
>
>
> Error 26202. Error -2147217900: failed to drop SQL database: , error
> detail:
> Incorrect syntax near 'DATABASE'..
>
>
>
> If manually deleted the
What's the difference between the two machines? Firewall? Different network
configuration/subnet?
On Fri, Nov 7, 2014 at 7:15 AM, Mohamed Yasir
wrote:
> Hi,
>
> I have created two msi file (SampleSetup1 & SampleSetup2) using wix
> toolset3.8.
>
> In Installation,SampleSetup1 download successfull
You are trying to remove a directory that does not exist.
Missing folder property: APPLICATIONDATAFOLDER
and you are not creating it as a directory:
Instead searching the registery:
How do you know that the drive letter will always be h:?
Value="h:\topfolder\mid
Have you seen this WIX Tutorial?
http://wix.tramontana.co.hu/tutorial/getting-started/conditional-installation
also,
http://blogs.technet.com/b/alexshev/archive/2008/02/10/from-msi-to-wix-part-3.aspx
On Thu, Dec 4, 2014 at 2:12 PM, Marek Mielcarek
wrote:
> I need to define a Condition which g
That makes a little more sense now. Try placing a condition in your feature
that includes a condition message. The condition message should reference
the condition using similar to what Pavan gave an example of.
example for .net 4 detection just to give you an idea of what I am talking
about:
a message inside a
> Feature.
> WiX compiler generates this: "The Condition element contains an unexpected
> attribute 'Message'" :(
>
>
>
>
>
> -Original Message-
> From: Jeremiahf [mailto:jeremi...@gmail.com]
> Sent: Friday, December 05, 201
Now I see the rest of the threads. :/
On Fri, Dec 5, 2014 at 2:13 PM, Jeremiahf wrote:
> Did you set a condition level under the feature Id??
>
>
>
> On Fri, Dec 5, 2014 at 9:27 AM, Marek Mielcarek
> wrote:
>
>> Thank you for your help Jeremiah. I actually t
Are you setting Property Id's with values?
E.g.
Then:
On Mon, Dec 15, 2014 at 8:53 AM, patrickpirzer
wrote:
>
> I want to create a new SQL Login, so i tried this with the following
> SqlString:
>
> Guid="AEE91491-99FA-40A9-AB47-1E9FC
Have a look at this.
http://wixtoolset.org/documentation/manual/v3/overview/heat.html
On Mon, Dec 15, 2014 at 2:42 PM, wixtester wrote:
>
>
>
> The COM+ application is .Net and not native. After correcting the attribute
> values, I am now getting errors with .Net failing to register the assembly
--
Dive into the World of Parallel Programming! The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
le
Oh and if SQL is clustered or has a named instance don't use "."
J
On Wed, Jan 7, 2015 at 2:23 AM, patrickpirzer
wrote:
> I have programmed a bootstrapper-project with WiX 3.8.
> While the installation i want to create a sql server login with
> sql-authentication.
> So i embedded in the Product
I think this is what you may be looking for.
http://stackoverflow.com/questions/1601186/sql-server-script-to-create-a-new-user
I don't think you want to use ContinueOnError="yes". That way you may be
able to see what is wrong if you use verbose logging and it might help.
J
On Wed, Jan 7, 2015 a
Defer it?
On Wed, Jan 7, 2015 at 8:49 PM, wixtester wrote:
>
> The CustomAction does not permit "Win64" attribute for a managed custom
> action
>
> BinaryKey='provisionCA' DllEntry='SearchJRE' Execute="immediate"
> Return="check" Win64="yes"/>
>
>
> Error message
>
> error
.aspx
It should give you some direction.
On Thu, Jan 8, 2015 at 12:01 AM, Jeremiahf wrote:
> Defer it?
>
> On Wed, Jan 7, 2015 at 8:49 PM, wixtester wrote:
>
>>
>> The CustomAction does not permit "Win64" attribute for a managed custom
>> action
>>
&
Are you using conditions in the install execute sequence?
On Fri, Jan 9, 2015 at 9:31 AM, wixtester wrote:
> Hi,
>
>I have a scripted custom action to register a COM+ service on install
> and
> unregister it during uninstall.
> It works fine during install, but fails during uninstall.
>
> Cu
Include the condition in your execute sequence to include REMOVE=ALL
On Fri, Jan 16, 2015 at 11:35 AM, wixtester wrote:
> Hi,
>
>I am using the WIXFAILWHENDEFFERED customaction reference to test the
> installer rollback sequence.
> The Install rollback works fine with this property but the u
So you want to leave the old config file there? Will your new installer
configure the new config file and maintain it from there on?
On Wed, Jan 28, 2015 at 8:15 AM, Kraygsoft
wrote:
> Anyone
>
>
>
> --
> View this message in context:
> http://windows-installer-xml-wix-toolset.687559.n2
I assume you have read this?
https://msdn.microsoft.com/en-us/library/windows/desktop/aa373680(v=vs.85).aspx
On Thu, Feb 12, 2015 at 4:43 PM, Sascha Sertel
wrote:
> My WiX 3.9 installer uses RestartManager to shut down the app if it's still
> running before upgrading or uninstalling. That has wo
1 - 100 of 116 matches
Mail list logo
