One more question. Is the following a known item? I don't have any compile errors but at run-time I get alot of the following at
if ((_settings == null)) { _settings = CreateObjectSet<Setting>(); }
The relationship 'NopSolutions.NopCommerce.BusinessLogic.Data.FK_Nop_TierPrice_Nop_ProductVariant' was not loaded because the type 'NopSolutions.NopCommerce.BusinessLogic.Data.ProductVariant' is not available. The following information may be useful in resolving the previous error: The required property 'RequiresTextOption' does not exist on the type 'NopSolutions.NopCommerce.BusinessLogic.Products.ProductVariant'.
The designer should not be empty. The only thing you need to ensure is to right click the edmx in solution explorer > properties > and make sure custom tool is blank.
If you follow the concepts of the article you should not have any problems extending one of the existing entities. I had a quick look at your post and you mentioned 1.4. Just to clarify this applies to 1.7 onwards (using entity framework). As aGorilla commented on your post, if you are extending an existing class (i.e. adding new fields to the table) then you need to make sure your class name is the same, is partial and is in the same namespace. Also you should update the existing insert/update methods to take in the extra parameters (again covered in my article).
If you are adding a new entity you can take a more domain driven approach and just pass in the object itself (we will be using this approach in 1.9).
Ben
Ben, thank you for your time, i will be very great full if you could help me with the code as i am new in asp.net technology.
The article covers the core concepts of extending the nopCommerce model. If you are having difficulty understanding these concepts and are new to asp.net in general, I would recommend getting an overall understanding of the asp.net platform before jumping into an app like nopCommerce.