Question

I’ve been asked to design a solution to integrate several ASP.NET applications, some of them are big, where integrations means:

• Share layout and css
• Common header, footer and menu
• Share only one login area

I discard joining applications under one solution as they are big and in the future there may be more applications so I’m thinking of defining a MasterPage or Custom Control that will be included in EVERY page of every application.

This MasterPage or Custom Control will define the common parts and control the access security.

What do you think of this solution? Other (better) possibilities? What’s better, MasterPage or Custom Control?

Thank you

Answer 1

Master Pages are generally used to:

1. reduce duplication of code
2. reduce duplication of script and css includes
3. provide a common layout to all pages that reference it
4. provide a central location to perform logic

You can put a custom control on a master page as well, but for what you want to do a master page is the perfect/only good solution.

To share a single login area you can create a page (Login.aspx) that doesn’t use a master page. Once the user logs in, redirect them to the appropriate page.

To control access the recommended approach is to use forms authentication and the membership provider interface. The role membership provider will allow you to restrict specific pages and code paths to specific groups (roles) of users.