Last post Apr 09, 2015 04:52 AM by sjnaughton
Mar 14, 2015 10:15 AM|klca|LINK
Knowing that I already know that you can merge an ASP.Net project with a Dynamic Data one, I'd like to know a couple of things clearer:
1) Should I use the Dynamic Data project as the base project and merge into it the 2nd normal ASP.Net project or should it be the other way around)
2) How can I make the Dynamic Data features, such as validation, MetaData usage and so forth available for the non-Dynamic Data pages?
Is there a path or something that can be followed in order to accomplish these tasks?
Carlos N. Porras
Mar 14, 2015 11:03 AM|sjnaughton|LINK
Hi Carlos, I always start with a DD project and then add my plain asp.net pages to that you can configure routing so that the pages look like the they are in the DD structure but it's not required.
Always remember though DD is just plain old Web Forms with some templates and some metadata it's not fundamentally different like MVC is. :D
Mar 15, 2015 09:32 AM|klca|LINK
But how do you do to get #2 (MetaData and validation) to be available on your non-Dynamic Data pages?
Mar 15, 2015 05:09 PM|sjnaughton|LINK
that only works on controls where you SetMetaTable i.e. you have to enable Dynamic Data and that relies on you have entities that have metadata on them that you can use in the SetMetaTable extension method.
Apr 08, 2015 09:16 AM|Sp91|LINK
can i implement jqgrid in place of normal grid in dynamic data site.
Apr 09, 2015 02:08 AM|klca|LINK
Steve is the expert here
In my opinion you can't because of all of the work that is done by the DD behind engine dll's
My guess is that the GridView control is vital part of all of DD and is needed to make the proper functions call
I'm just guessing
Apr 09, 2015 04:52 AM|sjnaughton|LINK
Hi Carlos you are mostly right but you could write an asp.net server control that implemented jqgrid and that would work but it would be a bigish job.