from:"Farrukhw"

Hi
I need to make a patch for an already installed product, to just update its
version information i.e. 9.4.5.10 to 9.4.5.11.

I read different articles/posts, but not getting any proper way to do this.

Any help would be really appreciated.

Thanks a bunch 
Farrukh


--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Patch-to-update-version-of-installed-product-tp7579458.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Patch to update version of installed product?

Hi Peter,
Thanks for such a quick response... It does make sense to me.
But what do you mean by wholly wix patching?? 

I'm quite a newbie to patches actually. 

--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Patch-to-update-version-of-installed-product-tp7579458p7579460.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Patch to update version of installed product?

Thanks again...
I was reading this article about patch restrictions:
http://wix.sourceforge.net/manual-wix3/patch_restrictions.htm

and it mentions following:
Small updates: do not change the ProductVersion property of a target product
and typically represent a small subset of files to be updated.

Now got confused again :(

--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Patch-to-update-version-of-installed-product-tp7579458p7579463.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Patch to update version of installed product?

Thanks Neil,
But that's a full product upgrade. My task is to generate a patch which
would update the Version info of installed product.

I just tried this:

http://schemas.microsoft.com/wix/2006/wi";>
  

  
   



  


  

  

  

  


and it worked. It changed the version that 4 digit version successfully. But
only problem I faced is when I launched the msp file, it showed Customize
Dialog (Repair, Reinstall, Uninstall) and I have to click on Repair but it
did the job.

i want to get rid of that Customize Dialog and wanted that this should do
the job directly.

Any ideas?


--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Patch-to-update-version-of-installed-product-tp7579458p7579468.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Patch to update version of installed product?

Thanks anyway Neil for giving time 

--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Patch-to-update-version-of-installed-product-tp7579458p7579470.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Patch to update version of installed product?

Peter,
I just tried this:

http://schemas.microsoft.com/wix/2006/wi";>
  

  
   



  


  

  

  

  


and it worked. It changed the version that 4 digit version successfully. But
only problem I faced is when I launched the msp file, it showed Customize
Dialog (Repair, Reinstall, Uninstall) and I have to click on Repair but it
did the job.

i want to get rid of that Customize Dialog and wanted that this should do
the job directly.

Any ideas if I can skip any Dialogs during Patch installation?

--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Patch-to-update-version-of-installed-product-tp7579458p7579472.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Patch can't update installed product and shows Change/Repair dialog..

Hi Guys,
I'm building a patch using PCP, according to this tutorial:
http://wix.sourceforge.net/manual-wix3/patch_building.htm
http://wix.sourceforge.net/manual-wix3/patch_building.htm

I'v two MSI (extracted as Admin installs)
1. 8.11.9.225 (This is my target to update)
2. 8.11.9.353 (The latest one).

Above procedure worked without any problem and generates my .msp file, but
of a big size (500+ MB) so I think, it is getting too much differences.

However, whenever I tried to install this patch, it shows Change/Repair
Dialog, and if I use Change or Repair, in both cases it error
"Another version is already installed. You must first uninstall it in order
to install this version."

I even changed the Product Code in the 2nd msi (in all tables), but it can't
solve any problem.

Here is my patch code:

*As it is generating a big size .msp, should I use msp for such size or do
major upgrade?*

Any help would be really appreciate

Best regards

--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Patch-can-t-update-installed-product-and-shows-Change-Repair-dialog-tp7579479.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Patch to update version of installed product?

Thanks all for your replies. I've just posted my resultant patch script here:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Patch-can-t-update-installed-product-and-shows-Change-Repair-dialog-td7579479.html

but with some issues and I need help in these.

Thanks

--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Patch-to-update-version-of-installed-product-tp7579458p7579480.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Patch to update version of installed product?

Hi Moc
Thanks for the tips. No, I only changed ProductCode with a new GUID and
updated in all other tables e.g. Registry, INIFile etc.



--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Patch-to-update-version-of-installed-product-tp7579458p7579482.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Patch to update version of installed product?

In the WIX of Product, we do not use PackageCode, as far I remember. It was
deprecated

--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Patch-to-update-version-of-installed-product-tp7579458p7579483.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Patching Components with different GUIDs?

2012-07-19 Thread Farrukhw

Hi Guys,
Is that possible to Patch a Component whose GUID was changed in Updated
build?
Pyro gives an error:



I know if I change the GUID in my updated msi back to the one which was in
Original msi. But I have a case in which a great number of GUIDs (might be
in thousands) have to be updated then.

Any suggestions please??

Thanks

--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Patching-Components-with-different-GUIDs-tp7579493.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Patching Components with different GUIDs?

2012-07-19 Thread Farrukhw

Hi Peter,
Thanks for your reply..

I've given msi builds which were not designed by me and after Pyro's
complaint, I investigated that in every build, same named components got new
Component ID (GUID).

Although, I've informed the owners and asked them if they are changing the
Component IDs for each build, but I'm also thinking to write a script to
extract the GUIDs from original msi and update/correct in updated msi, but I
know it would not be a good idea...

Regards
Farrukh

--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Patching-Components-with-different-GUIDs-tp7579493p7579496.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Burn: Managed Boostrapper upgrade but Installs side by side with older version

I'm struggling with my Custom Boostrapper Upgrade issue. By following  this
stackoverflow thread

 
, I'm using LaunchAction.Install.

This does Upgrade the Product as well as Boostrapper, but older Bootstrapper
remains there, as shown in following screen shot.

 

If I invoke ver 1.0.0.0 from here, it would display Dialog to Install, but
would do nothing. However, invoking ver 1.0.1.0 would give me the option to
Uninstall the product. However, upon Uninstall, it would only remove itself,
and "My Product" is left behind.

I also tried with

_bootstrapper.Engine.Plan(LaunchAction.UpdateReplace);
and

_bootstrapper.Engine.Plan(LaunchAction.UpdateReplaceEmbedded);
but it has no effect.

Question: How to upgrade older installation with falling in above situation?
Can anyone please provide a working example of CustomBA upgrade?

Would really appreciate any help in this regard.
Thanks



--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-Managed-Boostrapper-upgrade-but-Installs-side-by-side-with-older-version-tp7592745.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Managing the Performance of Cloud-Based Applications
Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
Read the Whitepaper.
http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Burn: Managed Boostrapper upgrade but Installs side by side with older version

Hi Rob :)
I should have attached the log file before.. Adding the log file from
version 1.0.1.0 while updating 1.0.0.0.
MyProdSoftwareInstaller.log

  

Btw, to me, this doesn't show any indication to be installing side by side.
But I'm not good with logs files.

Please guide.

Thanks





--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-Managed-Boostrapper-upgrade-but-Installs-side-by-side-with-older-version-tp7592745p7592760.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Managing the Performance of Cloud-Based Applications
Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
Read the Whitepaper.
http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Burn: Managed Boostrapper upgrade but Installs side by side with older version

Yes, that may be because before Apply Complete, it is not finished and
-uninstall is failing.
from last lines: 
26D4:2C38][2014-02-19T08:42:31]i301: Applying execute package:
{c0489d1d-654e-4caa-9f95-0fe034d74cc6}, action: Uninstall, path:
C:\Users\Farrukh\AppData\Local\Package
Cache\{c0489d1d-654e-4caa-9f95-0fe034d74cc6}\MyProdSoftwareInstaller.exe,
arguments: '"C:\Users\Farrukh\AppData\Local\Package
Cache\{c0489d1d-654e-4caa-9f95-0fe034d74cc6}\MyProdSoftwareInstaller.exe"
-uninstall -quiet -burn.related.upgrade' 
[26D4:2C38][2014-02-19T08:42:42]i319: Applied execute package:
{c0489d1d-654e-4caa-9f95-0fe034d74cc6}, result: 0x0, restart: None 
[26D4:2C38][2014-02-19T08:42:42]i351: Removing cached package: MainProduct,
from path: C:\Users\Farrukh\AppData\Local\Package
Cache\{0CD51F14-9566-44BD-AB1D-04E65B2AF229}v1.0.1.0\ 

I tested 'MyProdSoftwareInstaller.exe" -uninstall" and it has no effect. So
looks like burn engine is issuing -uninstall, but
MyProdSoftwareInstaller.exe is not responding to -uninstall.

I wonder where -uninstall or other arguments are passed to Burn Engine.. ? 

Any hint/guide?



--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-Managed-Boostrapper-upgrade-but-Installs-side-by-side-with-older-version-tp7592745p7592762.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Managing the Performance of Cloud-Based Applications
Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
Read the Whitepaper.
http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Burn: Managed Boostrapper upgrade but Installs side by side with older version

Sean,
There was Environment.Exist(this.FinalResult) in ApplyComplete(). Now
replaced with:
this.FinalResult = e.Status; //Storing the final status code.
bootstrapperApplication.Engine.Quit(e.Status);

Please find latest log attached with this reply.

However, I've figured out that "this.Command.GetCommandLineArgs().Length()"
is 0 if I pass -uninstall or -log (Bootstrapper's command line). But when I
pass -Sean or -Farrukh, its length > 0, and it does recognize these.

>From log, it looks like -uninstall has no effect upon it. Now I'm wondering
where bootstrapper's arguments are vanishing?


On Wed, Feb 19, 2014 at 9:26 AM, Sean Hall [via Windows Installer XML (WiX)
toolset]  wrote:

> The line
>
> [26D4:2C38][2014-02-19T08:42:31]i301: Applying execute package:
> {c0489d1d-654e-4caa-9f95-0fe034d74cc6}, action: Uninstall, path:
> C:\Users\Farrukh\AppData\Local\Package
> Cache\{c0489d1d-654e-4caa-9f95-0fe034d74cc6}\MyProdSoftwareInstaller.exe,
> arguments: '"C:\Users\Farrukh\AppData\Local\Package
> Cache\{c0489d1d-654e-4caa-9f95-0fe034d74cc6}\MyProdSoftwareInstaller.exe"
> -uninstall -quiet -burn.related.upgrade'
>
> seems to be fine because the very next line says the exit code was 0.
>
> [26D4:2C38][2014-02-19T08:42:42]i319: Applied execute package:
> {c0489d1d-654e-4caa-9f95-0fe034d74cc6}, result: 0x0, restart: None
>
> Since there's no Apply complete, that makes me think that either your BA
> is hanging or someone killed your setup application process.  Although I
> guess it's possible that the engine crashed.
>
> Sean
>
>
> > Date: Tue, 18 Feb 2014 20:09:08 -0800
> > From: [hidden email]
> > To: [hidden email]
> > Subject: Re: [WiX-users] Burn: Managed Boostrapper upgrade but Installs
> side by side with older version
> >
> > Yes, that may be because before Apply Complete, it is not finished and
> > -uninstall is failing.
> > from last lines:
> > 26D4:2C38][2014-02-19T08:42:31]i301: Applying execute package:
> > {c0489d1d-654e-4caa-9f95-0fe034d74cc6}, action: Uninstall, path:
> > C:\Users\Farrukh\AppData\Local\Package
> >
> Cache\{c0489d1d-654e-4caa-9f95-0fe034d74cc6}\MyProdSoftwareInstaller.exe,
> > arguments: '"C:\Users\Farrukh\AppData\Local\Package
> >
> Cache\{c0489d1d-654e-4caa-9f95-0fe034d74cc6}\MyProdSoftwareInstaller.exe"
> > -uninstall -quiet -burn.related.upgrade'
> > [26D4:2C38][2014-02-19T08:42:42]i319: Applied execute package:
> > {c0489d1d-654e-4caa-9f95-0fe034d74cc6}, result: 0x0, restart: None
> > [26D4:2C38][2014-02-19T08:42:42]i351: Removing cached package:
> MainProduct,
> > from path: C:\Users\Farrukh\AppData\Local\Package
> > Cache\{0CD51F14-9566-44BD-AB1D-04E65B2AF229}v1.0.1.0\
> >
> > I tested 'MyProdSoftwareInstaller.exe" -uninstall" and it has no effect.
> So
> > looks like burn engine is issuing -uninstall, but
> > MyProdSoftwareInstaller.exe is not responding to -uninstall.
> >
> > I wonder where -uninstall or other arguments are passed to Burn Engine..
> ?
> >
> > Any hint/guide?
> >
> >
> >
> > --
> > View this message in context:
> http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-Managed-Boostrapper-upgrade-but-Installs-side-by-side-with-older-version-tp7592745p7592762.html
>
> > Sent from the wix-users mailing list archive at Nabble.com.
> >
> >
> --
>
> > Managing the Performance of Cloud-Based Applications
> > Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
> > Read the Whitepaper.
> >
> http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk
> > ___
> > WiX-users mailing list
> > [hidden email] 
> > https://lists.sourceforge.net/lists/listinfo/wix-users
>
> --
>
> Managing the Performance of Cloud-Based Applications
> Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
> Read the Whitepaper.
>
> http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk
> ___
> WiX-users mailing list
> [hidden email] 
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>
> --
>  If you reply to this email, your message will be added to the discussion
> below:
>
> http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-Managed-Boostrapper-upgrade-but-Installs-side-by-side-with-older-version-tp7592745p7592763.html
>  To unsubscribe from Burn: Managed Boostrapper upgrade but Installs side
> by side with older version, click 
> here

Re: [WiX-users] Burn: Managed Boostrapper upgrade but Installs side by side with older version

So when if found (Engine.Detect) that 1.0.0.0 is there, the Command got
Uninstall automatically. But we are invoking our UI dialogs here like:

if(MyViewModel.PState==PackageState.Absent)
   Application.Run(BootStrapDlgs.Welcome_Dlg);  //Let's start with
Welcome Dlg
 else
 Application.Run(BootStrapDlgs.Install_Uninstall_Repair_Dlg);

And I can see that it doesn't do Uninstall, instead it is launching the
Install_Uninstall_Repair_Dlg where Update button is available. However, that
in turn executes Welcome_Dlg of 1.0.0.0 and shows the Install button.

How to make it respect -uninstall and -quite arguments?



--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-Managed-Boostrapper-upgrade-but-Installs-side-by-side-with-older-version-tp7592745p7592766.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Managing the Performance of Cloud-Based Applications
Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
Read the Whitepaper.
http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Burn: Managed Boostrapper upgrade but Installs side by side with older version

2014-02-24 Thread Farrukhw

Any good response? 



--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-Managed-Boostrapper-upgrade-but-Installs-side-by-side-with-older-version-tp7592745p7592881.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Flow-based real-time traffic analytics software. Cisco certified tool.
Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer
Customize your own dashboards, set traffic alerts and generate reports.
Network behavioral analysis & security monitoring. All-in-one tool.
http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] WixBA shows No .Net Framework installed

2014-02-24 Thread Farrukhw

Experimentally, I simply copied WixBA project from Wix 3.7 source. Replaced
the reference from core.csproj to BootstrapperCore and tried to use it with
my own Bundle which is working fine with my own Manged Bootstrapper. It
built fine. But strangely, when I tried to run it, it showed me the dialog
to install .Net framework. And I already have .Net framework 4.5 installed.
I even tried with changing the WixBA's Targetframework to 4.5, but resulted
in same thing.

Why is that so? Is there any security technique used, so that no other
Bundle can be used with it? If yes, then I'm curious to know?



--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/WixBA-shows-No-Net-Framework-installed-tp7592880.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Flow-based real-time traffic analytics software. Cisco certified tool.
Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer
Customize your own dashboards, set traffic alerts and generate reports.
Network behavioral analysis & security monitoring. All-in-one tool.
http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Managed BA command line not effective

2014-02-24 Thread Farrukhw

While playing with  TestBA Bootstrapper from Bryan

 
, first I installed 1.0.0.0. 
Then I incremented version to 1.0.0.1 and logged the process. Here is the
part where -uninstall -quite command line was passed during upgrade:

[2870:21C0][2014-02-24T17:46:38]i300: Apply begin
[1A44:1E54][2014-02-24T17:46:41]i360: Creating a system restore point.
[1A44:1E54][2014-02-24T17:47:15]i361: Created a system restore point.
[1A44:1E54][2014-02-24T17:47:15]i000: Caching bundle from:
'C:\Users\fwaheed\AppData\Local\Temp\{57a07296-0310-4628-971c-2da38aa09f25}\.be\BootstrapperSetup.exe'
to: 'C:\ProgramData\Package
Cache\{57a07296-0310-4628-971c-2da38aa09f25}\BootstrapperSetup.exe'
[1A44:1E54][2014-02-24T17:47:15]i320: Registering bundle dependency
provider: {57a07296-0310-4628-971c-2da38aa09f25}, version: 1.0.0.1
[1A44:2B40][2014-02-24T17:47:16]i305: Verified acquired payload:
DummyInstallationPackageId at path: C:\ProgramData\Package
Cache\.unverified\DummyInstallationPackageId, moving to:
C:\ProgramData\Package
Cache\{F1D62AA5-E68C-4B99-A6DD-D7EAE5A1D238}v1.0.0.1\DummyInstaller.msi.
[1A44:1E54][2014-02-24T17:47:16]i323: Registering package dependency
provider: {F1D62AA5-E68C-4B99-A6DD-D7EAE5A1D238}, version: 1.0.0.1, package:
DummyInstallationPackageId
[1A44:1E54][2014-02-24T17:47:16]i301: Applying execute package:
DummyInstallationPackageId, action: Install, path: C:\ProgramData\Package
Cache\{F1D62AA5-E68C-4B99-A6DD-D7EAE5A1D238}v1.0.0.1\DummyInstaller.msi,
arguments: ' ARPSYSTEMCOMPONENT="1" MSIFASTINSTALL="7"'
[2870:21C0][2014-02-24T17:47:22]i319: Applied execute package:
DummyInstallationPackageId, result: 0x0, restart: None
[1A44:1E54][2014-02-24T17:47:22]i325: Registering dependency:
{57a07296-0310-4628-971c-2da38aa09f25} on package provider:
{F1D62AA5-E68C-4B99-A6DD-D7EAE5A1D238}, package: DummyInstallationPackageId
[1A44:1E54][2014-02-24T17:47:22]i301: Applying execute package:
{f1d57671-5e3d-4be7-908f-5a47e72737d9}, action: Uninstall, path:
C:\ProgramData\Package
Cache\{f1d57671-5e3d-4be7-908f-5a47e72737d9}\BootstrapperSetup.exe,
*arguments: '"C:\ProgramData\Package
Cache\{f1d57671-5e3d-4be7-908f-5a47e72737d9}\BootstrapperSetup.exe"
-uninstall -quiet -burn.related.upgrade*'
[2870:21C0][2014-02-24T17:48:54]i319: Applied execute package:
{f1d57671-5e3d-4be7-908f-5a47e72737d9}, result: 0x0, restart: None
[2870:21C0][2014-02-24T17:48:54]i399: Apply complete, result: 0x0, restart:
None, ba requested restart:  No
[2870:21C0][2014-02-24T17:48:55]i500: Shutting down, exit code: 0x0

*Problem: Instead of quietly uninstalling, it would display the Uninstall
Dialog. * And if I click Uninstall, it would uninstall 1.0.0.0 and then
application would be upgraded to 1.0.0.1.

*Question: How to make it understand its command line arguments and do the
process without showing Uninstall Dialog box?*

I also consulted in WixBA project from Wix 3.7 source, but its command line
handling is only handling InstallFolder argument.

I would really appreciate any help, as this upgrade scenario is block my
Bootstrapper project.

Thanks a bunch.



--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Managed-BA-command-line-not-effective-tp7592884.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Flow-based real-time traffic analytics software. Cisco certified tool.
Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer
Customize your own dashboards, set traffic alerts and generate reports.
Network behavioral analysis & security monitoring. All-in-one tool.
http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Is this a Bug in Wix Bootstrapper command line?

2014-02-25 Thread Farrukhw

I already posted a related problem here:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Managed-BA-command-line-not-effective-td7592884.html
and
http://stackoverflow.com/questions/21989084/wix-managed-ba-command-line-not-effective,
which is about command line passed during upgrade.

Now I tried to explore, how it interpret the command line. Here is my run
method to do so:

protected override void Run()
{
  string cmdOptions = string.Empty;
  this.Engine.Log(LogLevel.Verbose, "Launching custom TestBA UX");

   foreach (string cmdOpt in this.Command.GetCommandLineArgs())
   {
  cmdOptions += cmdOpt + "\n"; //collecting command line options
passed.
   }

Debug.WriteLine("Command.Display: {0} Command.Action: {1}",
this.Command.Display.ToString(), this.Command.Action.ToString());
   Environment.Exit(1);
}

I understand that Wixdba would digest its own command line options and would
pass extra to our Managed Bootstrapper Application. From above mentioned
post, this line from log:

[1A44:1E54][2014-02-24T17:47:22]i301: Applying execute package:
{f1d57671-5e3d-4be7-908f-5a47e72737d9}, action: Uninstall, path:
C:\ProgramData\Package
Cache\{f1d57671-5e3d-4be7-908f-5a47e72737d9}\BootstrapperSetup.exe,
arguments: '"C:\ProgramData\Package
Cache\{f1d57671-5e3d-4be7-908f-5a47e72737d9}\BootstrapperSetup.exe"
-uninstall -quiet -burn.related.upgrade'

shows that it is passing -uninstall and -quiet to BootstrapperSetup.exe
which is in cache i.e. already installed there.

Here are the results of command line options passed to Bootstrapper:

/C:\bin\Debug>BootstrapperSetup.exe -quite -uninstall/
*Command.Display: Full,  Command.Action: Uninstall * 

/C:\bin\Debug>>BootstrapperSetup.exe -q -uninstall/
*Command.Display: None  Command.Action: Uninstall*

/C:\bin\Debug>>BootstrapperSetup.exe -q -u/
*Command.Display: None  Command.Action: Install*


*Summary:* From above test, it seems that 

 1. -quite is not effective, while -q does.
 2. -u is not effective, while -Uninstall does.

Although, after knowing this, I can parse for -quite and -u in my Managed
Bootstrapper, but I would like to know, *If it is a Bug or I'm doing
something wrong here*.

Best regards



--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Is-this-a-Bug-in-Wix-Bootstrapper-command-line-tp7592912.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Flow-based real-time traffic analytics software. Cisco certified tool.
Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer
Customize your own dashboards, set traffic alerts and generate reports.
Network behavioral analysis & security monitoring. All-in-one tool.
http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Wix Bootstrapper maximum number of packages and file size limit

2014-03-19 Thread Farrukhw

Sorry, if this is a re-post.

We have lots of third party components (msi, exe installer) to be delivered
on user's machine. Although, there is a main script, used to install these
in a required sequence on user's machine, but for delivery purposes, we are
creating one self extracting archive using WinRAR. Its size is 3.50 GB at
this time.

*Problem:* When we tried to sign this exe using signtool (use similar to
sign our other binaries), it always got corrupted and become unusable.

Now we are thinking to pack these in Wix based bootstrapper and do the
installation on target machine. However we are unaware about Bootstrapper's
file size maximum limit.

*Questions:* 
1-How many number of packages can we add in one Bundle? 
2-What is the maximum file size Bundle.exe would be supported?

Regards




--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Wix-Bootstrapper-maximum-number-of-packages-and-file-size-limit-tp7593535.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/13534_NeoTech
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Managed bootstrapper on a PC without .NET framework 4.0

2014-05-16 Thread Farrukhw

Sky, I faced same problem. At the end, we discovered that on Win 7 with no
SP, we are getting this error. When we installed Net Framework 4
(dotNetFx40_Full_x86_x64.exe) on same windows, it started working fine. 

So finally we got to know that on Windows 7 + Service Pack 1, it may work
fine. 

However, I haven't got a chance to test is on fresh Windows 7 with SP1.

Now I'm trying to find out how to avoid this, in case there in Windows 7
with No SP on target machine??



--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Managed-bootstrapper-on-a-PC-without-NET-framework-4-0-tp7592017p7594766.html
Sent from the wix-users mailing list archive at Nabble.com.

--
"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
Instantly run your Selenium tests across 300+ browser/OS combos.
Get unparalleled scalability from the best Selenium testing platform available
Simple to use. Nothing to install. Get started now for free."
http://p.sf.net/sfu/SauceLabs
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Managed bootstrapper on a PC without .NET framework 4.0

2014-05-16 Thread Farrukhw

Ok, just solved this. On Windows 7 without SP1, there is Net FW 3.5. In my
BootstrapperCore.Config file, it was:



 **


*I removed .* This causes
bootstrapper to launch .Net FW 4.0 installation (Packed with as payload). It
updated the machine with .Net FW 4 and then launched my bootstrapper, and
now working like charm.. :)

Hope, it would help you as well.



--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Managed-bootstrapper-on-a-PC-without-NET-framework-4-0-tp7592017p7594767.html
Sent from the wix-users mailing list archive at Nabble.com.

--
"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
Instantly run your Selenium tests across 300+ browser/OS combos.
Get unparalleled scalability from the best Selenium testing platform available
Simple to use. Nothing to install. Get started now for free."
http://p.sf.net/sfu/SauceLabs
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] Using '*' in Component Guids and Patches

2014-05-25 Thread Farrukhw

Hi
While searching for best practices, I came across  this thread

 
, which is discussing the use of '*' instead of GUIDs in components. 

As far I know, while generating GUID dynamically from '*', if the
destination of a Component is changes, so its GUID would also be changed.
There may be some other factors as well.

Let's say we released ver 1.0.0.0 and then in 1.0.1.0 we changed the
destination of a Component from Dir1 to Dir2.

*Question:* If we generate Differential Patch between these two versions,
would the file get patched who's destination was changed in ver 1.0.1.0?
Would using '*' in this case would be good?

Regards
Farrukh





--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Using-in-Component-Guids-and-Patches-tp7594909.html
Sent from the wix-users mailing list archive at Nabble.com.

--
The best possible search technologies are now affordable for all companies.
Download your FREE open source Enterprise Search Engine today!
Our experts will assist you in its installation for $59/mo, no commitment.
Test it for FREE on our Cloud platform anytime!
http://pubads.g.doubleclick.net/gampad/clk?id=145328191&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Using '*' in Component Guids and Patches

2014-05-28 Thread Farrukhw

It might not be a common practice, but I faced it due to some customer
requirement when we have to move a dll to another location. So ethically,
it should be a Major Upgrade which would handle it with no problem. But I
was asked to build a patch, as it is just one dll,

So we build a new dll with a new incremented version and while sing same
GUID for the component, patch didn't moved the file to new location, but
did updated the dll to the new version.

However, I tried to reproduced this using "*" instead of GUID and it simply
didn't worked.



On Thu, May 29, 2014 at 3:43 AM, Bryan Wolf-2 [via Windows Installer XML
(WiX) toolset]  wrote:

> You should change the component code if the destination of the component
> changes, as documented here:
> http://msdn.microsoft.com/en-us/library/aa367849(v=vs.85).aspx
>
> Changing the component code is incompatible with minor/small updates;
> since
> you're talking about a patch and a major upgrade patch is more or less a
> non-feature, the short answer is that it won't work. Don't change the path
> of a component during the course of a patch - it's just not a compatible
> use case.
>
> Technically speaking, you can make it work through careful and very
> elaborate tailoring of the MSI package and manipulation of the feature
> tree, but you really really don't want to do this :-)
>
>
> On Wed, May 28, 2014 at 5:29 PM, Rob Mensching <[hidden 
> email]<http://user/SendEmail.jtp?type=node&node=7594938&i=0>>
> wrote:
>
> > IIRC, I don't think that's going to work out well. You can try but I
> think
> > patching across directory moves probably doesn't work out great since
> IIRC
> > moving Component directories during repair doesn't tend to work out real
> > well either. But that's just from memory...
> >
> > ___
> >  FireGiant  |  Dedicated support for the WiX toolset  |
> > http://www.firegiant.com/
> >
> > -Original Message-
> > From: Farrukhw [mailto:[hidden 
> > email]<http://user/SendEmail.jtp?type=node&node=7594938&i=1>]
>
> > Sent: Sunday, May 25, 2014 10:13 PM
> > To: [hidden email]<http://user/SendEmail.jtp?type=node&node=7594938&i=2>
> > Subject: [WiX-users] Using '*' in Component Guids and Patches
> >
> > Hi
> > While searching for best practices, I came across  this thread <
> >
> http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Best-Practices-Using-quot-quot-for-GUID-automation-td5234716.html
> > >
> > , which is discussing the use of '*' instead of GUIDs in components.
> >
> > As far I know, while generating GUID dynamically from '*', if the
> > destination of a Component is changes, so its GUID would also be
> changed.
> > There may be some other factors as well.
> >
> > Let's say we released ver 1.0.0.0 and then in 1.0.1.0 we changed the
> > destination of a Component from Dir1 to Dir2.
> >
> > *Question:* If we generate Differential Patch between these two
> versions,
> > would the file get patched who's destination was changed in ver 1.0.1.0?
> > Would using '*' in this case would be good?
> >
> > Regards
> > Farrukh
> >
> >
> >
> >
> >
> > --
> > View this message in context:
> >
> http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Using-in-Component-Guids-and-Patches-tp7594909.html
> > Sent from the wix-users mailing list archive at Nabble.com.
> >
> >
> >
> --
>
> > The best possible search technologies are now affordable for all
> companies.
> > Download your FREE open source Enterprise Search Engine today!
> > Our experts will assist you in its installation for $59/mo, no
> commitment.
> > Test it for FREE on our Cloud platform anytime!
> >
> >
> http://pubads.g.doubleclick.net/gampad/clk?id=145328191&iu=/4140/ostg.clktrk
> > ___
> > WiX-users mailing list
> > [hidden email] <http://user/SendEmail.jtp?type=node&node=7594938&i=3>
> > https://lists.sourceforge.net/lists/listinfo/wix-users
> >
> >
> >
> --
>
> > Time is money. Stop wasting it! Get your web API in 5 minutes.
> > www.restlet.com/download
> > http://p.sf.net/sfu/restlet
> > ___
> > WiX-u

Re: [WiX-users] Using '*' in Component Guids and Patches

2014-05-30 Thread Farrukhw

That's not a differential patch. Its a minor upgrade using the msi... 



--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Wix-Patches-and-using-instead-of-Component-Guids-tp7594909p7594962.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Time is money. Stop wasting it! Get your web API in 5 minutes.
www.restlet.com/download
http://p.sf.net/sfu/restlet
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] HarvestDirectory target for multiple directories

2014-09-19 Thread Farrukhw

I'm trying to harvest different folders in my *.wixproj file. But
HeatDirectory task is only harvesting last HarvestDirectory target. What I'm
missing here?

Here is my code segment:

 

  Components.wxs


  
  

  true
  SimpleWebAppGroup
  INSTALLFOLDER
  true
  true
  var.SourceDir
 false



  true
  SVNOverLays
  PROGFILES
  true
  true
  var.SourceDir
  false

  
  
  

  

  


If I omit HeatDirectory task, it would definitely not updating
Component.wxs. I didn't find any example showing the use of HarvestDirectory
with HeatDirectory task. While  Wix documentation

  
shows that HarvestDirectory target passes HarvestDirectory items to the
HeatDirectory task to generate authoring from a file. 

Any help would be really appreciated.




--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/HarvestDirectory-target-for-multiple-directories-tp7596917.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Slashdot TV.  Video for Nerds.  Stuff that Matters.
http://pubads.g.doubleclick.net/gampad/clk?id=160591471&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] HeatDirectory failure on TFS

Hi experts, 
I'm using HeatDirectory task in my *.wixproj file, which is working very
fine on my machine, being built locally.

However, on TFS, it is failing with following error:

C:\Program Files (x86)\WiX Toolset v3.8\bin\Heat.exe dir
D:\Builds\32\48\bin\Debug\InstallSrc\WebApp\ -cg CompGrp_WebApp -dr WebApp
-ke -scom -sreg -srd -var var.WebAppSrc -v -ag -sfrag -suid -out WebApp_.wxs
 Could not load file or assembly 'file:///C:\Program Files (x86)\WiX
Toolset v3.8\bin\Heat.exe' or one of its dependencies. An attempt was made
to load a program with an incorrect format.
at System.Reflection.RuntimeAssembly._nLoad(AssemblyName
fileName, String codeBase, Evidence assemblySecurity, RuntimeAssembly
locationHint, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean
throwOnFileNotFound, Boolean forIntrospection, Boolean
suppressSecurityChecks)
at
System.Reflection.RuntimeAssembly.InternalLoadAssemblyName(AssemblyName
assemblyRef, Evidence assemblySecurity, RuntimeAssembly reqAssembly,
StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean
throwOnFileNotFound, Boolean forIntrospection, Boolean
suppressSecurityChecks)
at
System.Reflection.RuntimeAssembly.InternalLoadAssemblyName(AssemblyName
assemblyRef, Evidence assemblySecurity, RuntimeAssembly reqAssembly,
StackCrawlMark& stackMark, Boolean throwOnFileNotFound, Boolean
forIntrospection, Boolean suppressSecurityChecks)
at System.Reflection.RuntimeAssembly.InternalLoadFrom(String
assemblyFile, Evidence securityEvidence, Byte[] hashValue,
AssemblyHashAlgorithm hashAlgorithm, Boolean forIntrospection, Boolean
suppressSecurityChecks, StackCrawlMark& stackMark)
at System.Reflection.Assembly.LoadFrom(String assemblyFile)
at
Microsoft.Tools.WindowsInstallerXml.Build.Tasks.WixToolTask.ExecuteToolThread(Object
parameters)
 0>MSBUILD : error MSB4166: Child node "3" exited prematurely. Shutting
down. Diagnostic information may be found in files in the temporary files
directory named MSBuild_*.failure.txt.


However, on same build machine, I tried to execute heat command line
(generated by above log) and got it working fine: i.e.
C:\Program Files (x86)\WiX Toolset v3.8\bin\Heat.exe dir
D:\Builds\32\48\bin\Debug\InstallSrc\WebApp\ -cg CompGrp_WebApp -dr WebApp
-ke -scom -sreg -srd -var var.WebAppSrc -v -ag -sfrag -suid -out WebApp_.wxs



I even tried it, by disabling MsBuild Multi-Proc (building projects in
parallel) in TFS definition, but in vain.

Why it is failing on TFS, but not locally?

Thanks a bunch.





--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/HeatDirectory-failure-on-TFS-tp7596956.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] HeatDirectory failure on TFS

Hi John,
Thanks for reply. Presently, MSBuild PlatForm is Auto. 
However, I'm just wondering how the command line generated in MsBuild log
working on command line? In addition, same MsBuild project is working just
fine if we build it in Visual Studio or using MsBuild command line.






--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/HeatDirectory-failure-on-TFS-tp7596956p7596972.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] HeatDirectory failure on TFS

I will try that in morning.. but we are also building 64 bit projects in our
solution. Would these be affected?



--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/HeatDirectory-failure-on-TFS-tp7596956p7596974.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] HeatDirectory failure on TFS

Hi John, eyoung100
<http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/template/NamlServlet.jtp?macro=user_nodes&user=396493>
Thanks a lot Guys. This worked, at least it is building properly now...

Really appreciated

On Wed, Sep 24, 2014 at 11:52 PM, John Cooper-2 [via Windows Installer XML
(WiX) toolset]  wrote:

> No.  All of my projects are 64-bit.  The X86 just instructs the workflow
> to use the 32-bit MSBuild.
>
> --
> John Merryweather Cooper
> Senior Software Engineer | Enterprise Service Applications | Continuing
> Development
> Jack Henry & Associates, Inc.® | Lenexa, KS  66214 | Ext:  431050 |[hidden
> email] <http://user/SendEmail.jtp?type=node&node=7596975&i=0>
>
>
>
> -Original Message-
> From: Farrukhw [mailto:[hidden email]
> <http://user/SendEmail.jtp?type=node&node=7596975&i=1>]
> Sent: Wednesday, September 24, 2014 1:38 PM
> To: [hidden email] <http://user/SendEmail.jtp?type=node&node=7596975&i=2>
> Subject: Re: [WiX-users] HeatDirectory failure on TFS
>
> I will try that in morning.. but we are also building 64 bit projects in
> our solution. Would these be affected?
>
>
>
> --
> View this message in context:
> http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/HeatDirectory-failure-on-TFS-tp7596956p7596974.html
> Sent from the wix-users mailing list archive at Nabble.com.
>
> --
>
> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve
> PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you
> Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI
> DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
> http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
> ___
> WiX-users mailing list
> [hidden email] <http://user/SendEmail.jtp?type=node&node=7596975&i=3>
> https://lists.sourceforge.net/lists/listinfo/wix-users
> NOTICE: This electronic mail message and any files transmitted with it are
> intended
> exclusively for the individual or entity to which it is addressed. The
> message,
> together with any attachment, may contain confidential and/or privileged
> information.
> Any unauthorized review, use, printing, saving, copying, disclosure or
> distribution
> is strictly prohibited. If you have received this message in error, please
> immediately advise the sender by reply email and delete all copies.
>
>
> --
>
> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
>
> http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
> ___
> WiX-users mailing list
> [hidden email] <http://user/SendEmail.jtp?type=node&node=7596975&i=4>
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>
> --
>  If you reply to this email, your message will be added to the discussion
> below:
>
> http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/HeatDirectory-failure-on-TFS-tp7596956p7596975.html
>  To unsubscribe from HeatDirectory failure on TFS, click here
> <http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=7596956&code=ZmFycnVraDFAZ21haWwuY29tfDc1OTY5NTZ8LTcxNDU3NzEzNQ==>
> .
> NAML
> <http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>




--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/HeatDirectory-failure-on-TFS-tp7596956p7596980.html
Sent from the wix-users mailing list archive at Nabble.com.
--
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] HeatDirectory failure on TFS

2014-09-25 Thread Farrukhw

Just updated my  query on StackOverflow

   



--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/HeatDirectory-failure-on-TFS-tp7596956p7596981.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[WiX-users] TFS: Wix can't see its source files if using TfvcTemplate.12.xaml.

I need to use TfvcTemplate.12.xaml because of its Pre and Post build script
execution support and I need to run a Powershell script as PreBuild event.

On TFS 2013, Building a Wix project using old DefaultTemplate.xaml works
fine. While trying to build using new default template TfvcTemplate.12.xaml
builds the csharp project fine, but Wix is unable to find its files, while
files are present at same location. 

Here is the log from TFS:




I verified multiple times that files are there and it builds without any
problem at command line using MsBuild and Wix Tool set as well. 

I'm unable to figure out why using TfvcTemplate.12.xaml, wix is unable to
see its files while these are present intact there



Any help would be really appreciated.





--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/TFS-Wix-can-t-see-its-source-files-if-using-TfvcTemplate-12-xaml-tp7597267.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://p.sf.net/sfu/Zoho
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] TFS: Wix can't see its source files if using TfvcTemplate.12.xaml.

Well, I got it with 2013 actually and I'm trying to run a script for
versioning, just according to  this msdn article
  

and it is working just as guided and expected. But Wix's behavior is not as
expected. However, I do have a Wix project on another TFS repository which
is working fine with same parameters. But I can't figure out what's wrong
now while using with other projects...?



--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/TFS-Wix-can-t-see-its-source-files-if-using-TfvcTemplate-12-xaml-tp7597267p7597271.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://p.sf.net/sfu/Zoho
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] TFS: Wix can't see its source files if using TfvcTemplate.12.xaml.

I've set to Unrestricted for the sake for making things run. But it is even
failing when no script is specified, i.e. simply building Solution just as
we were doing in older DefaultTemplate... 



--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/TFS-Wix-can-t-see-its-source-files-if-using-TfvcTemplate-12-xaml-tp7597267p7597276.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://p.sf.net/sfu/Zoho
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] TFS: Wix can't see its source files if using TfvcTemplate.12.xaml.