Question

My project went through a name change, which led to using ReSharper to change the name of namespaces throughout the solution. Everything compiles just fine, but my ASP.NET MVC views are no longer seeing any inherited classes. I’ve changed the namespace imports in web.config and everything, and I’m certain that the classes exist. They work if I refer to the fully-qualified class name (Name.Space.ClassName).

Why is this happening and how can I fix it?

EDIT: More detail:

Before refactoring, I had custom view page, master page, and user control classes:

SalesWeb.Mvc.Views.SalesWebViewPage
SalesWeb.Mvc.Views.SalesWebMasterPage
SalesWeb.Mvc.Views.SalesWebUserControl

After refactoring:

Wasabi.SalesPortal.Mvc.Views.SalesPortalViewPage
Wasabi.SalesPortal.Mvc.Views.SalesPortalMasterPage
Wasabi.SalesPortal.Mvc.Views.SalesPortalUserControl

In web.config, before refactoring:

<configuration>     <system.web>         ...         <pages ...>             ...             <namespaces>                 ...                 <add namespace='SalesWeb.Mvc.Views' />             </namespaces>         </pages>     </system.web> </configuration> 

After:

<configuration>     <system.web>         ...         <pages ...>             ...             <namespaces>                 ...                 <add namespace='Wasabi.SalesPortal.Mvc.Views' />             </namespaces>         </pages>     </system.web> </configuration> 

I’ve also changed the Inherits attribute on each of my views, master pages, and user controls. However, when attempting to visit the MVC application, it complains that SalesPortalMasterPage cannot be found, although I’m absolutely certain that it exists because I don’t have any problems when referring to it as Wasabi.SalesPortal.Mvc.Views.SalesPortalMasterPage.

Answer 1

Try cleaning your bin directory and do a rebuild. Sometimes an older dll lingers in the bin folder and mess up your references/namespacing.