Home/ Questions/Q 210593
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-11T18:01:09+00:00

I am adding MVC to a project that has MANY legacy webform pages. This

  • 0

I am adding MVC to a project that has MANY legacy webform pages. This works fine. However, I currently have a separate masterpage for MVC and for the webforms. The two master pages produce essentially identical output. I’d really like to kill the webforms one and just use the MVC master page with all my pages and stay DRY.

Not being DRY has already bitten me a couple times when I forgot to change both.

I tried doing the obvious way and just pointing the webform content page’s MasterPage attribute at the MVC masterpage. This throws an error saying the MVC masters only work with MVC views.

This seems like it would be a pretty common problem with mixed MVC and webform projects. My MVC master isn’t doing anything with ViewData, so I don’t see any reason the webforms couldn’t use them.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    You can absolutely share the same master page. Your MVC master page must simply point to the WebForms masterpage via its MasterPageFile attribute. This applies your WebForms MasterPage styles to your MVC MasterPage.

    I am using this setup in production.

    The declaration on my MVC Master Page, pointing at the Web Forms Master Page:

    <%@ Master Language="C#" MasterPageFile="~/MasterPage/Site.Master"
AutoEventWireup="true" Inherits="System.Web.Mvc.ViewMasterPage" %>

    Works like a charm.

    • 0