Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Shared Master Pages

Status
Not open for further replies.

governmentworker

Programmer
May 5, 2011
3
CA
I am working in asp.net 2005. I have a giant web application that contains all the styles and master pages, plus several web apps. We need to create many more web apps that have the same look and feel. What I want to do is divide the application up into one solution with many projects. One project, the "parent", would contain all of the formatting things (style sheets, masterpages, anything common to all apps) then create many "child" projects that would reference the parent's dll file. That way we don't have to recompile everything every time we make a change. This is going to be very large and needs to be modular.
Here's the problem; every thing I read on the internet says that it's possible, yet I can't find a working solution. I've done this sort of thing for windows apps, but never with a master page. I can reference the classes, but not the masterpage (so far).
When it comes time to reference the Parent master page in the child code, it keeps telling me it can't find the file. I have all of my code, for all of the apps, saved within the same parent directory.
<%@ Page Language="vb" AutoEventWireup="false" CodeBehind="Child2.aspx.vb" Inherits="ASP.masterpagebase_master" MasterPageFile="/1Column.master"%> 1column.master cannot be found....
Any ideas?
 
This forum is for Classic ASP. The ASP.NET forum here: forum855
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top