IIShttp://www.drowningintechnicaldebt.com/ShawnWeisfeld/category/38.aspx
IISen-USShawn WeisfeldSubtext Version 2.1.2.2Cannot open IIS based websites in VS.NET 2008http://www.drowningintechnicaldebt.com/ShawnWeisfeld/archive/2010/04/12/cannot-open-iis-based-websites-in-vs.net-2008.aspx
<p>Problem, when creating a "Web Site" or opening a "Web Site" in VS.NET 2008 using the Local IIS option you get the following message. </p> <p>To Access Local IIS Web Sites, you must install the following IIS components: </p> <p>In addition, you must run Visual Studio in the context of an administrator account. </p> <p>For more information, press F1. </p> <p><a href="http://www.drowningintechnicaldebt.com/images/www_drowningintechnicaldebt_com/ShawnWeisfeld/WindowsLiveWriter/CannotopenIISbasedwebsitesinVS.NET2008_110A4/clip_image003_2.jpg"><img style="border-bottom: 0px; border-left: 0px; display: inline; border-top: 0px; border-right: 0px" title="clip_image003" border="0" alt="clip_image003" src="http://www.drowningintechnicaldebt.com/images/www_drowningintechnicaldebt_com/ShawnWeisfeld/WindowsLiveWriter/CannotopenIISbasedwebsitesinVS.NET2008_110A4/clip_image003_thumb.jpg" width="550" height="434" /></a></p> <p>Fix, start the "IIS Admin Service". To do this open the "Services" control panel. Right click on the service and select start. See image below. Good luck! </p> <p><a href="http://www.drowningintechnicaldebt.com/images/www_drowningintechnicaldebt_com/ShawnWeisfeld/WindowsLiveWriter/CannotopenIISbasedwebsitesinVS.NET2008_110A4/clip_image005_2.jpg"><img style="border-bottom: 0px; border-left: 0px; display: inline; border-top: 0px; border-right: 0px" title="clip_image005" border="0" alt="clip_image005" src="http://www.drowningintechnicaldebt.com/images/www_drowningintechnicaldebt_com/ShawnWeisfeld/WindowsLiveWriter/CannotopenIISbasedwebsitesinVS.NET2008_110A4/clip_image005_thumb.jpg" width="1145" height="225" /></a></p><img src="http://www.drowningintechnicaldebt.com/ShawnWeisfeld/aggbug/700.aspx" width="1" height="1" />Shawn Weisfeldhttp://www.drowningintechnicaldebt.com/ShawnWeisfeld/archive/2010/04/12/cannot-open-iis-based-websites-in-vs.net-2008.aspxTue, 13 Apr 2010 07:26:00 GMThttp://www.drowningintechnicaldebt.com/ShawnWeisfeld/comments/700.aspxhttp://www.drowningintechnicaldebt.com/ShawnWeisfeld/archive/2010/04/12/cannot-open-iis-based-websites-in-vs.net-2008.aspx#feedbackhttp://www.drowningintechnicaldebt.com/ShawnWeisfeld/comments/commentRss/700.aspxhttp://www.drowningintechnicaldebt.com/ShawnWeisfeld/services/trackbacks/700.aspxMicrosoft Web Platform Installerhttp://www.drowningintechnicaldebt.com/ShawnWeisfeld/archive/2008/11/04/microsoft-web-platform-installer.aspx
While I was not able to attend PDC, Microsoft did good by the community and has provided free recordings of many of the sessions (<a href="http://www.microsoftpdc.com/">http://www.microsoftpdc.com</a>). While this is cool and has some great content, the purpose of this blog post is to talk about the Microsoft Web Platform Installer (<a href="http://www.microsoft.com/web/channel/products/WebPlatformInstaller.aspx">http://www.microsoft.com/web/channel/products/WebPlatformInstaller.aspx</a>). This tool allows for single deployment model for all the bits and pieces needed to put together a clean PC image for a developer use (i.e. VS.NET, SQL SVR, and IIS). IMHO this is a great idea and Microsoft is only scratching the surface of what they could do in this space. Currently the tool works for the express editions, which is good for the hobbyist and more importantly at schools. With my experiences teaching .NET at the University anything that helps bring students into a working development environment faster and easier is goodness. However this will become much more valuable when it gets pushed into the enterprise environment. Currently one of the most frustrating jobs that I have my day job is helping team members with the setup of development machines. Anything that MSFT can do to stream line and reduce errors in the process of installing the entire suite of development tools is much appreciated.<img src="http://www.drowningintechnicaldebt.com/ShawnWeisfeld/aggbug/270.aspx" width="1" height="1" />sweisfeldhttp://www.drowningintechnicaldebt.com/ShawnWeisfeld/archive/2008/11/04/microsoft-web-platform-installer.aspxTue, 04 Nov 2008 13:39:00 GMThttp://www.drowningintechnicaldebt.com/ShawnWeisfeld/comments/270.aspxhttp://www.drowningintechnicaldebt.com/ShawnWeisfeld/archive/2008/11/04/microsoft-web-platform-installer.aspx#feedback1http://www.drowningintechnicaldebt.com/ShawnWeisfeld/comments/commentRss/270.aspxhttp://www.drowningintechnicaldebt.com/ShawnWeisfeld/services/trackbacks/270.aspxBe warned aspnet_regiis might change the version of .NET on your Virtual Directories http://www.drowningintechnicaldebt.com/ShawnWeisfeld/archive/2007/02/14/be-warned-aspnet_regiis-might-change-the-version-of-.net-on.aspx
<p class="MsoNormal" style="MARGIN: 0in 0in 0pt"><font face="Times New Roman" size="3">Yesterday we ran aspnet_regiis in an effort to get WCF working on our server (see this KB article for details on that http<a href="http://msdn2.microsoft.com/en-us/library/ms752252.aspx">://msdn2.microsoft.com/en-us/library/ms752252.aspx</a>) and all heck broke loose. Apparently the tool went through the websites and virtual directories on our server and change some of the ones set to .NET 1.1 to .NET 2.0. It was strange that it was only some of the directories and very frustrating to find, but it is fixed now and I thought I would share it with you all.</font></p><img src="http://www.drowningintechnicaldebt.com/ShawnWeisfeld/aggbug/176.aspx" width="1" height="1" />sweisfeldhttp://www.drowningintechnicaldebt.com/ShawnWeisfeld/archive/2007/02/14/be-warned-aspnet_regiis-might-change-the-version-of-.net-on.aspxThu, 15 Feb 2007 03:52:00 GMThttp://www.drowningintechnicaldebt.com/ShawnWeisfeld/comments/176.aspxhttp://www.drowningintechnicaldebt.com/ShawnWeisfeld/archive/2007/02/14/be-warned-aspnet_regiis-might-change-the-version-of-.net-on.aspx#feedbackhttp://www.drowningintechnicaldebt.com/ShawnWeisfeld/comments/commentRss/176.aspxhttp://www.drowningintechnicaldebt.com/ShawnWeisfeld/services/trackbacks/176.aspx