{"id":493,"date":"2010-09-16T23:25:19","date_gmt":"2010-09-16T23:25:19","guid":{"rendered":"https:\/\/blogs.msdn.microsoft.com\/heaths\/2010\/09\/16\/restart-manager-functionality-in-wix-3-5\/"},"modified":"2024-07-03T12:10:35","modified_gmt":"2024-07-03T20:10:35","slug":"restart-manager-functionality-in-wix-3-5","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/setup\/restart-manager-functionality-in-wix-3-5\/","title":{"rendered":"Restart Manager functionality in WiX 3.5"},"content":{"rendered":"

WiX 3.5 provides features to integrate with Visual Studio 2005, 2008, and 2010. But like many add-ins, since new files are being added they certainly can\u2019t be in use by devenv.exe. So when we call devenv.exe \/setup as part of our install, the changes may not show up in running instances of Visual Studio.<\/p>\n

To provide a better experience \u2013 and because this seems to be a fairly common request \u2013 I\u2019ve added a custom action in WiX 3.5\u2019s WixUtilExtension to use the Restart Manager<\/a> in Vista and newer. The Restart Manager is capable of shutting down applications \u2013 similar to the normal files-in-use functionality in Windows Installer<\/a> \u2013 but is also capable of restarting some of those applications. Visual Studio is not, unfortunately, one of those programs. But because Restart Manager provides APIs to add resources like file paths to devenv.exe, we can tell Windows Installer to detect and prompt that Visual Studio needs to be closed. Contrast this with detecting that Visual Studio is running and raising an error dialog. After you close Visual Studio, then you have to restart setup.<\/p>\n

To use this functionality yourself \u2013 even if you target Windows XP, for example \u2013 you can author the RestartResource<\/code> element similar to the example below.<\/p>\n

<<\/font><\/font><\/span>PropertyRef<\/font><\/span> <\/font><\/span>Id<\/font><\/span>=<\/font><\/span>"VS2010DEVENV<\/font><\/span>"<\/font><\/font> \/><\/span>
<<\/span><\/font>DirectoryRef<\/font><\/span> <\/font><\/span>Id<\/font><\/span>=<\/font><\/span>"BinDir<\/font><\/span>"<\/font>><\/span>
    <<\/span><\/font>Component<\/font><\/span> <\/font><\/span>Id<\/font><\/span>=<\/font><\/span>"VisualStudioPackage2010<\/font><\/span>" <\/font><\/span>Guid<\/font><\/span>=<\/font><\/span>"C8D37529-F79E-46B4-89FD-EA7BC6654770<\/font><\/span>" <\/font><\/span>Win64<\/font><\/span>=<\/font><\/span>"no<\/font><\/span>"<\/font>><\/span>
        <<\/span><\/font>File<\/font><\/span> <\/font><\/span>Source<\/font><\/span>=<\/font><\/span>"votive2010.dll<\/font><\/span>" <\/font><\/span>KeyPath<\/font><\/span>=<\/font><\/span>"yes<\/font><\/span>" <\/font><\/span>Checksum<\/font><\/span>=<\/font><\/span>"yes<\/font><\/span>" <\/font><\/span>Vital<\/font><\/span>=<\/font><\/span>"yes<\/font><\/span>"<\/font> \/><\/span>
        <<\/span><\/font>util:RestartResource<\/font><\/span> <\/font><\/span>Path<\/font><\/span>=<\/font><\/span>"[VS2010DEVENV]<\/font><\/span>"<\/font> \/><\/span>
    <\/<\/span><\/font>Component<\/font><\/span><\/font><\/font>><\/span>
<\/<\/span><\/font>DirectoryRef<\/font><\/span><\/font>><\/font><\/span><\/font><\/pre>\n
Now when you install WiX 3.5 when Visual Studio is running, you should see the following message asking you to shut it down automatically or reboot after installation is complete. Because you are installing new files it will not actually prompt to reboot but you will not be able to use WiX successfully until you restart Visual Studio or start a new instance.<\/p>\n
\"image\"<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"
WiX 3.5 provides features to integrate with Visual Studio 2005, 2008, and 2010. But like many add-ins, since new files are being added they certainly can\u2019t be in use by devenv.exe. So when we call devenv.exe \/setup as part of our install, the changes may not show up in running instances of Visual Studio. To […]<\/p>\n","protected":false},"author":389,"featured_media":3843,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[10,20,44,45,63,64],"class_list":["post-493","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-uncategorized","tag-custom-actions","tag-installation","tag-vista","tag-visual-studio","tag-windows-7","tag-wix"],"acf":[],"blog_post_summary":"
WiX 3.5 provides features to integrate with Visual Studio 2005, 2008, and 2010. But like many add-ins, since new files are being added they certainly can\u2019t be in use by devenv.exe. So when we call devenv.exe \/setup as part of our install, the changes may not show up in running instances of Visual Studio. To […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/setup\/wp-json\/wp\/v2\/posts\/493","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/setup\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/setup\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/setup\/wp-json\/wp\/v2\/users\/389"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/setup\/wp-json\/wp\/v2\/comments?post=493"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/setup\/wp-json\/wp\/v2\/posts\/493\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/setup\/wp-json\/wp\/v2\/media\/3843"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/setup\/wp-json\/wp\/v2\/media?parent=493"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/setup\/wp-json\/wp\/v2\/categories?post=493"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/setup\/wp-json\/wp\/v2\/tags?post=493"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}