Problem with .NET adoption in MS and performance is that few people
understand (even in Microsoft) what's going on in the framework. For
example, I see lots of people recommending NGEN, but few people mentioning
that if you do that and you don't change the default base addresses of your
assemblies and GAC, you incur the huge cost of rebasing + strong name
verification, usually slower than JIT.

I won't name names but someone I talked to said one of the reasons they
don't use .NET was because if parts of System.* or mscorlib get inlined,
then they can't be serviced through normal framework patches.

--
Josh Einstein (Tablet PC MVP)
Einstein Technologies
Tablet Enhancements for Outlook - Try it free: www.tabletoutlook.com


"JohnGoogle" <JohnGoogle********.co.uk> wrote in message
news:1194899977.631930.228980@v3g2000hsg.googlegro ups.com...
> OMG!
>
> I thought MS were really into .NET!
>
> I just assumed that OneNote used the .Net framework. The time taken to
> display the Tools / Options dialog made me believe that it was a .Net
> application.
>