Web Design. Development. Optimization. RSS 2.0
 Tuesday, October 10, 2006

OK, perhaps saying "too easy" in my last post was asking for trouble. Because trouble is what I have.

I have a weird situation and I need some help figuring out what the solution is... Any clues, please email me or leave a comment.

We have a "base page" that inherits from System.UI.Web.Page. My base page is called "BasePage.aspx".

All other web pages of our application inherit from that. So "default.aspx" inherits from BasePage.aspx.

So my problem is that the codebehind page for BasePage, called BasePage.aspx.cs, has been saved in the App_Code folder. Now I don't know this folder or what it's for, thats my first problem.

Now all the pages that inherit BasePage.aspx now fail because the class doesn't exist.

If I move BasePage.aspx.cs out and put it at the root folder, then another page breaks about the BasePage class (one of our User Web Controls).

Ugh. I am sure once I figure the underlying problem out, fixing all pages won't be a problem. This isn't a problem relating to the number of pages, it's a problem every web site would have during a migration with base pages, web controls, etc.

 

Tuesday, October 10, 2006 9:30:55 PM (Eastern Daylight Time, UTC-04:00)  #    Comments [0] -
.NET | The Blogging Life | Visual Studio 2005
Del.icio.us Digg Technorati Blinklist Furl reddit
Comments are closed.
Archive
<August 2008>
SunMonTueWedThuFriSat
272829303112
3456789
10111213141516
17181920212223
24252627282930
31123456
About the author/Disclaimer

Disclaimer
The opinions expressed herein are my own personal opinions and do not represent my employer's view in any way.

© Copyright 2008
Scott Duffy
Sign In
Statistics
Total Posts: 471
This Year: 30
This Month: 2
This Week: 0
Comments: 73
Themes
Pick a theme:
All Content © 2008, Scott Duffy
DasBlog theme 'Business' created by Christoph De Baene (delarou)