The virtual directory doesn't care about what version ASP.NET you are
running, since it's not actually responsible for running any processes.
It's only the Application Pool that runs processes and thus cares about
whether you are .NET v2 or .NET v4 etc.. or even if you are 64-bit vs
32-bit.
When y
Usually you debug this with the fusion log viewer to see why it's not
working. Typical issues are assembly naming differences (like the
version or language) and the bitness. If you mean that you copied them
from the GAC to the app folder, that's more mysterious, but if you got
them from somewhere e
More specifically, we did the work when we initially designed Burn to not have
any of the security vulnerabilities that the unnamed bootstrapper did in the
blog entry.
This design is the main reason you have to double sign Bundles.
Chalk one up for doing the right thing the first time.
__
As Neil indicated you have to provide correct names in your Payload
attributes.
Here is another discussion about this issue:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Custom-theme-in-Bundle-how-to-add-xml-and-wxl-td7588021.html#a7588026
http://windows-installer-xml-wix-toolset
I agree seems like the engine should be doing what you expect.
___
FireGiant | Dedicated support for the WiX toolset |
http://www.firegiant.com/
-Original Message-
From: Tobias Weigt [mailto:t.we...@datam.de]
Sent: Friday,
Treat warnings as werrors?
___
FireGiant | Dedicated support for the WiX toolset |
http://www.firegiant.com/
-Original Message-
From: Narayana Rao, Sanjay [mailto:sanjay.narayana...@philips.com]
Sent: Friday, February 14,
It seems I have no clue about what the RequestState.Cache value does.
I hoped to uninstall a package (but keep it cached) by setting its RequestState
to Cache in the PlanPackageBegin event of my BA but it had no effect. See
appended log.
What are the uses of RequestState.Cache (and RequestState.
You are correct I found the same thing. Any text that changes during the
install must have a Background attribute on the font otherwise the text just
keeps drawing over itself. This makes it really difficult if you are using a
background image.
I did come across the issue with the images you
On 14-Feb-14 11:18, Hoover, Jacob wrote:
> I think this is more than just resigning
Unless you were doing the particular thing they're now ruling out, you
shouldn't have to re-sign anything.
> Will this impact Wix and Burn as a similar technique was used to put the BA,
> Manifest, resources,
I think this is more than just resigning
Will this impact Wix and Burn as a similar technique was used to put the BA,
Manifest, resources, and any embedded installers into the overlay?
Any chance we could have MS consider previously signed files with timestamps to
be exempt?
-Origi
Everyone should be aware of the issue and be prepared to re-sign their binaries
and installers :(
http://blogs.technet.com/b/srd/archive/2013/12/10/ms13-098-update-to-enhance-the-security-of-authenticode.aspx
--
Android
Further information: I had taken out the Background attributes from -
putting them back seems to
fix that problem.
However, and possibly related, I've also now tried putting different images
on individual pages and I'm seeing *all* of the images appear on each page.
Is the window not cleared be
Nope, just Windows 7 and standard DPI (and WiX 3.7 BTW)
Hoover, Jacob wrote
> Hmm, are you trying to make the font larger or smaller? What OS are you
> testing the bundle on and what is the DPI/Font scaling configured as?
>
> A quick scan of the source shows me no calls to SetProcessDPIAware, an
That is a property whose value i fetch from another include file
On 14-02-2014 19:19, Steven Ogilvie wrote:
> Hi Suvrajyoti,
>
> Curious, I don't use a
> What is "VIRTUAL_DIR_VAL" ?
>
> Thanks,
>
> Steve
>
> -Original Message-
> From: Suvrajyoti Panda [mailto:suvrajyo...@contata.co.in]
>
Kiran
Turn on MSI logging either via the registry OR adding it to your product.wxs:
Find out WHY you are getting that error...
Steve
-Original Message-
From: Kiran Somisetty [mailto:mr.svski...@gmail.com]
Sent: February-14-14 8:55 AM
To: General discussion about the WiX toolset.
Subje
I suspect in IIS the Virtual dir or Application is already exist,again
your trying to install the same virtual dir with ur MSI..delete the the
virtual dir and try again..it may work
On 14-02-2014 19:24, Kiran Somisetty wrote:
> the installation is failing and show the below error
>
> INSTALL c
the installation is failing and show the below error
INSTALL completed, msiexec.exe return code: 1603
I have copied my code usage below, pls take a glance.
On Fri, Feb 14, 2014 at 7:07 P
Hi Suvrajyoti,
Curious, I don't use a mailto:suvrajyo...@contata.co.in]
Sent: February-14-14 6:50 AM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] How to select ASP.NET version
Hi Kiran,
I have used as below. Please see the app pool creation here.
Hmm, are you trying to make the font larger or smaller? What OS are you testing
the bundle on and what is the DPI/Font scaling configured as?
A quick scan of the source shows me no calls to SetProcessDPIAware, and the
manifest doesn't contain dpiAware, so I would assume it's because you are on a
Just use the below for your app pool.
ManagedRuntimeVersion="v4.0"
Could you please be more elaborate on the error you are facing.
On 14-02-2014 18:47, Kiran Somisetty wrote:
> Thanks for the response.
> I tried to implement like this, but I am getting a :1603 error during
> installation, any cl
I'm using a custom theme with WixStandardBootstrapperApplication and my
elements look a bit rubbish. I've tried various combinations of Height, Weight
and font name and, while some look worse than others, none seems to me to look
particularly good. Could I be doing something wrong? Any tricks/t
Hmm, sorry for pushing this, but is it really true, that this is the only
solution?!?
It seems like there is no way to do "greater-than" on a DWORD from the
registry.
Anyone?
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/How-to-compare-REG-DW
Thanks for the response.
I tried to implement like this, but I am getting a :1603 error during
installation, any clues on this.
On Fri, Feb 14, 2014 at 5:20 PM, Suvrajyoti Panda wrote:
> Hi Kiran,
>
> I have used as below. Please see the app pool creation here.
>
>
>
>
Hi there,
I have a little problem with my wix installation.
I`m putting some dlls into the gac by using Assembly=".net" atribute...
Everything works fine on win7 64bit, after installation apllication runs
fine, however if I will do the same on the win7 32bit it is not working.
It looks like on 3
Hi Kiran,
I have used as below. Please see the app pool creation here.
Regards,
Suvra Jyoti
On 14-02-2
you can seletc buy setting tag tag "ManagedRunTimeVersion".
On 14-02-2014 16:17, Kiran Somisetty wrote:
> Is there a way to provide the ASP.NET version while creating Web virtual
> directory in wix installer. I have created a installer that creates a web
> virtual directory, but I see the ASP.NE
Is there a way to provide the ASP.NET version while creating Web virtual
directory in wix installer. I have created a installer that creates a web
virtual directory, but I see the ASP.NET version is pointed to 2.0. I want
to set it to 4.0, rather than manually changing it.
-
You need to embed the wxl files using the element.
I tend to do it like this:
Where and are the LCID values of the language in the wxl file.
Neil
>Hi , Phill
>
>Thanks for the reply, I read the web page and now I know how to create a
>wxl
>file and embed it into my bootstrappe
Hi , Phill
Thanks for the reply, I read the web page and now I know how to create a wxl
file and embed it into my bootstrapper project in VS.
But my problem still exists. How I create more than one culture file and use
them in the same project?
I tried to create one file named "local-enUS.wxl" a
Yes Module dependency.
New MSM:
Test MSI:
If I miss Merging old.msm which New.msm is depending on, I get foll
30 matches
Mail list logo
