I did try setting that property and I'm sure it would have worked fine if the
necessary dependencies had already been installed in the GAC.
I think the issue was that the .NET COM+ library has dependencies on the
GAC'd components and that the "commit" to the GAC doesn't occur until the
MSI has f
Exactly - it will depend on the account lockout policy for things like password
failures. If the policy says that the threshold is 1 invalid logon, and the
service starts up with the wrong password then boom, you're locked out.
Phil Wilson
-Original Message-
From: Christopher Painter
InstallServices standard action in itself cannot *directly* cause an account
lockout. For that matter, I don't think I've ever ( in 7 years ) seen an
install *directly* fail because of InstallServices.
StartServices is another story though.
If the service can't start for whatever reason,
Thanks everyone. I will point out replacing the msi and see what feedback I
get.
Tim
On Fri, Jan 28, 2011 at 5:40 AM, Rob Mensching wrote:
> Verbose log file should explain why the source was necessary. There are all
> kinds of things that can require the source.
>
> On Fri, Jan 28, 2011 at
ServiceInstall is standard functionality provided by Windows Installer.
I've never had its use result in an account lockout. In my experience the
installer fails after the first time it tries to register the service but fails
because the username/password are invalid. I've never experienced it t
Since it is so basic can you envision a situation where it would cause an
account lockout? By basic what is the underlying implementation being used?
Kevin Burton
Senior Software Engineer
BUYSEASONS
262-901-2000 Office
262-901-2312 Fax
kev...@buyseasons.com
-Original Message-
From: Rob
Here the .csproj:
http://schemas.microsoft.com/developer/msbuild/2003";>
Debug
AnyCPU
9.0.30729
2.0
{51290030-D188-4D4A-A989-DC9A57C28926}
Library
Properties
WiX.Extension
EnvironmentExtension
v3.5
512
SAK
SAK
SAK
SAK
true
Are you setting the ComPlusAssembly/@RegisterInCommit="yes"? That is
usually required for GAC'd com+ components.
Neil
-Original Message-
From: adam_j_bradley [mailto:adam_j_brad...@yahoo.com]
Sent: 28 January 2011 09:02
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Q: Erro
As I stated I'm very new to using Wix and I'm learning more about how things
work as I continue to use it. I figured out my issue and also found
something else, which as you stated below about my custom action being
executed after InstallExecuteSequence. I had a mesagebox I popped up that
indicated
I'm not very familiar with .NET projects. I need to integrate the build of C#
projects to our build process (based on msbuild). Now it is done by running
.csproj (with import of WixBuild.Common.targets) from another .proj using task
. Could you please provide me a sample of .csproj for the exten
Need a bit more information than that to help. What exactly are you doing?
What exactly was the error?
On Thu, Jan 27, 2011 at 7:34 AM, bharat jasti wrote:
> Hello All,
>
> I have tried updating web.config with the user entered host and
> credentials.
>
>
> While the installation process is goin
The built in service install of the Windows Installer is pretty basic. One
of the few standard actions I've seriously considered replacing with a
custom action.
On Thu, Jan 27, 2011 at 10:38 AM, Kevin Burton wrote:
> It seems that the default behavior for this code
>
>
> Name="ServiceExeFile" D
Verbose log file should explain why the source was necessary. There are all
kinds of things that can require the source.
On Fri, Jan 28, 2011 at 2:24 AM, Pally Sandher wrote:
> You should be able to use "msiexec /fv [original.msi]" to recache the
> source although it would also run a repair of th
A verbose log file should explain all.
On Fri, Jan 28, 2011 at 3:42 AM, Pally Sandher wrote:
> Could be a patch uninstallation bug in Windows Installer then.
> Personally I don't allow uninstalling a patch as it causes more problems
> than it solves in my experience.
> What happens if you uninsta
You'll want to double check this but I *think* you are scheduling your
custom action after the install is completed. IIRC, ExecuteAction is what
kicks off the InstallExecuteSequence which does the install. When that
finishes it comes back and executes your custom action, I think.
A verbose log fil
http://robmensching.com/blog/posts/2010/7/19/WiX-Mercurial-TortoiseHg-and-the-command-line
should
explain what is going on there.
On Thu, Jan 27, 2011 at 8:41 AM, Kevin Burton wrote:
> I am looking at
> http://wix.sourceforge.net/manual-wix3/WixUI_customizations.htm and I see
> the instructions,
No, you'll have to debug in.
On Thu, Jan 27, 2011 at 11:56 AM, Massoud Mazar wrote:
> Hi,
>
>
>
> I'm using the following libraries in a web application, to decompress cab
> files posted to the site:
>
>
>
> Microsoft.Deployment.Compression
>
> Microsoft.Deployment.Compression.Cab
>
> Microsoft.
I don't think you need WixBuild for the extensions. IIRC, we have some
helper stuff in there to flatten the XML and such that isn't necessary.
On Fri, Jan 28, 2011 at 12:12 AM, wrote:
> Hi all,
>
> Is there any way to build C# part of WiX compiler extension using only WiX
> sdk, without building
Both? Auto-harvesting was aborted in WiX v3.5 becuase it exposed too many
bugs in other project systems. It's a partial feature that is defaulted off.
We'll revisit later.
On Thu, Jan 27, 2011 at 8:56 AM, Maillet, Ed wrote:
> Hey all,
> Just wondering if this is by design or a bug.
>
> I have a
Yes.
On Fri, Jan 28, 2011 at 1:34 AM, Rune Moberg wrote:
> On Thu, Jan 27, 2011 at 5:09 PM, Rob Mensching
> wrote:
> > IIRC, a Commit Custom Action *always* runs at the end of the install.
>
> After all files have been removed..?
>
> --
> Rune
>
>
>
Unless I misunderstand, you shouldn't need to build any part of Wix to make
your own compiler extension.
You can make an extension with custom tables and schema and your own targets
without have to build/re-build any of the Wix stuff.
-Original Message-
From: maksim.vazhe...@emc.com [m
Unfortunately, updating Product A isn't an option. I could continue the
practice of using a CA until Product A is retired and removed from the servers
but I was hoping for a better option.
-Original Message-
From: Pally Sandher [mailto:pally.sand...@iesve.com]
Sent: Friday, January 28
Could be a patch uninstallation bug in Windows Installer then.
Personally I don't allow uninstalling a patch as it causes more problems
than it solves in my experience.
What happens if you uninstall the patched product A? Do logs for both
agree?
Palbinder Sandher
Software Deployment & IT Administ
Thanks for the reply.
They are from the same wixlib. And I'm 99% positive I have adhered to all the
component rules..
The only reason I can fathom for this occurring is the patch does not
recognise that a new application has installed the same component after the
patch. The reference to the compone
Would it be possible to release upgrades for both products with the
Event Sources authored? That way you can uninstall both.
Palbinder Sandher
Software Deployment & IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + Innovate with the **
You broke the component rules some how. A less error prone way to deal
with shared files of this type is to use either a wixlib or a merge
module. That way you're guaranteed to install the exact same thing &
much less likely to break the component rules.
Palbinder Sandher
Software Deployment & IT
You should be able to use "msiexec /fv [original.msi]" to recache the
source although it would also run a repair of the installation.
The root of the problem is the missing cached MSI. You need to fix that
to be able to uninstall as otherwise Windows Installer has no idea what
to actually uninstal
The answer, heat. You're allowed to say I told you so.
:)
Sincerely,
Adam
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Q-Error-using-ComPlusAssemblyDependency-to-register-a-NET-COM-assembly-tp5951460p5969344.html
Sent from the wix-users mailing
On Thu, Jan 27, 2011 at 5:09 PM, Rob Mensching wrote:
> IIRC, a Commit Custom Action *always* runs at the end of the install.
After all files have been removed..?
--
Rune
--
Special Offer-- Download ArcSight Logger for
I think I've worked out what the issue is... its just the solution which is
causing issues!
I'm trying to install a .NET application which has a .NET COM+ component. Of
course, the COM+ component wont register until the assemblies it depends
upon are present in the GAC which doesn't seem to happe
Hi all,
Is there any way to build C# part of WiX compiler extension using only WiX sdk,
without building needed WiX binaries? Now I have to build WixBuild.dll, because
it is required by WixBuild.Common.targets. I have to use
WixBuild.Common.targets to build the extension because there are some
31 matches
Mail list logo
