Re: [WiX-users] How do you use VS2005_PROJECTTEMPLATES_DIR, etc... from WixVSExtension
Thanks Rob, that makes sense, I guess :) Not sure if I should file something, but it might be nice to add that to the examples on the WixVSExtension documentation page. For anyone else facing this issue here's how I resolved it... !-- Create dummy directories to assign the VS2005 directory properties to. -- DirectoryRef Id=INSTALLDIR Directory Id=DIR_VS2005_SCHEMAS / Directory Id=DIR_VS2005_PROJECTTEMPLATES / Directory Id=DIR_VS2005_ITEMTEMPLATES / /DirectoryRef PropertyRef Id='VS2005_SCHEMAS_DIR'/ SetDirectory Id=DIR_VS2005_SCHEMAS Value=[VS2005_SCHEMAS_DIR] Sequence=both / PropertyRef Id='VS2005_PROJECTTEMPLATES_DIR'/ SetDirectory Id=DIR_VS2005_PROJECTTEMPLATES Value=[VS2005_PROJECTTEMPLATES_DIR] Sequence=both / PropertyRef Id='VS2005_ITEMTEMPLATES_DIR'/ SetDirectory Id=DIR_VS2005_ITEMTEMPLATES Value=[VS2005_ITEMTEMPLATES_DIR] Sequence=both / -Ian -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rob Mensching Sent: Saturday, July 12, 2008 9:16 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] How do you use VS2005_PROJECTTEMPLATES_DIR, etc... from WixVSExtension VS2005_SCHEMAS_DIR is a Property not a Directory. You can't create a DirectoryRef to a Property. To set a Directory to the value of a Property use the SetDirectory element. For example: SetDirectory Id=Dir_ParentOfMyProjectTemplatesVS2005 Value=[VS2005_SCHEMAS_DIR] Sequence=both / -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ian Sullivan Sent: Friday, July 11, 2008 20:35 To: wix-users@lists.sourceforge.net Subject: [WiX-users] How do you use VS2005_PROJECTTEMPLATES_DIR, etc... from WixVSExtension I'm trying to use PropertyRef Id='VS2005_SCHEMAS_DIR'/ PropertyRef Id='VS2005_PROJECTTEMPLATES_DIR'/ PropertyRef Id='VS2005_ITEMTEMPLATES_DIR'/ PropertyRef Id='VS90_SCHEMAS_DIR'/ PropertyRef Id='VS90_PROJECTTEMPLATES_DIR'/ PropertyRef Id='VS90_ITEMTEMPLATES_DIR'/ For things like DirectoryRef Id=VS2005_PROJECTTEMPLATES_DIR Directory Id=Dir_MyProjectTemplatesVS2005 Name=MyTemplates Component Id=Comp_ProjectTemplatesVS2005 DiskId=1 Guid=$(var.Comp_ProjectTemplatesVS2005_Guid) But I'm getting the following link errors Unresolved reference to symbol 'Directory:VS2005_PROJECTTEMPLATES_DIR' in section 'Fragment:'.Installer\Integration.wxs 302 1 Installer Unresolved reference to symbol 'Directory:VS2005_ITEMTEMPLATES_DIR' in section 'Fragment:'.Installer\Integration.wxs 312 1 Installer Unresolved reference to symbol 'Directory:VS90_PROJECTTEMPLATES_DIR' in section 'Fragment:'.Installer\Integration.wxs 323 1 Installer Unresolved reference to symbol 'Directory:VS90_ITEMTEMPLATES_DIR' in section 'Fragment:'. Installer\Integration.wxs334 1 Installer Unresolved reference to symbol 'Directory:VS2005_SCHEMAS_DIR' in section 'Fragment:'. Installer\Integration.wxs348 1 Installer Unresolved reference to symbol 'Directory:VS90_SCHEMAS_DIR' in section 'Fragment:'. Installer\Integration.wxs362 1 Installer I'm pretty sure I've got the correct WixVSExtension referenced, since these references PropertyRef Id='VS2005DEVENV'/ CustomActionRef Id=VS2005Setup/ seem to work (I don't get any reference errors about VS2005Setup or VS2005DEVENV) Custom Action=VS2005Setup Before=InstallFinalize VS2005DEVENV /Custom Extension Id=myext ContentType=text/xml Verb Id=Open Command=amp;Open in Visual Studio 2005 TargetProperty=VS2005DEVENV Argument=quot;%1quot; / /Extension I'm using version 3.0.4123.0 Any help would be appreciated. Thanks, -Ian Ian Sullivan Software Development Engineer Microsoft Inc., Windows Live Agents: SDK - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08
[WiX-users] How do you use VS2005_PROJECTTEMPLATES_DIR, etc... from WixVSExtension
I'm trying to use PropertyRef Id='VS2005_SCHEMAS_DIR'/ PropertyRef Id='VS2005_PROJECTTEMPLATES_DIR'/ PropertyRef Id='VS2005_ITEMTEMPLATES_DIR'/ PropertyRef Id='VS90_SCHEMAS_DIR'/ PropertyRef Id='VS90_PROJECTTEMPLATES_DIR'/ PropertyRef Id='VS90_ITEMTEMPLATES_DIR'/ For things like DirectoryRef Id=VS2005_PROJECTTEMPLATES_DIR Directory Id=Dir_MyProjectTemplatesVS2005 Name=MyTemplates Component Id=Comp_ProjectTemplatesVS2005 DiskId=1 Guid=$(var.Comp_ProjectTemplatesVS2005_Guid) But I'm getting the following link errors Unresolved reference to symbol 'Directory:VS2005_PROJECTTEMPLATES_DIR' in section 'Fragment:'.Installer\Integration.wxs 302 1 Installer Unresolved reference to symbol 'Directory:VS2005_ITEMTEMPLATES_DIR' in section 'Fragment:'.Installer\Integration.wxs 312 1 Installer Unresolved reference to symbol 'Directory:VS90_PROJECTTEMPLATES_DIR' in section 'Fragment:'.Installer\Integration.wxs 323 1 Installer Unresolved reference to symbol 'Directory:VS90_ITEMTEMPLATES_DIR' in section 'Fragment:'. Installer\Integration.wxs334 1 Installer Unresolved reference to symbol 'Directory:VS2005_SCHEMAS_DIR' in section 'Fragment:'. Installer\Integration.wxs348 1 Installer Unresolved reference to symbol 'Directory:VS90_SCHEMAS_DIR' in section 'Fragment:'. Installer\Integration.wxs362 1 Installer I'm pretty sure I've got the correct WixVSExtension referenced, since these references PropertyRef Id='VS2005DEVENV'/ CustomActionRef Id=VS2005Setup/ seem to work (I don't get any reference errors about VS2005Setup or VS2005DEVENV) Custom Action=VS2005Setup Before=InstallFinalize VS2005DEVENV /Custom Extension Id=myext ContentType=text/xml Verb Id=Open Command=amp;Open in Visual Studio 2005 TargetProperty=VS2005DEVENV Argument=quot;%1quot; / /Extension I'm using version 3.0.4123.0 Any help would be appreciated. Thanks, -Ian Ian Sullivan Software Development Engineer Microsoft Inc., Windows Live Agents: SDK - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] ProgId referencing dll installed in the GAC
Not sure if this is a bug or user (my) error, but I just tried to add a ProgId that referencing a dll that gets installed into the GAC, after install I see in the registry that the DefaultIcon points to the place where the dll would have been installed if it wasn't being installed into the GAC HKEY_CLASSES_ROOT\Comp.ext.5.0\DefaultIcon C:\Program Files\My App\Comp.dll,1000 DirectoryRef Id=INSTALLDIR Component Id=Comp_GAC DiskId=1 Guid=$(var.Comp_GAC_Guid) File Id=File_Comp.dll Assembly=.net KeyPath=yes Name=Comp.dll Source=$(var.ProjectDLLPath)\Comp.dll / ProgId Id=Comp.ext.5.0 Description=My File Icon=File_Comp.dll IconIndex=1000 Is there any way to get this to work, or do I need to make up a resource container and install it? I saw something about being able to specify an Icon directly if you are advertising a ProgId but when I looked into what advertising meant it sounded like something I shouldn't mess with. -Ian Ian Sullivan Software Development Engineer Microsoft Inc., Windows Live Agents: SDK, Tools, Web Services - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Devenv /setup does half of the work
Are you installing into the GAC? If so you need to run your CA during Commit. From another list “Commit custom actions are risky – they don’t run if rollback is disabled. The problem is that assemblies being installed to the GAC aren’t committed there until the install transaction is being committed during InstallFinalize, so ‘devenv /setup’ before then will fail to find the packages. Unfortunately, by the time the assemblies are in the GAC, there’s no way to run ‘devenv /setup’ with elevated privileges. So commit CAs are risky but about your only choice.” -Ian From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Xin Liu (Intl Vendor) Sent: Monday, September 17, 2007 3:33 AM To: Schrieken, Rene; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Devenv /setup does half of the work As you see it’s a deferred custom action which must be scheduled between InstallInitialize and InstallFinialize. Thanks, Xin Liu Alias: v-liux Group: Protocol Tools Test Team Occupation: Build Engineer Seat: No. 2186 Sigma Plaza, Beijing From: Schrieken, Rene [mailto:[EMAIL PROTECTED] Sent: Monday, September 17, 2007 5:59 PM To: Xin Liu (Intl Vendor); wix-users@lists.sourceforge.net Subject: RE: [WiX-users] Devenv /setup does half of the work Ok, are you sure it is executed at the correct moment? Would it hurt to try to schedule it after InstallFinalize? From: Xin Liu (Intl Vendor) [mailto:[EMAIL PROTECTED] Sent: Monday, September 17, 2007 5:26 AM To: Schrieken, Rene; wix-users@lists.sourceforge.net Subject: RE: [WiX-users] Devenv /setup does half of the work Thanks, Rene. I have tried “//setup” but VisualStudio complained that it is an invalid option. Thanks, Xin Liu Alias: v-liux Group: Protocol Tools Test Team Occupation: Build Engineer Seat: No. 2186 Sigma Plaza, Beijing From: Schrieken, Rene [mailto:[EMAIL PROTECTED] Sent: Friday, September 14, 2007 6:59 PM To: Xin Liu (Intl Vendor); wix-users@lists.sourceforge.net Subject: RE: [WiX-users] Devenv /setup does half of the work Did you try ExeCommand=//setup ? Rene From: [EMAIL PROTECTED] on behalf of Xin Liu (Intl Vendor) Sent: Fri 9/14/2007 11:18 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Devenv /setup does half of the work At the end of our installation, an deferred custom action is invoked to register our VSTS package as well as the CTC menu: InstallExecuteSequence Custom Action=CA_DevenvSetup2005 Before=InstallFinalize / ... /InstallExecuteSequence CustomAction Id=CA_DevenvSetup2005 Property=DEVENV_EXE_2005 ExeCommand=/setup Execute=deferred Return=check Impersonate=no / The installation succeeds and our package is registered to Visual Studio (custom action return value is 1). The problem is that the context menu doesn’t shown in the VSTS project supported by our package just intalled. Manually running “devenv /setup” solves the problem. Something strange is that “devenv /setup” actually does everything other than the context menu registration --- all the other functionalities provided by our package works well in VS. Does anyone have this problem before? Thanks, Xin Liu Alias: v-liux Group: Protocol Tools Test Team Occupation: Build Engineer Seat: No. 2186 Sigma Plaza, Beijing From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Christopher Painter Sent: Friday, September 07, 2007 11:53 PM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Using WiX v3 Votive to build WiX v2 projects This is why I've been asking Justin about using votive v3 to build wix v2 projects. It's a hybrid solution but it seems to work.The risk is minimal since the points that could fail are at build time, not install time. PS- IS is pretty easy to build with TFS once you learn how it works. I have dozens of installers that I use TFS to build with nothing but .NET 2.0, TeamBuild and IS StandAloneBuild installed.You just have to understand how to map product configurations / releases to your solution config. If you would like, I can send you a sample project. http://blog.deploymentengineering.com/2007/05/tip-parallel-is122008-builds-using-tfs.html [EMAIL PROTECTED] wrote: Had a look at the files and I've finally got my head round this. As i understand it WiX v2 .wixproj files, which are used for VS integration, aren't MSBuild files. You have to create your own .wproj files for that. Which means that WiX v2 isn't compatible withTeam Build (as it tries to build the .wixproj file). It'd be really cool if v2 did support Team Build and it's solution centric build process. Without it we can't really consider using WiX v2 or v3 (as it's not stable yet). Which leads me to my next question, is there a rough time line for the switch to v3? Oh and in case it makes you feel better Justin I've been messing around with IS for two days and 2 hotfixes later i still can't get it to build with MS or Team! :-) Matt Matt
Re: [WiX-users] Customizing the dialog sequnce with Floating Publish events
The docs I'm talking about are part of the v3 (Version 3.0.2925.0) install, kind of bleeding edge, if you can call 4 months old bleeding edge :). If you look in the chm it's in WiX Help-Authoring-Using the WixUI dialog library, if you look at the source it's in src/chm/html/ WixUI_dialog_library.html. That page seems to imply that (in v3) you can affect dialog sequence without having to make your own wixlib. I've also seen brief mentions of this functionality on the list, but nothing concrete. -Ian From: János Brezniczky [mailto:[EMAIL PROTECTED] Sent: Friday, September 14, 2007 1:57 AM To: Ian Sullivan Cc: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Customizing the dialog sequnce with Floating Publish events Hi, What documentation do you mention? I couldn't manage to find the Publish.Dialog attribute, but I would also be interested in this method of overriding the default event linking between dialogs. (Thanks for a link if appropriate.) Otherwise I suppose these Publish nodes should be parented by the control which should fire the event, which is not the dialog, but a button in these cases. I thought it forces me to the check the source code of the (wixui) lib, and sometimes import/recompile them to be able to change their behaviour except for the final dialogs (error, success, etc..) or if they take their Value argument from a property. This latter exception (quotes mean it is a frequent one) is illustrated here http://www.tramontana.co.hu/wix/lesson2.php#2.3 I hope I wasn't wrong, and would appreciate other ideas/thoughts on the subject.. 2007/9/14, Ian Sullivan [EMAIL PROTECTED]mailto:[EMAIL PROTECTED]: HI, I'm trying to see if I can insert a dialog into the WixUI_InstallDir sequence, the docs say you can do Publish Dialog=WelcomeDlg Control=Next Event=NewDialog Value=SpecialDlg1/Publish Publish Dialog=SpecialDlg Control=Back Event=NewDialog Value=WelcomeDlg1/Publish Publish Dialog=SpecialDlg Control=Next Event=NewDialog Value=LicenseAgreementDlg1/Publish Publish Dialog=LicenseAgreementDlg Control=Back Event=NewDialog Value=SpecialDlg1/Publish Publish Dialog=LicenseAgreementDlg Control=Next Event=NewDialog Value=InstallDirDlgLicenseAccepted = 1/Publish But aren't really clear about where that should happen. I tried doing this, but I never see my dialog... Property Id =WIXUI_INSTALLDIR Value =INSTALLDIR / UIRef Id =WixUI_InstallDir / UI Dialog Id =SpecialDlg Width =370 Height=270 Control Id =Special_Txt Type =Text X=5 Y=20 Width= 60 Height=18 TabSkip=no Text[DialogFont]Hi there! /Text /Control Control Id =Next Type =PushButton X=236 Y=243 Width= 56 Height=17 Default=yes Text =!(loc.WixUINext) / Control Id =Back Type =PushButton X=180 Y=243 Width= 56 Height=17 Disabled=yes Text =!(loc.WixUIBack) / /Dialog Publish Dialog =WelcomeDlg Control =Next Event=NewDialog Value=SpecialDlg Order =11/Publish Publish Dialog =SpecialDlg Control =Back Event=NewDialog Value=WelcomeDlg Order =11/Publish Publish Dialog =SpecialDlg Control =Next Event=NewDialog Value=LicenseAgreementDlg Order =11/Publish Publish Dialog =LicenseAgreementDlg Control =Back Event=NewDialog Value=SpecialDlg Order=11/Publish /UI Thanks, -Ian Ian Sullivan Software Development Engineer Microsoft Inc., Windows Live Agents: SDK, Tools, Web Services - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.netmailto:WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Customizing the dialog sequnce with Floating Publish events
HI, I'm trying to see if I can insert a dialog into the WixUI_InstallDir sequence, the docs say you can do Publish Dialog=WelcomeDlg Control=Next Event=NewDialog Value=SpecialDlg1/Publish Publish Dialog=SpecialDlg Control=Back Event=NewDialog Value=WelcomeDlg1/Publish Publish Dialog=SpecialDlg Control=Next Event=NewDialog Value=LicenseAgreementDlg1/Publish Publish Dialog=LicenseAgreementDlg Control=Back Event=NewDialog Value=SpecialDlg1/Publish Publish Dialog=LicenseAgreementDlg Control=Next Event=NewDialog Value=InstallDirDlgLicenseAccepted = 1/Publish But aren't really clear about where that should happen. I tried doing this, but I never see my dialog... Property Id=WIXUI_INSTALLDIR Value=INSTALLDIR / UIRef Id=WixUI_InstallDir / UI Dialog Id=SpecialDlg Width=370 Height=270 Control Id=Special_Txt Type=Text X=5 Y=20 Width=60 Height=18 TabSkip=no Text[DialogFont]Hi there!/Text /Control Control Id=Next Type=PushButton X=236 Y=243 Width=56 Height=17 Default=yes Text=!(loc.WixUINext) / Control Id=Back Type=PushButton X=180 Y=243 Width=56 Height=17 Disabled=yes Text=!(loc.WixUIBack) / /Dialog Publish Dialog=WelcomeDlg Control=Next Event=NewDialog Value=SpecialDlg Order=11/Publish Publish Dialog=SpecialDlg Control=Back Event=NewDialog Value=WelcomeDlg Order=11/Publish Publish Dialog=SpecialDlg Control=Next Event=NewDialog Value=LicenseAgreementDlg Order=11/Publish Publish Dialog=LicenseAgreementDlg Control=Back Event=NewDialog Value=SpecialDlg Order=11/Publish /UI Thanks, -Ian Ian Sullivan Software Development Engineer Microsoft Inc., Windows Live Agents: SDK, Tools, Web Services - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
