<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://weblogs.asp.net/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Fixing Vista's Default Web Development Settings</title><link>http://weblogs.asp.net/toddanglin/archive/2008/03/12/fixing-vista-s-default-web-development-settings.aspx</link><description>File this under &amp;quot;used to be easy with XP&amp;quot; tips and tricks for Vista. As a long time web developer on XP (all the way back to &amp;quot;classic&amp;quot; ASP), I feel I am pretty comfortable around IIS. I've successfully configured many a development</description><dc:language>en</dc:language><generator>CommunityServer 2007 SP1 (Build: 20510.895)</generator><item><title>re: Fixing Vista's Default Web Development Settings</title><link>http://weblogs.asp.net/toddanglin/archive/2008/03/12/fixing-vista-s-default-web-development-settings.aspx#6239984</link><pubDate>Sun, 01 Jun 2008 19:26:50 GMT</pubDate><guid isPermaLink="false">c06e2b9d-981a-45b4-a55f-ab0d8bbfdc1c:6239984</guid><dc:creator>mehfuzh</dc:creator><author>mehfuzh</author><description>&lt;p&gt;I wonder why Asp.net is not enabled by default. I think it is a matter to consider :-)&lt;/p&gt;
&lt;img src="http://weblogs.asp.net/aggbug.aspx?PostID=6239984" width="1" height="1"&gt;</description></item><item><title>re: Fixing Vista's Default Web Development Settings</title><link>http://weblogs.asp.net/toddanglin/archive/2008/03/12/fixing-vista-s-default-web-development-settings.aspx#6213327</link><pubDate>Fri, 23 May 2008 09:55:51 GMT</pubDate><guid isPermaLink="false">c06e2b9d-981a-45b4-a55f-ab0d8bbfdc1c:6213327</guid><dc:creator>Rob</dc:creator><author>Rob</author><description>&lt;p&gt;It&amp;#39;s worth mentioning (as a timesaver!) that you can get to &amp;quot;Windows Features&amp;quot; more quickly by hitting the start menu and typing &amp;quot;optionalfeatures&amp;quot; (without the quotes) as this is the name of the EXE that runs. Anything to shave a bit of time off that thing loading! :)&lt;/p&gt;
&lt;p&gt;On the &amp;quot;off by default&amp;quot;, surely anything that minimises the attack surface is a good thing? Are you *sure* you hadn&amp;#39;t switched on Classic ASP yourself as it&amp;#39;s off by default, see: &lt;a rel="nofollow" target="_new" href="http://blogs.iis.net/bills/archive/2007/05/21/tips-for-classic-asp-developers-on-iis7.aspx"&gt;blogs.iis.net/.../tips-for-classic-asp-developers-on-iis7.aspx&lt;/a&gt;&lt;/p&gt;
&lt;img src="http://weblogs.asp.net/aggbug.aspx?PostID=6213327" width="1" height="1"&gt;</description></item><item><title>re: Fixing Vista's Default Web Development Settings</title><link>http://weblogs.asp.net/toddanglin/archive/2008/03/12/fixing-vista-s-default-web-development-settings.aspx#5971956</link><pubDate>Sat, 15 Mar 2008 04:08:12 GMT</pubDate><guid isPermaLink="false">c06e2b9d-981a-45b4-a55f-ab0d8bbfdc1c:5971956</guid><dc:creator>Bill Staples</dc:creator><author>Bill Staples</author><description>&lt;p&gt;Actually, IIS7 installs only a static-file web server by default. &amp;nbsp;This is to provide a minimal web server that is secure by default and easy to customize for your particular needs. &amp;nbsp;Classic ASP is not installed by default, but since you upgraded from XP, IIS preserved your settings and left ASP installed. &amp;nbsp;It sounds like for your particular box, ASP.NET was not upgraded, however, which would be a bug. &amp;nbsp;ASP.NET should have been enabled as well, assuming you had it installed on XP before the upgrade.&lt;/p&gt;
&lt;img src="http://weblogs.asp.net/aggbug.aspx?PostID=5971956" width="1" height="1"&gt;</description></item><item><title>re: Fixing Vista's Default Web Development Settings</title><link>http://weblogs.asp.net/toddanglin/archive/2008/03/12/fixing-vista-s-default-web-development-settings.aspx#5966123</link><pubDate>Fri, 14 Mar 2008 08:45:02 GMT</pubDate><guid isPermaLink="false">c06e2b9d-981a-45b4-a55f-ab0d8bbfdc1c:5966123</guid><dc:creator>ca8msm</dc:creator><author>ca8msm</author><description>&lt;p&gt;&amp;quot;It just looks different in Vista with IIS7.&amp;quot;&lt;/p&gt;
&lt;p&gt;Yes, that's definitely true as the process you've clearly described above is a lot different to how you enabled it in win2k3.&lt;/p&gt;
&lt;img src="http://weblogs.asp.net/aggbug.aspx?PostID=5966123" width="1" height="1"&gt;</description></item><item><title>re: Fixing Vista's Default Web Development Settings</title><link>http://weblogs.asp.net/toddanglin/archive/2008/03/12/fixing-vista-s-default-web-development-settings.aspx#5961136</link><pubDate>Thu, 13 Mar 2008 17:30:47 GMT</pubDate><guid isPermaLink="false">c06e2b9d-981a-45b4-a55f-ab0d8bbfdc1c:5961136</guid><dc:creator>tanglin05</dc:creator><author>tanglin05</author><description>&lt;p&gt;@ca8msm- That's true and a good point. I've admittedly done most of my dev work over the years on WinXP or well configured Win 2k3 boxes (as in, I didn't run in to the problem on Win2k3), but it is fair to note this is not a totally new problem. It just looks different in Vista with IIS7.&lt;/p&gt;
&lt;p&gt;That said, I still think it is silly to disable ASP.NET dev features on a consumer OS when all other dev features are enabled by default. I suppose this quirk just reveals how Win2k3-based Vista really is.&lt;/p&gt;
&lt;p&gt;-Todd&lt;/p&gt;
&lt;img src="http://weblogs.asp.net/aggbug.aspx?PostID=5961136" width="1" height="1"&gt;</description></item><item><title>re: Fixing Vista's Default Web Development Settings</title><link>http://weblogs.asp.net/toddanglin/archive/2008/03/12/fixing-vista-s-default-web-development-settings.aspx#5960328</link><pubDate>Thu, 13 Mar 2008 10:12:06 GMT</pubDate><guid isPermaLink="false">c06e2b9d-981a-45b4-a55f-ab0d8bbfdc1c:5960328</guid><dc:creator>ca8msm</dc:creator><author>ca8msm</author><description>&lt;p&gt;This isn't just new to Vista. ASP.NET support was also disabled by default in Windows Server 2003 so it's something that has been around for a while.&lt;/p&gt;
&lt;img src="http://weblogs.asp.net/aggbug.aspx?PostID=5960328" width="1" height="1"&gt;</description></item></channel></rss>