Comments on: T4 Tutorial: Debugging Code Generation Files

By: RT

RT — Sat, 09 Jan 2010 16:46:03 +0000

Awesome post. Thanks.

By: Oleg Sych

Oleg Sych — Wed, 08 Jul 2009 10:54:02 +0000

Alex, what did you refer to when you said “Break command”? Are you using Debugger.Break(); statement?

By: Alexandre

Alexandre — Tue, 07 Jul 2009 12:32:56 +0000

Hey Oleg,

thanks for the info. I tried to debug some Run time error. Unfortunately the Break command seems not to be picked up. It has no effect :( I have set the T4 attribute to debug = true. I’m running VS2008 with SP1.

Any idea?

Alex.

By: Introspection vs reflection

Introspection vs reflection — Wed, 24 Jun 2009 09:33:29 +0000

[…] Oleg states here, if you need to analyze assemblies during code generation, you should use fxcop […]

By: Rory Becker

Rory Becker — Mon, 27 Oct 2008 10:46:45 +0000

ok, as seems to be the way of the web, as soon as I posted my comment…I have found the solution. It seems that the 64bit edition requires that the registry switch is placed in a different location for 32bit apps. Therefore the “Microsoft” part of the registry path mentioned in fact sits under and additional ‘Wow6432Node’ Folder in my case. This sorted … Everything works :) Thanks again Oleg.

By: Rory Becker

Rory Becker — Mon, 27 Oct 2008 10:40:04 +0000

Hey Oleg

Great Site… Really good. I’m Loving T4 largely down to your wonderful source of information..

I’m reading your page on Debugging a T4 script. I’m using VS2008 Pro and Vista Ultimate 64bit Edition… Unfortunately it seems that even after following your advise on editing the registry to allow debugging… I am still experiencing a crash that takes out VS instead of launching a new version for debugging.

Any additional ideas?