comments wanted re side-by-side

[mklapp]

Hello,

I am working with a client who has the need to load
both 1.0 and 1.1 of the .NET Framework onto their
machines.

Rightfully, they want to test existing apps running
with both versions before a general release of both
versions.

I am interested in any problems whatsoever any one
has encountered with this. I have read the details,
understand the protectionoffereed by strong versioning
and do not think there are strong reasons for extensive
regression testing. I want to minimze their efforts
while still maintaining safe and robust development, QA
and production environments.

Thank You,

mklapp


Comments pertaining to problems experienced should
specify the type of app (WinForm, Web Service, Web Form,
console App, windows Service etc.), the nature of the
problem and how you fixed it. Accounts of uneventful,
reckless side-by-side upgrades are welcome. Brevity and
specificity counts.

This is not a MS hatchet job. I just want to know the
real experiences of real developers supporting two (or
more?) versions of the .NET Framework.

 

[Les Smith]

All of our applications are in VB.NET, Asp.NET (VB and
C#). All our developers run both release versions and are
switching back and forth constantly, as we have converted
some, but not all, of our apps to 1.1. We have never
experienced one problem that we can attribute to moving to
the latest version. Our main application has been
converted with no problems of any sort, with the
executables.

There are design nuances to be aware of. You can share
forms, classes, and modules between the two releases via
sourcesafe. You can copy controls from a form in 1.0 to a
form in 1.1, but you cannot do the opposite (i.e., copy
controls from a 1.1 form to a 1.0 form, apparently because
the clipboard format of the new IDE has changed). That's
the only caveat that I have encountered in developing in
both releases.

Hope this helps.

https://www.knowdotnet.com