Comments on: T4 Toolbox: LINQ to SQL classes generator http://www.olegsych.com/2009/01/t4-toolbox-linq-to-sql-classes-generator/ Interfaces are like alcohol - they are a lot of fun when used in moderation. Sat, 04 Feb 2012 05:32:43 +0000 http://wordpress.org/?v=2.3.3 By: Paul http://www.olegsych.com/2009/01/t4-toolbox-linq-to-sql-classes-generator/#comment-3369 Paul Wed, 02 Mar 2011 12:04:01 +0000 http://www.olegsych.com/2009/01/t4-toolbox-linq-to-sql-classes-generator/#comment-3369 I tried the NorthwindSolution but when I exceute the Northwind.tt-file I get an error: LinqToSqlDataContextTemplate.tt line 1 Column 1, here the File: The LinqToSqlDataContextTemplate.tt is: /// mappingSource as a parameter, this generator simply calls the matching base /// constructor. /// /// Hwat I deed wrong? I tried the NorthwindSolution but when I exceute the Northwind.tt-file I get an error:
LinqToSqlDataContextTemplate.tt line 1 Column 1, here the File:
The LinqToSqlDataContextTemplate.tt is:
/// mappingSource as a parameter, this generator simply calls the matching base
/// constructor.
///
///
Hwat I deed wrong?

]]> By: Tim Overbay http://www.olegsych.com/2009/01/t4-toolbox-linq-to-sql-classes-generator/#comment-3140 Tim Overbay Fri, 04 Jun 2010 20:02:18 +0000 http://www.olegsych.com/2009/01/t4-toolbox-linq-to-sql-classes-generator/#comment-3140 Apparently, MS programmers don't use StyleCop, either. The field names for the property backers of the new "auto-implemented properties" in VS 2010 use underscores. Apparently, MS programmers don’t use StyleCop, either. The field names for the property backers of the new “auto-implemented properties” in VS 2010 use underscores.

]]> By: Tim Overbay http://www.olegsych.com/2009/01/t4-toolbox-linq-to-sql-classes-generator/#comment-3139 Tim Overbay Fri, 04 Jun 2010 19:59:27 +0000 http://www.olegsych.com/2009/01/t4-toolbox-linq-to-sql-classes-generator/#comment-3139 This seems like a very interesting tool, but the lack of code generation for sprocs and removing the underscores from the property backers concerns me. Why all the rigmarole with changing the property backers to camelCase without the leading underscore? Being a long-time VB programmer, I like the property name with an underscore as the name of the private field. While this isn't really a show-stopper with VB anymore, it's still much more readable and avoids problems like the one Vadim described above. You mentioned the reason behind this change is to comply with StyleCop. Why is this even a rule in StyleCop? I don't use StyleCop, but it seems like a ridiculous rule tailored for C# code. This seems like a very interesting tool, but the lack of code generation for sprocs and removing the underscores from the property backers concerns me.

Why all the rigmarole with changing the property backers to camelCase without the leading underscore?

Being a long-time VB programmer, I like the property name with an underscore as the name of the private field. While this isn’t really a show-stopper with VB anymore, it’s still much more readable and avoids problems like the one Vadim described above.

You mentioned the reason behind this change is to comply with StyleCop. Why is this even a rule in StyleCop? I don’t use StyleCop, but it seems like a ridiculous rule tailored for C# code.

]]> By: Tae-Sung Shin http://www.olegsych.com/2009/01/t4-toolbox-linq-to-sql-classes-generator/#comment-3012 Tae-Sung Shin Sat, 24 Apr 2010 22:06:23 +0000 http://www.olegsych.com/2009/01/t4-toolbox-linq-to-sql-classes-generator/#comment-3012 Oleg I had the same error messages as Rasheed when I ran your demo. After some digging, I found following single line solved the problem. I am sure you bloged about this but the line is missing in your sample code. Anyway, great blog! Learned a lot. Oleg

I had the same error messages as Rasheed when I ran your demo. After some digging, I found following single line solved the problem.

I am sure you bloged about this but the line is missing in your sample code.

Anyway, great blog! Learned a lot.

]]> By: Oleg Sych http://www.olegsych.com/2009/01/t4-toolbox-linq-to-sql-classes-generator/#comment-2903 Oleg Sych Thu, 18 Feb 2010 17:41:52 +0000 http://www.olegsych.com/2009/01/t4-toolbox-linq-to-sql-classes-generator/#comment-2903 Jacobus, In the LINQ to SQL designer, you can specify different names for the class and for the table it is mapped to. This can be done using the Properties window. Oleg Jacobus,

In the LINQ to SQL designer, you can specify different names for the class and for the table it is mapped to. This can be done using the Properties window.

Oleg

]]> By: Jacobus http://www.olegsych.com/2009/01/t4-toolbox-linq-to-sql-classes-generator/#comment-2893 Jacobus Thu, 04 Feb 2010 23:52:46 +0000 http://www.olegsych.com/2009/01/t4-toolbox-linq-to-sql-classes-generator/#comment-2893 How can I change the code generation to change the names of generated classes? Like getting rid of prefixes etc. Thanks How can I change the code generation to change the names of generated classes? Like getting rid of prefixes etc.
Thanks

]]> By: Oleg Sych http://www.olegsych.com/2009/01/t4-toolbox-linq-to-sql-classes-generator/#comment-2396 Oleg Sych Tue, 27 Oct 2009 22:47:27 +0000 http://www.olegsych.com/2009/01/t4-toolbox-linq-to-sql-classes-generator/#comment-2396 Erik, could you be more specific? Erik, could you be more specific?

]]> By: Erik http://www.olegsych.com/2009/01/t4-toolbox-linq-to-sql-classes-generator/#comment-2395 Erik Tue, 27 Oct 2009 20:49:47 +0000 http://www.olegsych.com/2009/01/t4-toolbox-linq-to-sql-classes-generator/#comment-2395 Did Rasheed ever find a solution to his problem? I'm getting the same issue. Did Rasheed ever find a solution to his problem? I’m getting the same issue.

]]> By: Oleg Sych http://www.olegsych.com/2009/01/t4-toolbox-linq-to-sql-classes-generator/#comment-2313 Oleg Sych Tue, 06 Oct 2009 21:29:00 +0000 http://www.olegsych.com/2009/01/t4-toolbox-linq-to-sql-classes-generator/#comment-2313 Wouter, It would be great if LINQ to SQL designer could support additional attributes. Unfortunately, I don't think it does. It may be possible to hack the DBML in XML editor, but at that point, you would be better off writing this logic by hand in partial classes. Oleg Wouter,

It would be great if LINQ to SQL designer could support additional attributes. Unfortunately, I don’t think it does. It may be possible to hack the DBML in XML editor, but at that point, you would be better off writing this logic by hand in partial classes.

Oleg

]]> By: Wouter http://www.olegsych.com/2009/01/t4-toolbox-linq-to-sql-classes-generator/#comment-2312 Wouter Tue, 06 Oct 2009 13:33:57 +0000 http://www.olegsych.com/2009/01/t4-toolbox-linq-to-sql-classes-generator/#comment-2312 Thanks Oleg for this thorough explanation. So by changing the tt file(s) I can change what code is generated based on the dbml. But I am wondering: is it also possible to extend the dbml file itself, so that I can add extra properties to the columns present in the tables? (By properties I mean those in the "Properties Window" of Visual Studio.) I would like to use these extra properties in the code generation. As a simple example: Wuold it be possible to add a "DefaultValue" property that I can set on each column and use this to add a DefaultValueAttribute to each generated property (in addition to the currently added ColumnAttribute)? Thanks Oleg for this thorough explanation. So by changing the tt file(s) I can change what code is generated based on the dbml.
But I am wondering: is it also possible to extend the dbml file itself, so that I can add extra properties to the columns present in the tables? (By properties I mean those in the “Properties Window” of Visual Studio.) I would like to use these extra properties in the code generation.
As a simple example: Wuold it be possible to add a “DefaultValue” property that I can set on each column and use this to add a DefaultValueAttribute to each generated property (in addition to the currently added ColumnAttribute)?

]]>