I have a class called &#39;Article&#39; in a project called &#39;MyProject.Data&#39;, which acts as the data layer for my web application.

I have a separate project called &#39;MyProject.Admin&#39;, which is a web-based admin system for viewing/editing the data, and was build using ASP.NET Dynamic Data.

Basically I want to extend the Article class, using a partial class, so that I can augment one of its properties with a &quot;UIHint&quot; extender, which will allow me to replace the normal multi-line textbox with an FCKEdit control.

My partial class and extender would look like this:

    [MetadataType(typeof(ProjectMetaData))]
    public partial class Project
    {
    }

    public class ProjectMetaData
    {
        [UIHint(&quot;FCKeditor&quot;)]
        public object ItemDetails { get; set; }
    }

Now this all works fine if the partial class is in the same project as the original partial class - i.e. the MyProject.Data project.

But UI behavior shouldn&#39;t sit in the Data layer, but rather, in the Admin layer. So I want to move this class to MyProject.Admin.

However, if I do that, the functionality is lost.

My fundamental question is: can I have 2 partial classes in separate projects, but both referring to the same &quot;class&quot;?

If not, is there a way to accomplish what I&#39;m trying to do, without mixing data-layer logic with UI logic?

All asp.net Dynamic-Data Solutions on Gang of Coders

Total of 1 asp.net Dynamic-Data Solutions

Is it possible to have two partial classes in different assemblies represent the same class?