Is LINQ to SQL and Dotnetnuke a good choice, or should we stick to level 3 architecture?

Question

Project scenario

Technology: Dotnetnuke (about 100 - 150 screens)

Data Architecture: LINQ to SQL Selected Using Codesmith PLINQO

The modules are configured, so great if it does not work with Oracle or MySQL as a backend

So the question is:

Due to choosing LINQ to SQL instead of a 3-tier provider model, will this create any problem?

Is it recommended to use a site with dynamic data in this case?

Answer 1

We used Linq for SQL for the n-level system, and it was magical, a little learning curve, but the pain was worth the win.

Entity Framework,, Linq to SQL EF. . Linq to SQL - , .

EF , .

, ,