This isn't exactly what you are after but it might help :
In version 1.9, I've added a new field to the db based on Ben Foster's guide (Adding a new property to an existing entity).
Using Ben's example and following his description:
1. add the new field to the database: nop_Category table (Stylesheet, nvchar(50), allow nulls) using NopModel.edmx update the model based on the database
2. add a new class called Category.cs - simply copy and paste the text per Ben's guide or use this:
namespace NopSolutions.NopCommerce.BusinessLogic.Categories
{
/// <SUMMARY>
/// Represents a category
/// </SUMMARY>
public partial class Category : BaseEntity {
public string Stylesheet { get; set; }
}
}
3. now the variation to Ben's guide: add the new Stylesheet code to the CategoryInfo.ascx.cs in Admin. by adding these lines no's (assuming you are looking at a default install):
59 this.txtStylesheet.Text = category.Stylesheet;
136 category.Stylesheet = txtStylesheet.Text.Trim();
167 Stylesheet = txtStylesheet.Text.Trim(),
This places Stylesheet between the Name and Description in the code.
4. Now if you stick this code into CategoryInfo.ascx (should be on lines 36 to 45):
<tr>
<td class="adminTitle">
<nopCommerce:ToolTipLabel runat="server" ID="ToolTipLabel1" Text="STYLESHEET"
ToolTip="<% $NopResources:Admin.CategoryInfo.Name.ToolTip %>" ToolTipImage="~/Administration/Common/ico-help.gif" />
</td>
<td class="adminData">
<nopCommerce:SimpleTextBox runat="server" CssClass="adminInput" ID="txtStylesheet" ErrorMessage="<% $NopResources:Admin.CategoryInfo.Name.Required %>">
</nopCommerce:SimpleTextBox>
</td>
</tr>
5. Now compile and run you should see Stylesheet as a new field after CategoryName in the Admin/CategoryInfo screen - the tool tip above is a text version but you'd add a resource string normally.
I've not tested this fully yet, but this seems to be working OK so far. It seems the EF in v1.9 nopcom is making extending even easier - unless of course I've missed something!
Adding a new entity, which is what you're after, I am about to attempt, but it may take longer but this should point you in the right direction - with v1.9 not using the manager method it'll take a bit more reading to see how to extend v1.9 correctly.