Comments on: LINQ to SQL templates updated, now on CodePlex http://damieng.com/blog/2009/01/19/linq-to-sql-templates-updated-now-on-codeplex?utm_source=rss&utm_medium=rss&utm_campaign=linq-to-sql-templates-updated-now-on-codeplex A .NET developer in silicon valley Fri, 18 May 2012 15:31:00 +0000 hourly 1 http://wordpress.org/?v=3.3.2 By: LINQ to SQL T4 Templates and Nullable Foreign Keys | Matthew Sigman http://damieng.com/blog/2009/01/19/linq-to-sql-templates-updated-now-on-codeplex#comment-46896 LINQ to SQL T4 Templates and Nullable Foreign Keys | Matthew Sigman Wed, 09 Nov 2011 20:14:25 +0000 http://damieng.com/blog/2009/01/19/linq-to-sql-templates-updated-now-on-codeplex#comment-46896 [...] a developer at Microsoft and is one of the people on the original LINQ to SQL team.  He created a T4 Template that works with LINQ to SQL to offer code generation while still taking advantage of the ORM [...] [...] a developer at Microsoft and is one of the people on the original LINQ to SQL team.  He created a T4 Template that works with LINQ to SQL to offer code generation while still taking advantage of the ORM [...]

]]> By: Linq to Sql – How-to Separate the entities and the DataContext. « Daniel Wertheim http://damieng.com/blog/2009/01/19/linq-to-sql-templates-updated-now-on-codeplex#comment-37961 Linq to Sql – How-to Separate the entities and the DataContext. « Daniel Wertheim Sun, 14 Mar 2010 12:42:20 +0000 http://damieng.com/blog/2009/01/19/linq-to-sql-templates-updated-now-on-codeplex#comment-37961 [...] Guard has put together some T4-templates (read more) that could be used to take control of how the DataContext and the entities are generated. All I [...] [...] Guard has put together some T4-templates (read more) that could be used to take control of how the DataContext and the entities are generated. All I [...]

]]> By: KLCA http://damieng.com/blog/2009/01/19/linq-to-sql-templates-updated-now-on-codeplex#comment-36555 KLCA Fri, 19 Feb 2010 17:32:57 +0000 http://damieng.com/blog/2009/01/19/linq-to-sql-templates-updated-now-on-codeplex#comment-36555 Hi, Excuse me sir ... where is the .wmv file? I'm trying to build an MetaData file automatically having as a start point my .dbml LINQ to SQL DataContext File. Carlos Porras (El Salvador) Hi,

Excuse me sir … where is the .wmv file? I’m trying to build an MetaData file automatically having as a start point my .dbml LINQ to SQL DataContext File.

Carlos Porras (El Salvador)

]]> By: Harro Schmidt http://damieng.com/blog/2009/01/19/linq-to-sql-templates-updated-now-on-codeplex#comment-33019 Harro Schmidt Wed, 23 Dec 2009 08:52:09 +0000 http://damieng.com/blog/2009/01/19/linq-to-sql-templates-updated-now-on-codeplex#comment-33019 Hi Damien, When using the built-in generator the namespace of my DataContext is MyCompany.Database (the .dbml is located in the folder 'Database' within the project). But with using the template, the namespace 'Database' is missing. Any ideas? Harro Hi Damien,

When using the built-in generator the namespace of my DataContext is MyCompany.Database (the .dbml is located in the folder ‘Database’ within the project).
But with using the template, the namespace ‘Database’ is missing.
Any ideas?

Harro

]]> By: Damien Guard http://damieng.com/blog/2009/01/19/linq-to-sql-templates-updated-now-on-codeplex#comment-29930 Damien Guard Wed, 11 Nov 2009 19:39:58 +0000 http://damieng.com/blog/2009/01/19/linq-to-sql-templates-updated-now-on-codeplex#comment-29930 @Daniel : This is normally caused by a DBML coming from another project. The DBML tends to reference the connection via the app.config but the app.config wasn't copied. Opening the DBML in the designer will detect this and remove the offending code so you can setup a new connection. [)amien @Daniel : This is normally caused by a DBML coming from another project. The DBML tends to reference the connection via the app.config but the app.config wasn’t copied. Opening the DBML in the designer will detect this and remove the offending code so you can setup a new connection.

[)amien

]]> By: Daniel Cotter http://damieng.com/blog/2009/01/19/linq-to-sql-templates-updated-now-on-codeplex#comment-29928 Daniel Cotter Wed, 11 Nov 2009 19:33:11 +0000 http://damieng.com/blog/2009/01/19/linq-to-sql-templates-updated-now-on-codeplex#comment-29928 Great tool! It's really nice to be able to customize the L2S code like that. I used it to fix a circular reference problem LINQ was having when serializing a parent entity to JSON (by adding [ScriptIgnore] above any Associations). On another note, the line base(global::.Default., mappingSource) was causing a build error for me (couldn't find Default). Is this just because I'm using VS2010b2? Daniel Great tool! It’s really nice to be able to customize the L2S code like that. I used it to fix a circular reference problem LINQ was having when serializing a parent entity to JSON (by adding [ScriptIgnore] above any Associations).

On another note, the line base(global::.Default., mappingSource) was causing a build error for me (couldn’t find Default). Is this just because I’m using VS2010b2?

Daniel

]]> By: Pavel Kubik http://damieng.com/blog/2009/01/19/linq-to-sql-templates-updated-now-on-codeplex#comment-29793 Pavel Kubik Tue, 10 Nov 2009 14:20:08 +0000 http://damieng.com/blog/2009/01/19/linq-to-sql-templates-updated-now-on-codeplex#comment-29793 Hi, what if I have columns like 'private' and 'operator' in my database table. Compiling the code generated with this template fails, obviously. I can't (or lets say don't want to) make any changes to my tables... Any ideas? Thanks, Pavel. Hi,
what if I have columns like ‘private’ and ‘operator’ in my database table. Compiling the code generated with this template fails, obviously. I can’t (or lets say don’t want to) make any changes to my tables… Any ideas?

Thanks, Pavel.

]]> By: Damien Guard http://damieng.com/blog/2009/01/19/linq-to-sql-templates-updated-now-on-codeplex#comment-29151 Damien Guard Tue, 03 Nov 2009 23:03:00 +0000 http://damieng.com/blog/2009/01/19/linq-to-sql-templates-updated-now-on-codeplex#comment-29151 @Nigel: The warnings I see are: 1. Naming - casing/underscores/discrete (change the names in the DBML) 2. Usage - Settable collection properties (would be a breaking change but you could suppress this warning by modifying the template) [)amien @Nigel: The warnings I see are:

1. Naming – casing/underscores/discrete (change the names in the DBML)
2. Usage – Settable collection properties (would be a breaking change but you could suppress this warning by modifying the template)

[)amien

]]> By: Nigel Deakin http://damieng.com/blog/2009/01/19/linq-to-sql-templates-updated-now-on-codeplex#comment-29115 Nigel Deakin Tue, 03 Nov 2009 14:25:35 +0000 http://damieng.com/blog/2009/01/19/linq-to-sql-templates-updated-now-on-codeplex#comment-29115 Love the reorganised code but not so taken by the CA warnings I get from the code that gets generated. How do I surpress any code warnings from the generated code. The project is marked to ignore such but both standard VS2008 and running with this template causes CA to shout out warnings. Regards, Nigel Love the reorganised code but not so taken by the CA warnings I get from the code that gets generated.

How do I surpress any code warnings from the generated code. The project is marked to ignore such but both standard VS2008 and running with this template causes CA to shout out warnings.

Regards, Nigel

]]> By: Jordan Rieger http://damieng.com/blog/2009/01/19/linq-to-sql-templates-updated-now-on-codeplex#comment-27514 Jordan Rieger Wed, 07 Oct 2009 00:43:56 +0000 http://damieng.com/blog/2009/01/19/linq-to-sql-templates-updated-now-on-codeplex#comment-27514 This is a fantastic piece of plumbing and will save my team a lot of work, specifically in the realm of serialization. I really appreciate your efforts, Damien. I really hope DataContract serialization support is native in the next version of Visual Studio LINQ to SQL. This is a fantastic piece of plumbing and will save my team a lot of work, specifically in the realm of serialization. I really appreciate your efforts, Damien. I really hope DataContract serialization support is native in the next version of Visual Studio LINQ to SQL.

]]>