If I should or not use Dynamic Data in my applications?

Whats the maximum size?

Or should I just use it with prototype applications?

Dom Márcio:

If I should or not use Dynamic Data in my applications?

Whats the maximum size?

Or should I just use it with prototype applications?

From what I've seen Dom,

1. I would definately use it for prototyping apps (Data Access) and then I'd customize it to suit my needs
2. I think it has the same limitations as any ASP.Net web forms application running on which ever data access layer you choose to run.

sjnaughton:

Dom Márcio:

If I should or not use Dynamic Data in my applications?

Whats the maximum size?

Or should I just use it with prototype applications?

From what I've seen Dom,

1. I would definately use it for prototyping apps (Data Access) and then I'd customize it to suit my needs
2. I think it has the same limitations as any ASP.Net web forms application running on which ever data access layer you choose to run.

 Thanks partner.

 So, 1: You would use it not just for prototype apps, but for production apps too?
 

Yes I don't see why not, the FieldTemplates used buy the DynmaicControl & DynamicField are worth using in production alone for their ability to reduce the amount of code you have to write. Just follow through some of the demo's and you'll be converted yourself.

See some video tutorials here

Dynamic Data is a good technology for doing Rapid Applicaton Development which can be used for prototying initially. It has powerful data annotations attrbutes and validation mechanism which makes it a good candidate for making production level applications.

What is the maximum size that you are referring to?

 I'm just trying to find out if there is any risk I am not visualizing while implementing Dynamic Data in production apps.

 Thanks rustd.
 

You have a couple choices here:

1) Because the DataContext (from Linq to SQL) is a partial class you can create a partial classs to extend it and add your business logic there

2) You can also grab our futures release from http://www.codeplex.com/aspnet/Release/ProjectReleases.aspx?ReleaseId=14475 and use the DynamicObjectDataSource which allows you to write Dynamic Data pages using ObjectDataSource behavior which woudl call your business layer which can then use whatever underlying data technology of your choice for the data access layer.

In the next version of Dynamic Data we are going to focus heavily on this type of pattern.

Hi an example of business logic would look like this:

public partial class NorthwindDataContext : System.Data.Linq.DataContext
{
	partial void InsertCustomer(Customer instance)
	{
		var NWDC = new NorthwindDataContext();
		if (NWDC.Customers.SingleOrDefault(c => c.CustomerID == instance.CustomerID) != null)
		{
			throw new ValidationException("Duplicate CustoemrID is not allowed");
		}
		else
		{
			// finally send this to the DB
			this.ExecuteDynamicInsert(instance);
		}
	}
}

Here I have implemented the partial method InsertCustomer for the NorthwindDataContext so what I'm doing is checking that there is not already a customer with the same CustomerID.

You could also look at Scot Guthries Linq to SQL series

Part 6: Retrieving Data Using Stored Procedures
Part 7: Updating our Database using Stored Procedures

if you want to implement some of your business login in T-SQL sprocs.

Hope this helps