Why is .NET v2.0 slower than v1.1?

[miffy900]

I've been converting alot of previously existing projects from v1.1 to
the current v2.0 beta,
and so far, everything has been going well, will little or no hiccups in
the recompiling and
code reforming. I've noticed however, that, speed-wise, my recompiled
apps that run on the
v2.0 framework are somewhat slower and a bit less responsive than my
apps that ran
on the v1.1 of the framework. I have both frameworks installed on the
same machine, so I
was just wondering, if this slow-down was because of both versions of
the framework
were on the same machine. Is this the case? I never came across this in
the documentation.
And this lag in performance and response time affects my C++/CLI
projects (converted from
managed C++) as well.

 

[Umer]

hello miffy900,

well u might just encounter all these perf problems in just the betas. The
final version will be quite faster compared to the betas and .NET 2.0 apps
are expected to be more faster and responsive than .NET 1.1 Apps when the
framework is released.

Umer.

 

[CT]

You can't compare a beta product to a released one. Well, you can, but it
won't be a fair comparison, as the beta product hasn't been performance
optimized yet.

 

[miffy900]

I hope your right
also, is there any statement that Microsoft has made to confirm this?
Other beta's that ms has
released in the past, werent ever 'slow' or laggy like this one; well
none that ive tried anyway.

 

[Sami Kuhmonen]

I've been converting alot of previously existing projects from v1.1 to
the current v2.0 beta,
and so far, everything has been going well, will little or no hiccups in
the recompiling and
code reforming. I've noticed however, that, speed-wise, my recompiled
apps that run on the
v2.0 framework are somewhat slower and a bit less responsive than my
apps that ran
on the v1.1 of the framework.

Maybe that's because the 2.0 FW is in beta and not optimized? You should
never perform performance comparison between betas and final products.