Re: [WiX-users] Votive / WiX not releasing handles on extension dlls after build.
On 13-05-2012 23:42, Rob Mensching wrote: Yeah, pain isn't it. Visual Studio holds lock on MSBuild tasks as well. !Truly! Have you any experience executing the extension in a new separate AppDomain and thereby being able to unload it again? I started out but ended up in a dark alley of missing dependencies... /Morten -- 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] Votive / WiX not releasing handles on extension dlls after build.
When building a setup project using Votive in Visual Studio, a handle is kept on any extension dlls even after the build has completed. This poses two problems to me: 1. Developing extensions is a slow process, because Visual Studio has to be restarted every time I have to make a change to the extension. In order to release the lock on the extension dll. 2. If an extension loads an assembly from the product itself (the product being released with the setup project) that assembly is loaded into the AppDomain where the extension is running. As a consequence that is not released either, after the build has been completed. This means the product cannot be rebuild if the setup project has been build without restarting Visual Studio. Is there a way around this and release the locks on the assemblies without restarting Visual Studio, or will I have to run WiX manually from the command line? Thanks, Morten -- 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] WIX Setup Project says A reference dll could not be added in VS2010
I am creating a WIX installer project. When I am trying to add the reference: Microsoft.ReportViewer.Common.dll and Microsoft.ReportViewer.WinForms.dll, I got the error mentioned on the title. I searched online but can't find any useful info. My DLLs are located in C:\Program Files(x86)\Microsoft Visual Studio 10.0\ReportViewer, so it is not like a question mentioned by somebody when they are referencing to a dll located on network share. I am totally new to WIX and deployment project, so a little bit explanation on what happens will be appreciated! As I understand it, you basically add references in your installer projects for two reasons: 1. You create a reference to another project - the project you wish to install. By creating a reference, you ensure the project is build, when the installer project is build and you get access to some preprocessor variables. 2. You have WiX extension dlls that somehow add to the functionality of wix. You cannot add a reference to a regular dll. Dlls that should be included in the installation should be included by the use of File tags. Have you had a look at this tutorial: http://wix.tramontana.co.hu/tutorial /Regards, Morten -- 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] Managing dependencies to preprocessor extensions
I have written a preprocessor extension that has a dependency to another assembly. When I try to build a setup project using that extension, I get an error saying: In the preprocessor extension that handles prefix 'somePrefix' while trying to call function 'someFunction' and exception has occurred : Could not load file or assembly 'ExntensionDependency, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The system cannot find the file specified. The file ExtensionDependency.dll is located in the same folder as the wix extension Extension.dll. The assembly ExtensionDependency only has dependencies to System and System.Core. I have tried to have both files in a sub directory of the setup project and in the Wix/Bin folder. Both without success. Can I somehow use the dependency without placing it in the GAC? I'm using v. 3.5.2519.0 with Visual Studio. Thanks, Morten -- 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] Managing dependencies to preprocessor extensions
On 10-05-2012 14:31, Simon Dahlbacka wrote: The name in the error message and the name of the dll is spelled differently, can it be as simple as that? Sorry, that is just a typo I introduced when replacing the original assembly name. The names are the same in the two places. /Morten -- 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] Managing dependencies to preprocessor extensions
On 10-05-2012 14:00, Morten Lemvigh wrote: I have written a preprocessor extension that has a dependency to another assembly. When I try to build a setup project using that extension, I get an error saying: In the preprocessor extension that handles prefix 'somePrefix' while trying to call function 'someFunction' and exception has occurred : Could not load file or assembly 'ExntensionDependency, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The system cannot find the file specified. Just to make things clear: I have no problem creating a console application, linking it to the same preprocessor dll and making a manual call to: public override string EvaluateFunction(string prefix, string function, string[] args) -- 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] Omitting the license agreement in standard UIs
Hi, I'm trying the omit the license agreement in one of the standard UIs (WixUI_FeatureTree). I succeed in skipping the license agreement, when I press 'Next' in the WelcomeDlg, but when I press 'Back' on the CustomizeDlg, it always goes to the license agreement instead of the WelcomeDlg. What I have is the following: UI Id=UI_NoLicense UIRef Id=WixUI_FeatureTree / UIRef Id=WixUI_ErrorProgressText / Publish Dialog=CustomizeDlg Control=Back Event=NewDialog Value=WelcomeDlg Order=11/Publish Publish Dialog=WelcomeDlg Control=Next Event=NewDialog Value=CustomizeDlg1/Publish /UI I've tried various versions of the Publish on the CustomizeDlg.Back but without success, any help would be greatly appreciated! Thanks, Morten -- Virtualization Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Reference an extension dll on a network share
I have a WiX setup project in Visual Studio, and I'm having problems referencing an extension dll. If the dll is located on my local machine, there is no problem adding the reference, but if I try to reference the same dll on a network share, I get the following error message: A reference to [extension].dll could not be added. Please make sure that the file is accessible, and that it is a valid WiX reference. All my C# projects reference dll's at the same network location without any problems. Any ideas of getting around this while keeping the dll on the network share? Regards, Morten -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
