Comments on: Introducing PostSharp to your team

By: Gael Fraiteur

Gael Fraiteur — Thu, 17 Sep 2009 18:23:11 +0000

2. Ngen is not automatic. You have to ask (using the ngen utility). Ngenned images are used only when the command-line utility is used (PostSharpUseCommandLine=True).

By: Pawel Lesnikowski

Pawel Lesnikowski — Thu, 17 Sep 2009 17:36:47 +0000

Thanks Gael,

1.
DontImportPostSharp updated to True

2.
Why is PostSharp not ngenned in such case?
Shouldn’t it be ngenned after first usage?

3.
I just realized that in PostSharp 1.5 you should use PostSharp-1.5.targets instead of PostSharp.targets

By: Gael Fraiteur

Gael Fraiteur — Thu, 17 Sep 2009 15:57:45 +0000

Hm, XML in comments don’t work!!

So one more time:

You should use [DontImportPostSharp]True[/DontImportPostSharp]and not [DontImportPostSharp]False[/DontImportPostSharp]. This ensures that PostSharp targets are not imported twice in case that PostSharp is installed globally on the machine.

Finally, you way want to use [PostSharpUseCommandLine]True[/PostSharpUseCommandLine] if you experience OutOfMemory exceptions in Visual Studio (although this may slow down build if images are not ngenned).

By: Gael Fraiteur

Gael Fraiteur — Thu, 17 Sep 2009 15:55:37 +0000

Thank your for this blog.

I would like to precise that this way of using PostSharp without using it results in slower build time operations because PostSharp is not ngenned. Sounds stupid, but JIT compilation time is not neglictible for an application that is triggers many times per second.

Another thing:

You should use True and not False. This ensures that PostSharp targets are not imported twice in case that PostSharp is installed globally on the machine.

Finally, you way want to use True if you experience OutOfMemory exceptions in Visual Studio.