{"id":5074,"date":"2007-04-23T16:19:00","date_gmt":"2007-04-23T16:19:00","guid":{"rendered":"https:\/\/blogs.msdn.microsoft.com\/webdev\/2007\/04\/23\/downloadable-hotfix-publish-command-fails-when-virtual-path-is-set-to\/"},"modified":"2007-04-23T16:19:00","modified_gmt":"2007-04-23T16:19:00","slug":"downloadable-hotfix-publish-command-fails-when-virtual-path-is-set-to","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/dotnet\/downloadable-hotfix-publish-command-fails-when-virtual-path-is-set-to\/","title":{"rendered":"Downloadable Hotfix: Publish command fails when Virtual Path is set to \/"},"content":{"rendered":"<p><P>One of the&nbsp;convenient new&nbsp;things in&nbsp;Visual Studio 2005 SP1 is the ability to set the built-in ASP.NET Development Server to use&nbsp;&#8220;\/&#8221; as the <EM>Virtual path<\/EM> for when it runs.&nbsp; This is very useful&nbsp;for development of web apps that will eventually be deployed to the root folder of a web server, or for web applications that&nbsp;use <EM>server root relative<\/EM> URLs (e.g. &#8211; &#8220;\/images\/foo.jpg&#8221;).<\/P>\n<P><IMG src=\"https:\/\/devblogs.microsoft.com\/wp-content\/uploads\/sites\/16\/2019\/02\/WebQFE1.png\" border=\"0\"><\/P>\n<P>However, when you set the <EM>Virtual path<\/EM> of the built-in development server to &#8220;\/&#8221; for a Web site, you may encounter an issue with the <EM>Publish Website<\/EM> command not working.&nbsp; This may result in either of the following error messages:<\/P>\n<P><IMG src=\"https:\/\/devblogs.microsoft.com\/wp-content\/uploads\/sites\/16\/2019\/02\/WebQFE3.png\" border=\"0\">&nbsp;<\/P>\n<P><IMG src=\"https:\/\/devblogs.microsoft.com\/wp-content\/uploads\/sites\/16\/2019\/02\/WebQFE2.png\" border=\"0\"><\/P>\n<P>I&#8217;m glad to announce that&nbsp;our team&nbsp;has a <A class=\"\" href=\"https:\/\/connect.microsoft.com\/downloads\/downloaddetails.aspx?DownloadID=6178&amp;wa=wsignin1.0&amp;siteid=210\">hotfix available for download<\/A> that fixes the above described issue.&nbsp; If you are running into this problem after installing Visual Studio 2005 SP1, please download the <A class=\"\" href=\"https:\/\/connect.microsoft.com\/downloads\/downloaddetails.aspx?DownloadID=6178&amp;wa=wsignin1.0&amp;siteid=210\">hotfix<\/A>&nbsp;and that should make&nbsp;the <EM>Publish Website<\/EM> command&nbsp;work as expected.<\/P>\n<P>On a related note, both Visual Studio and the .NET Framework make all high-impact hotfixes available for download at the following website: <A href=\"https:\/\/connect.microsoft.com\/VisualStudio\/Downloads\">https:\/\/connect.microsoft.com\/VisualStudio\/Downloads<\/A>.<\/P>\n<P>Hope this information helps!<\/P>\n<P>Cheers,<\/P>\n<P>Omar Khan<BR>Group Program Manager<BR>Visual Studio Web Tools<\/P>\n<P>&nbsp;<\/P><\/p>\n","protected":false},"excerpt":{"rendered":"<p>One of the&nbsp;convenient new&nbsp;things in&nbsp;Visual Studio 2005 SP1 is the ability to set the built-in ASP.NET Development Server to use&nbsp;&#8220;\/&#8221; as the Virtual path for when it runs.&nbsp; This is very useful&nbsp;for development of web apps that will eventually be deployed to the root folder of a web server, or for web applications that&nbsp;use server [&hellip;]<\/p>\n","protected":false},"author":404,"featured_media":58792,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[197],"tags":[4,7265,31,7262,147,7267,7268,7269],"class_list":["post-5074","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-aspnet","tag-net","tag-announcements","tag-asp-net","tag-development","tag-visual-studio","tag-vwd","tag-web","tag-web-2-0"],"acf":[],"blog_post_summary":"<p>One of the&nbsp;convenient new&nbsp;things in&nbsp;Visual Studio 2005 SP1 is the ability to set the built-in ASP.NET Development Server to use&nbsp;&#8220;\/&#8221; as the Virtual path for when it runs.&nbsp; This is very useful&nbsp;for development of web apps that will eventually be deployed to the root folder of a web server, or for web applications that&nbsp;use server [&hellip;]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/posts\/5074","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/users\/404"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/comments?post=5074"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/posts\/5074\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/media\/58792"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/media?parent=5074"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/categories?post=5074"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/tags?post=5074"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}