This is what we Wanted, not what I expected, so remember this is a pattern.
If you have written SXL, then you can use Execute feature, the function template Specify the type of "row" class as the argument:
var myList = DataContext.ExecuteQuery & lt; MyRow & gt; ("Select * from myview");
The "row" square exposes the column as a public property, for example:
public class MyRow {public Ent ID (get; set) ;} The public string name {get} set;} ....}
You can do the column to decorate with more information:
Public class MyRow {.... [column (collection = "NameColumn", DbType = "VarChar (50)")] public string name {get; set;} ....}
SQL is very good SQL in my experience The code generates no code, and this code generates breaks for large databases. For SQL, what exactly does the SQL expose your client's stored functionality for example:
Var results = datacontex. Microformor (A, B, C);
This lets you store SQL in the database, while it is easy to use, automatically generated NAT cover.
Used for viewing the exact SQL, you can use the SQL Server Profiler tool:
Linq-to-Sql debug visualizer:
< P>
Or you can write a custom code to log the questions: