There would be some performance gains in CLR 2.0, particularly if you use
generics. If your code compiles under 1.1 then your'e not using generics,
and any performance gain would probably be minor. Also since you're running
a beta version of CLR 2.0 performance is actually probably slower than 1.1
until you get your hands on a release candidate.
There is always some potential for beta versions of the CLR to not coexist
peacefully with the final release version, particularly since as far as I
know, it's not 110% feature complete. If you have a lot of control over a
limited distribution and can correct any problems when the final CLR is
released, then you might consider going with the beta for development,
otherwise I would err on the side of caution.
Finally there are the licensing issues to consider. I frankly am not up to
speed on these but you need to determine whether releasing a finished
product running on the beta CLR is even legal.
--Bob
"Markon" <mm@nospam.hr> wrote in message news:d5*********@ss405.t-com.hr...
Hello
I am tempted to deploy my applications compiled on framework2.0
Does anyone have an argument why I shouldn't?
I ask because I have SDK's for v1.0, v1.1 and v2.0
and just recently I begun compiling apps in v1.1 (for customer
deployement).
Now, I have noticed some problems with printing on MS Server 2003 (when
remote users connect to server and run app from it) and problems with
display of some drawn items on WinXP sp2, both of which dissapear on apps
compiled with 2.0
What I am affraid of eventual data loss if I would deploy apps compiled
with
2.0 ( unfortunately I have not enough time or patience to thoroughly test
it).
Also, what is the gain from v2.0 vs v1.1 (my code compiles without any
change on both)
