Al Pascual


Geo RSS
Geo Twitter Timeline

Blogs I read

<August 2008>
SunMonTueWedThuFriSat
272829303112
3456789
10111213141516
17181920212223
24252627282930
31123456

Do not call name a Web form "Login.aspx" on VS2008 with ASP.NET 2.0

In Visual Studio 2005 came out the new framework 2.0, in that one, there was a class called Login that had always problems if you create a page called "Login.aspx" as you partial class was going to be called Login.

Now in VS2008 I was hoping for that issue to be resolved, no luck, still I cannot create a page called Login.aspx without having a conflict when compiling.

Related Links

https://blogs.msdn.com/rahulso/archive/2006/07/03/cs0030-cannot-convert-type-asp-login-aspx-to-system-web-ui-webcontrols-login.aspx

Posted from http://weblogs.asp.net/albertpascual

Posted: Feb 05 2008, 11:06 PM by albert | with 4 comment(s)
Filed under: , ,

Comments

» Daily Bits - February 6, 2008 Alvin Ashcraft’s Daily Geek Bits: Daily links, development, gadgets and raising rugrats. said:

Pingback from  &raquo; Daily Bits - February 6, 2008 Alvin Ashcraft&#8217;s Daily Geek Bits: Daily links, development, gadgets and raising rugrats.

# February 6, 2008 8:29 AM

Speednet said:

Your advice is good if you don't change the class names of your pages and you don't use a namespace.  I always change the page class name, so this is never an issue for me.

For example, if I create a page called "login.aspx", I change the default class name to "LoginPage".

Routinely changing the class name for each page like this is a nice way to avoid any naming conflicts, while maintaining consistency and readability throughout the site.

# February 6, 2008 9:25 AM

Sean said:

I just wrap the page in a namesspace and i don't have any problems

# February 7, 2008 4:16 AM
Leave a Comment

(required) 

(required) 

(optional)

(required) 


Protected by FormShield
Refresh
Listen
Please enter the characters shown on the image


Code: