Comments on: CodeSmith template to generate LINQ To SQL Data Context http://damieng.com/blog/2007/06/26/codesmith-template-to-generate-linq-to-sql-data-context?utm_source=rss&utm_medium=rss&utm_campaign=codesmith-template-to-generate-linq-to-sql-data-context A .NET developer in Redmond Fri, 23 Jul 2010 04:45:33 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: steve http://damieng.com/blog/2007/06/26/codesmith-template-to-generate-linq-to-sql-data-context#comment-1933 steve Wed, 27 Jun 2007 03:39:02 +0000 http://damieng.com/blog/archive/2007/06/26/codesmith-template-to-generate-linq-to-sql-data-context.aspx#comment-1933 Unless that doesn't actually hide it but just categorises it for filtering? MSDN is pretty damn vague on the whole thing (shock) and I've not had to debug .Net much before... Unless that doesn’t actually hide it but just categorises it for filtering? MSDN is pretty damn vague on the whole thing (shock) and I’ve not had to debug .Net much before…

]]> By: steve http://damieng.com/blog/2007/06/26/codesmith-template-to-generate-linq-to-sql-data-context#comment-1932 steve Wed, 27 Jun 2007 03:36:42 +0000 http://damieng.com/blog/archive/2007/06/26/codesmith-template-to-generate-linq-to-sql-data-context.aspx#comment-1932 Cool. <br /><br />The DebuggerNonUserCodeAttribute makes me shudder though - asking to hide code from the debugger just seems like asking someone to kick you in the nuts. What's wrong with just using 'step over' (or equivalent) when you don't wanna see something? Or defining a visibility mask in the debugger session (typical Eclipse way)? Hiding stuff from the debugger statically in the code itself just gives me horrible nightmares of debugging VB6 and knowing there's something wrong happening in between the lines that you can't see... Cool.

The DebuggerNonUserCodeAttribute makes me shudder though – asking to hide code from the debugger just seems like asking someone to kick you in the nuts. What’s wrong with just using ‘step over’ (or equivalent) when you don’t wanna see something? Or defining a visibility mask in the debugger session (typical Eclipse way)? Hiding stuff from the debugger statically in the code itself just gives me horrible nightmares of debugging VB6 and knowing there’s something wrong happening in between the lines that you can’t see…

]]>