Hi,
I am creating a virtual directory in the Existing website with WIX 3.5 in
IIS 7.0.The site has its own apppool called CRMAppPool.
Now I am want to set the same AppPool (CRM AppPool)for my virtual directory.
But by default , it is setting as default app pool.
Please tell me how can I refer
If you always reference an existing AppPool, which is not installed by
your installation and should stay after your application is uninstalled,
you can move the definition of the AppPool (iis:WebAppPool element) out
of the Component/ and then only reference it from your virtual folder
Hi yaan,
thnx for you suggestion. But I did that. Then the compilation is giving the
error as follows.
Error 3 The iis:WebAppPool/@Identity attribute cannot be specified
unless
the element has a Component as an ancestor. A iis:WebAppPool that does not
have a Component ancestor is not
Do you want to change the identity of the existing application pool? If
not, you can just omit that attribute in order to leave the settings of
the apppool untouched. Just specify required attributes (Id and Name).
-- Yan
-Original Message-
From: MYFLEX [mailto:shrinuen...@gmail.com]
I also have the same problem. Can anyone Please tell me how to solve this.
srinivas
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/AppPool-gets-deleted-during-uninstall-tp5159767p5234250.html
Sent from the wix-users mailing list archive at
Hi,
I would like to create a patch which can install a single
file/component.
I specified the component, say SampleComponent which I want to
patch as shown below:
Fragment
PatchFamily Id='SamplePatchFamily' Version='1.0.0.0'
Supersede='yes'
ComponentRef
I'm not sure what the same problem means, but the following works the
way you need:
Directory Id=TARGETDIR Name=SourceDir
Directory Id=ProgramFilesFolder
Directory Id=INSTALLLOCATION
Name=TestAppPool
I am trying to determine the best approach to take with creating GUIDs for
the various WiX elements. We use a full upgrade approach so I believe for
the Product Id=* is okay. It probably goes without saying that setting
Package Id=* makes sense in all cases. It is my understanding that the
Hi Blair
thancxz for the information regarding referencing of an Extension Library.., i
followed ur advise and my WiX Installer code builds successfully... however
whenever i execute the MSI.package the custom action still doesn't get invoked
to run a console application in deferred mode.. i
Hi Blair
thancxz for the information regarding referencing of an Extension Library.., i
followed ur advise and my WiX Installer code builds successfully... however
whenever i execute the MSI.package the custom action still doesn't get invoked
to run a console application in deferred mode.. i
Guys,
I want to delete an entire element based on some checkbox. I have got the
decision logic working but cant seem to get the xml delete to work.
Basically we have historically have a template file for web.config that
contains some assigned values for session state
i.e.
sessionState
I haven't had any problems with component ids set to *. We keep the
Upgrade id constant but vary everything else, including the version and
the MSI name (which contains the version). Because of the changing
version and the constant upgrade id (and the PREVIOUSFOUND property
getting set in the
Hi,
I am using Wix 3.0 and developed a managed custom action which dotnet
framework version is 2.0.
Now, I faced a problem. This custom action can not be run in dot net 4.0
only machine, say WinXP SP2 + dotNet 4.0.
(For a managed EXE application, I can add app.config to indicate the
Dear WiX Users,
is there a condition for an installed .NET 4.0 Client Profile?
Also good to know would be if there are checks for an installed MSBuild and Web
Deploy (msdeploy.exe).
Thanks for your help,
KR,
J. H.
After rebuilding WIX 3.0.5419.0 locally without errors I am unable to
reference the WixUIExtension.dll, no source modifications were made.
When attempting to select the rebuilt file Visual Studio errors with A
reference to C:\Wix3.0\Build\Debug\x86\ WixUIExtension.dll could not be
added. Please
Hi,
How Do I create a domain user?
Thanks,
Carolina Zuqueto.
--
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first --
Note: I sent this yesterday, but it never appeared on the list. I
apologize if this is a repost for some.
I'm trying to understand how to install a newer version of a
component that is shared between multiple installers. I can't seem
to find any explanation of this in the docs or via google.
Hello wix users!
This is my first email, so if i do something wrong, please bare with me
(but DO tell me ;)
I have a situation where i'm really stuck and want to do things the
right way:
I use Wix 3.5.1811.0 in visual studio 2010.
Skipping the basic configuration stuff, i create a c# custom
Have you seen this example?
http://www.tramontana.co.hu/wix/lesson6.php#6.8
-Original Message-
From: Carolina Zuqueto Amaral [mailto:carolina.ama...@conv.com.br]
Sent: Tuesday, June 29, 2010 12:22 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Domain User
Hi,
How Do I
Okay, it seemed like this approach would work, just wanted to verify.
Thanks!
On Tue, Jun 29, 2010 at 10:10 AM, Cherney John-CJC030
john.cher...@motorola.com wrote:
I haven't had any problems with component ids set to *. We keep the
Upgrade id constant but vary everything else, including the
Please don't hijack threads by replying to a message and changing the
subject! Instead create a new message if you want to start a new thread.
Thanks,
Tom
On 29.06.2010 16:53, Johannes Hetzer wrote:
Dear WiX Users,
is there a condition for an installed .NET 4.0 Client Profile?
Also
Could someone chime in with a time when you wouldn't want to use * on
component Guids? Would this cause issues with generating patches?
-James
On Tue, Jun 29, 2010 at 1:19 PM, Andy Clugston clug...@gmail.com wrote:
Okay, it seemed like this approach would work, just wanted to verify.
Thanks!
I tried setting the Platform target of the custom actions project to x64
That should do exactly what you want. When you have set that, can you check the
build logs to see whether it is getting sfxca.dll from Program Files
(x86)\Windows Installer XML v3.5\SDK\x64 ?
The relevant logic is on
2.0-targeted applications do not activate with .NET 4.0 by default -- that was
a deliberate compatibility policy decision made by.NET 4.0, for better or
worse. You'll need to add useLegacyV2RuntimeActivationPolicy=true attribute to
the startup element in your CustomAction.config. For more
Hi...
I've been slapping together an installer for a window service,
and I added
ServiceDependency Id=MSMQ /
ServiceDependency Id=MSSQLServer /
To the .wxs file. When I ran the resulting msi on my dev box, the service was
installed but not all the dependencies applied.
There have been a few posts recently about harvesting registry files
with WiX v3. I have written a Heat Extension that should allow you to do
this and am hoping to get this integrated in to the v3.5 Heat core tool
but if you want to use it now or need it to work with v3 I have made
this available
How do you stop and then restart windows service when patching?
--
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first --
ServiceControl Start=install Stop=both/
-Original Message-
From: Alex Ivanoff [mailto:alex.ivan...@shavlik.com]
Sent: Tuesday, June 29, 2010 2:00 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Stop service when patching
How do you stop and then restart windows service when
Place the SampleComponent component in its own Fragment.
-Original Message-
From: Sunkesula, Srivardhan [mailto:srivardhan.sunkes...@netapp.com]
Sent: Tuesday, June 29, 2010 2:57 AM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] patching a single file
Hi,
I think you want is:
SetProperty Id=Database.Install Sequence=execute After=InstallFiles
Value=quot;[INSTALLDIR]db2mobileSQLPackage.exequot;/server:[SERVERNAME]/database:[DATABASENAME]/quiet/makedatabase
/
CustomAction Id=Database.Install BinaryKey=WixCA DllEntry=CAQuietExec
Execute=deferred
Using * for components should always be appropriate for all components
that accept * for the Guid, as long as you have never shipped the
component with a different GUID before.
It won't cause problems with generating Patches. What will cause problems
with generating patches is removing any
v1.0.0 of a particular product was shipped with hard coded GUIDs. So, if I
change to * for version 1.0.1, I will have issues?
On Tue, Jun 29, 2010 at 7:47 PM, Blair os...@live.com wrote:
Using * for components should always be appropriate for all components
that accept * for the Guid, as long
Hi,
I wrote a custom action to validate user inputs:
[CustomAction]
public static ActionResult ValidateInputs(Session session)
{
//...
If(invalid)
{ session[invalid_input]=1;}
Return ActionResult.Success.
}
The in the Wix file I check for invalid_input property.
Although this works fine, I
No problems if you use a major upgrade and schedule the upgrade early.
Standardizing on Component/@Guid=* is fantastic except when you can't use
it. The binder will tell you when that is. Then you're stuck with specifying
a GUID.
--
virtually, Rob Mensching - http://RobMensching.com LLC
On
candle.exe (or light.exe) is probably throwing an exception. Try debugging
in and seeing what it says.
On Tue, Jun 29, 2010 at 8:58 AM, Manson, Daniel (H USA)
daniel.man...@siemens.com wrote:
After rebuilding WIX 3.0.5419.0 locally without errors I am unable to
reference the
I tried to use your solution in Wix 3.0: Add this attribute and
supportedruntime in customaction.config.
Rebuild the custom action in dotnet framework 2.0 and wix package.
Copy it into a WinXP + .Net 4 machine and run.
The custom action still can not be run. :(
Could you please give me more
36 matches
Mail list logo
