Hi All,

I'm going to use ADO.NET Entity Framework for my custom modules development with DNN5.x and VS2008 SP1.

My question is: did anybody here do this kind of development within C# DotNetNuke Compiled Module project?

If Yes - how smoothly it was going?

If Not - what do you think about such a "crossing of DNN and ADO.NET EF"?

The reason to use this "crossing" is to minimize the set of stored procedures usualy used in DNN custom modules.

I expect that:

DataProvider.cs
{Modulename}Controller.cs
{ModuleName}Info.cs
SqlDataProvider.cs

will all get their code heavily cut.

I do not plan to use [Edit{ModuleName}.ascx] control - I do plan to use [View{ModuleName}.ascx] control(s) only.

Does [Settings.ascx] need some custom Stored Procedures - I haven't yet checked - but I guess [Settings.ascx] works using standard DNN stored procedures therefore my [01.00.00.SqlDataProvider] and [Uninstall.SqlDataProvider] will not have any executable T-sql code.

I can also have [Edit{ModuleName}.ascx] as an empty control, and I'd need to localize only [View{ModuleName}.ascx.resx] as end-user viewable controls will be only be displayed in view mode.

I plan to have several View{ModuleName}1.ascx, View{ModuleName}2.ascx, ..., View{ModuleName}N.ascx custom controls per custom module - still an open question here how to parameterize the call to a custom module to pass index/name of its custom to be displayed - do you know hwo to do that?

Do you see any hidden (for me) drawbacks in my plan?

I must note that I'm only starting DNN (custom) development and my above plan can have missed to take into account some important details, which could make this plan absolutely unachievable....

Thank you.

--
Shamil