<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/wordpress-mu-1.2.3-2.2.1" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: ASP.NET MVC Membership</title>
	<link>http://blogs.teamb.com/craigstuntz/2008/04/29/37813</link>
	<description>News of interest to Delphi, .NET, and InterBase developers</description>
	<pubDate>Sun, 07 Sep 2008 06:29:58 +0000</pubDate>
	<generator>http://wordpress.org/?v=wordpress-mu-1.2.3-2.2.1</generator>

	<item>
		<title>By: Craig Stuntz</title>
		<link>http://blogs.teamb.com/craigstuntz/2008/04/29/37813#comment-3528</link>
		<author>Craig Stuntz</author>
		<pubDate>Mon, 05 May 2008 15:07:34 +0000</pubDate>
		<guid>http://blogs.teamb.com/craigstuntz/2008/04/29/37813#comment-3528</guid>
		<description>Dan,

Right now, neither.  Our project (s) are in very early stages.  So I'm using the development server.  Current thinking is that we'll use IIS 7, though. Regarding your issue report, I agree it should "just work," but I'm not sure that the login URL goes through the routing system at all. The URL comes from your web.config.  You could try editing it there.

Good to hear from you!</description>
		<content:encoded><![CDATA[<p>Dan,</p>
<p>Right now, neither.  Our project (s) are in very early stages.  So I&#8217;m using the development server.  Current thinking is that we&#8217;ll use IIS 7, though. Regarding your issue report, I agree it should "just work," but I&#8217;m not sure that the login URL goes through the routing system at all. The URL comes from your web.config.  You could try editing it there.</p>
<p>Good to hear from you!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dan Miser</title>
		<link>http://blogs.teamb.com/craigstuntz/2008/04/29/37813#comment-3527</link>
		<author>Dan Miser</author>
		<pubDate>Mon, 05 May 2008 14:54:37 +0000</pubDate>
		<guid>http://blogs.teamb.com/craigstuntz/2008/04/29/37813#comment-3527</guid>
		<description>Always good to see a familiar face! :-)

Are you deploying to IIS6 or IIS7? I just added this issue when using this with IIS6:
http://www.codeplex.com/MvcMembership/WorkItem/View.aspx?WorkItemId=740

Take care,
Dan</description>
		<content:encoded><![CDATA[<p>Always good to see a familiar face! <img src='http://blogs.teamb.com/craigstuntz/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
<p>Are you deploying to IIS6 or IIS7? I just added this issue when using this with IIS6:<br />
<a href="http://www.codeplex.com/MvcMembership/WorkItem/View.aspx?WorkItemId=740" rel="nofollow">http://www.codeplex.com/MvcMembership/WorkItem/View.aspx?WorkItemId=740</a></p>
<p>Take care,<br />
Dan</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Craig Stuntz</title>
		<link>http://blogs.teamb.com/craigstuntz/2008/04/29/37813#comment-3510</link>
		<author>Craig Stuntz</author>
		<pubDate>Wed, 30 Apr 2008 12:44:10 +0000</pubDate>
		<guid>http://blogs.teamb.com/craigstuntz/2008/04/29/37813#comment-3510</guid>
		<description>OK, I updated the post to call attention to your discussion of the template fix.</description>
		<content:encoded><![CDATA[<p>OK, I updated the post to call attention to your discussion of the template fix.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Troy Goode</title>
		<link>http://blogs.teamb.com/craigstuntz/2008/04/29/37813#comment-3509</link>
		<author>Troy Goode</author>
		<pubDate>Wed, 30 Apr 2008 05:02:59 +0000</pubDate>
		<guid>http://blogs.teamb.com/craigstuntz/2008/04/29/37813#comment-3509</guid>
		<description>Hi Craig,

Thanks for the write-up! I'm sure this will be useful to many people.

A quick note about step #8: I think it is worth noting that the new release is now available that fixes this template issue. You'll have to be sure to uninstall the templates if you've previously installed them, however, as Visual Studio aggressively caches those suckers.

Even if you are not yet ready to upgrade to the 1.2 release of the starter kit (which uses the interim build of the MVC Framework), the 1.2 VS templates -- and specifically the Administration View templates which contained the bug -- should be safe for use with the 1.1 version of the starter kit.

Please let me know if you encounter any further difficulties with the templates!

Troy</description>
		<content:encoded><![CDATA[<p>Hi Craig,</p>
<p>Thanks for the write-up! I&#8217;m sure this will be useful to many people.</p>
<p>A quick note about step #8: I think it is worth noting that the new release is now available that fixes this template issue. You&#8217;ll have to be sure to uninstall the templates if you&#8217;ve previously installed them, however, as Visual Studio aggressively caches those suckers.</p>
<p>Even if you are not yet ready to upgrade to the 1.2 release of the starter kit (which uses the interim build of the MVC Framework), the 1.2 VS templates &#8212; and specifically the Administration View templates which contained the bug &#8212; should be safe for use with the 1.1 version of the starter kit.</p>
<p>Please let me know if you encounter any further difficulties with the templates!</p>
<p>Troy</p>
]]></content:encoded>
	</item>
</channel>
</rss>
