Skip to main content

70-562 Dynamic Data

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.

Comments

Post a Comment

Popular posts from this blog

Rxjs Forkjoin vs Zip

These Rxjs combination operators are handy to make Rest calls in parallel and combine their results. Both take n observables and will return the results, with the difference that forkJoin will complete even if one of the nested observables errors of completes.
Post a Comment
Read more

React JS Patterns

React JS is always evolving, and evolving quickly. These evolutions can be very significant ones, for example, the addition of hooks. React has a lot of code patterns, often these patterns are motivated by the DRY and/or the open-close principle. These patterns sometimes come in to replace a previous one, yet the previous ones still stays in use, as a consequence, the list of patterns keep growing. The goal of the next few posts will be to list the patterns commonly used in React JS developpement. Some patterns are more specific to JSX and I will start with these, and maybe add patterns specific to Redux.
4 comments
Read more

Javascript: Closure and Lexical Scope

The two are separate topics, I just happen to put them in the same post for now. Closure Closure is the capability to remember it's lexical scope, even when executed outside it's lexical scope. If two inner functions, are within the same scope, they share the same closure.     Lexical scope The lexical scope is the scope in which a variable is declared during the first pass of the javascript compilation, which has two passes, compilation and execution. During the compilation pass, the compiler goes through the code looking for formal declaration, that is, var, function and parameters of function. For each of these formal declarations, the compiler will check the current lexical scope, and add this identifier if it isn't already there. Then at the second pass, execution, the compiler will run the code as we are intuitively use to and once it reaches the the identifiers found earlier, will ask if they are left hand side(RHS), or right hand side (LHS). If th...
Post a Comment
Read more