Object Relational Mappers, for example Linq and Entity Framework are well integrated in VS 2008, and have project template available; Dynamic Data Web Site.
Creating a dynamic data web site project is a good way to explore the server controls and datasources offered via the toolbox menu.
This template starts out witha basic website shell, but the connection string isnt configured. The Linq to SQL and Entity to SQL are the ORM offered and by default use the default databse located in App_Data folder of this template project.
The designer.cs file defines the data model and wraps the objects around it in order to access the data model via code.
In the global.asax contains the RegisterRoutes method that comes with a default model.RegisterContext method of the type YourDataConectType, you will replace this one with your data context which, after having created the model pointing to your database should be avaialble in intellisence under the name yourDatabaseNameDataContext.
ScaffoldAllTables to true will include all the tables in the model.
At th8is point it's possible to run the website and default.aspx that will show the various tables in your model and page the content of each table when clicking on the table.
If you notice the form of the URL, this can be customized through routing in the global.asax file, using the ASP.Net routing engine.
In this site, there is no code generation, the sturction is based on templates and is dynamic thanks to routing features that reuse the same edit.aspx page for each item.
For example this routing defintion is defuined by routes.Add(new DynamicRoute("{Table}/{actions}.aspx"));
There is a lot to say on ORMs and Dynamic Data layers, the purpose of this section was mostly to summarize some of the VS2008 features that make using Linq and EF faster and customizable.
Creating a dynamic data web site project is a good way to explore the server controls and datasources offered via the toolbox menu.
This template starts out witha basic website shell, but the connection string isnt configured. The Linq to SQL and Entity to SQL are the ORM offered and by default use the default databse located in App_Data folder of this template project.
The designer.cs file defines the data model and wraps the objects around it in order to access the data model via code.
In the global.asax contains the RegisterRoutes method that comes with a default model.RegisterContext method of the type YourDataConectType, you will replace this one with your data context which, after having created the model pointing to your database should be avaialble in intellisence under the name yourDatabaseNameDataContext.
ScaffoldAllTables to true will include all the tables in the model.
At th8is point it's possible to run the website and default.aspx that will show the various tables in your model and page the content of each table when clicking on the table.
If you notice the form of the URL, this can be customized through routing in the global.asax file, using the ASP.Net routing engine.
In this site, there is no code generation, the sturction is based on templates and is dynamic thanks to routing features that reuse the same edit.aspx page for each item.
For example this routing defintion is defuined by routes.Add(new DynamicRoute("{Table}/{actions}.aspx"));
There is a lot to say on ORMs and Dynamic Data layers, the purpose of this section was mostly to summarize some of the VS2008 features that make using Linq and EF faster and customizable.
Comments
Post a Comment