Unofficial SxS poll

  • Thread starter Thread starter Angel Saenz-Badillos[MS]
  • Start date Start date
A

Angel Saenz-Badillos[MS]

Hello group, I am trying to get a rough idea of how many people are using
Side By Side installations of .net and how it is being used. This is just an
unofficial poll but I would like to encourage your participation so that we
can ship a better product as we keep coming out with new releases.

POLL, please choose the option that more closely describes you:
1) I do not trust side by side installations of .net and do not plan have
multiple Visual Studios/frameworks installed.
2) I have installed Visual Studio and/or Visual Studio 2003 and plan to
install whidbey Visual Studio on my main machine.
3) I have installed Visual Studio and/or Visual Studio 2003 and plan to
install whidbey Visual Studio on my main machine for testing only. I will
remove Whidbey when I am done.
4) I plan to install Whidbey when it comes out and uninstall all previous
versions if everything works ok.

Thank you
 
3- is the closest but I have 2002, 2003 and Whidbey on all of my machines.
I"m using Virtual Machine for Whidbey and longhorn, not b/c I don't trust it
but just so it's easy to install new builds and VM makes life a lot easier.
 
¤ Hello group, I am trying to get a rough idea of how many people are using
¤ Side By Side installations of .net and how it is being used. This is just an
¤ unofficial poll but I would like to encourage your participation so that we
¤ can ship a better product as we keep coming out with new releases.
¤
¤ POLL, please choose the option that more closely describes you:
¤ 1) I do not trust side by side installations of .net and do not plan have
¤ multiple Visual Studios/frameworks installed.
¤ 2) I have installed Visual Studio and/or Visual Studio 2003 and plan to
¤ install whidbey Visual Studio on my main machine.
¤ 3) I have installed Visual Studio and/or Visual Studio 2003 and plan to
¤ install whidbey Visual Studio on my main machine for testing only. I will
¤ remove Whidbey when I am done.
¤ 4) I plan to install Whidbey when it comes out and uninstall all previous
¤ versions if everything works ok.

No. 4. Assuming the release version here, not the beta.


Paul ~~~ (e-mail address removed)
Microsoft MVP (Visual Basic)
 
2) when Visual Studio.Net 2005 is RTM.

I have to use old versions for maintenance of old apps (not mine) reasons :)
 
Thanks for your response! very much appreciated.

I should have made it clearer that when I referred to Whidbey versions of
the framework and of Visual Studio I was talking about the released version.
Would this influence your decision?

--
Angel Saenz-Badillos [MS] Managed Providers
This posting is provided "AS IS", with no warranties, and confers no
rights.Please do not send email directly to this alias.
This alias is for newsgroup purposes only.

William Ryan eMVP said:
3- is the closest but I have 2002, 2003 and Whidbey on all of my machines.
I"m using Virtual Machine for Whidbey and longhorn, not b/c I don't trust it
but just so it's easy to install new builds and VM makes life a lot easier.

Angel Saenz-Badillos said:
Hello group, I am trying to get a rough idea of how many people are using
Side By Side installations of .net and how it is being used. This is
Click to expand...
just
an
unofficial poll but I would like to encourage your participation so that we
can ship a better product as we keep coming out with new releases.

POLL, please choose the option that more closely describes you:
1) I do not trust side by side installations of .net and do not plan have
multiple Visual Studios/frameworks installed.
2) I have installed Visual Studio and/or Visual Studio 2003 and plan to
install whidbey Visual Studio on my main machine.
3) I have installed Visual Studio and/or Visual Studio 2003 and plan to
install whidbey Visual Studio on my main machine for testing only. I will
remove Whidbey when I am done.
4) I plan to install Whidbey when it comes out and uninstall all previous
versions if everything works ok.

Thank you
--
Angel Saenz-Badillos [MS] Managed Providers
This posting is provided "AS IS", with no warranties, and confers no
rights.Please do not send email directly to this alias.
This alias is for newsgroup purposes only.
Click to expand...
Click to expand...
 
Thank you for your response, so in your case compatibility between versions
is more important than side by side behavior is this correct?

There are breaking changes between v1.0 and v1.1, there will be more
breaking changes when v2.0 ships. The list is as small we can possibly make
it and mostly related to security issues or very bad bugs. Here is a
complete list:
http://www.gotdotnet.com/team/changeinfo/Forwards1.0to1.1/default.aspx
http://www.gotdotnet.com/team/changeinfo/Backwards1.0to1.1/default.aspx

I am trying to understand whether the cost of verifying compatibility is a
barrier to updating to the latest release or if it is more expensive to keep
multiple development environments.
Thanks
--
Angel Saenz-Badillos [MS] Managed Providers
This posting is provided "AS IS", with no warranties, and confers no
rights.Please do not send email directly to this alias.
This alias is for newsgroup purposes only.


 
Miha, thanks for your response. It sounds like you already have a lot of
experience with side by side between 1.0 and 1.1. So in your case it is more
expensive to rev up existing code than to maintain multiple development
environments, and you expect all of the visual studio versions to "play
nice" with each other is this correct?

What about asp.net applications and COM loading of managed components that
by default uses the latest version of the framework installed in your
machine. Are you getting around these issues with config files and setup?
ignoring the problem and relying on compatibility?

To clarify my question for other people who may be reading this, when you
have v1.0 and v1.1 versions of the framework installed you expect that a
program compiled with v1.0 will run against the 1.0 framework. This is true
in all cases except two, when using asp.net the code is compiled when it is
run, so even though you developed your asp.net page with 1.0 it will run
under v1.1 (This is configurable in iis6). The second exception is that COM
by default loads the latest version of the framework, so if you have a 1.0
dll that is being called by a COM component it will run on v1.1 (this is
config file settable)

Thank you,
--
Angel Saenz-Badillos [MS] Managed Providers
This posting is provided "AS IS", with no warranties, and confers no
rights.Please do not send email directly to this alias.
This alias is for newsgroup purposes only.

Miha Markic said:
2) when Visual Studio.Net 2005 is RTM.

I have to use old versions for maintenance of old apps (not mine) reasons :)

--
Miha Markic [MVP C#] - RightHand .NET consulting & development
miha at rthand com
www.rthand.com

Angel Saenz-Badillos said:
Hello group, I am trying to get a rough idea of how many people are using
Side By Side installations of .net and how it is being used. This is
Click to expand...
just
an
unofficial poll but I would like to encourage your participation so that we
can ship a better product as we keep coming out with new releases.

POLL, please choose the option that more closely describes you:
1) I do not trust side by side installations of .net and do not plan have
multiple Visual Studios/frameworks installed.
2) I have installed Visual Studio and/or Visual Studio 2003 and plan to
install whidbey Visual Studio on my main machine.
3) I have installed Visual Studio and/or Visual Studio 2003 and plan to
install whidbey Visual Studio on my main machine for testing only. I will
remove Whidbey when I am done.
4) I plan to install Whidbey when it comes out and uninstall all previous
versions if everything works ok.

Thank you
--
Angel Saenz-Badillos [MS] Managed Providers
This posting is provided "AS IS", with no warranties, and confers no
rights.Please do not send email directly to this alias.
This alias is for newsgroup purposes only.
Click to expand...
Click to expand...
 
Hi Angel,

Angel Saenz-Badillos said:
Miha, thanks for your response. It sounds like you already have a lot of
experience with side by side between 1.0 and 1.1. So in your case it is more
expensive to rev up existing code than to maintain multiple development
environments, and you expect all of the visual studio versions to "play
nice" with each other is this correct?
Click to expand...

Actually it is not my decision. It is the client's.
If I would have to take a decision I would certainly go with rev up.
Plus, I can tell you how much I am suffering with 3rd party components (one
client uses one version while the other another version).
However, the pain is only at design time. No problems at runtime that I know
of.
And to answer your question: Yes, I am expecting vsnet2005 to be side by
side.
Otherwise you'll just add a new dimension to my versioning problems :)
What about asp.net applications and COM loading of managed components that
by default uses the latest version of the framework installed in your
machine. Are you getting around these issues with config files and setup?
ignoring the problem and relying on compatibility?
Click to expand...

Sorry, currently I have only WinForms applications that I have to take care
of.
 
Hi Angel:

Hmm, here's basically what we've done in the past. Install the beta and
start getting ready for it. When we get the new RTM Release, we made an
upgrade version of each of our apps, and tested thoroughly, still both side
by side. After testing and enough time to convince us everything was
totally compatible, we got rid of the previous version. It's not that we
don't trust the products, we just have 24/7 uptime requirements, so we have
to be as sure as possible everything will work before we make any full
transition....a decision more out of neurotic worrying than logic but in our
environment, better safe than sorry.

Anyway, within 2 months of RTM , VS 2005 will be installed on all of our
machines and we'll probably free up the space 2003 is taking.. that's what
we've done in the past anyway. We all have VS 2005 on our machines now.
Angel Saenz-Badillos said:
Thanks for your response! very much appreciated.

I should have made it clearer that when I referred to Whidbey versions of
the framework and of Visual Studio I was talking about the released version.
Would this influence your decision?

--
Angel Saenz-Badillos [MS] Managed Providers
This posting is provided "AS IS", with no warranties, and confers no
rights.Please do not send email directly to this alias.
This alias is for newsgroup purposes only.

William Ryan eMVP said:
3- is the closest but I have 2002, 2003 and Whidbey on all of my machines.
I"m using Virtual Machine for Whidbey and longhorn, not b/c I don't
Click to expand...
trust
it
but just so it's easy to install new builds and VM makes life a lot easier.

Hello group, I am trying to get a rough idea of how many people are using
Side By Side installations of .net and how it is being used. This is
Click to expand...
just
an
unofficial poll but I would like to encourage your participation so
Click to expand...
that
we
can ship a better product as we keep coming out with new releases.

POLL, please choose the option that more closely describes you:
1) I do not trust side by side installations of .net and do not plan have
multiple Visual Studios/frameworks installed.
2) I have installed Visual Studio and/or Visual Studio 2003 and plan to
install whidbey Visual Studio on my main machine.
3) I have installed Visual Studio and/or Visual Studio 2003 and plan to
install whidbey Visual Studio on my main machine for testing only. I will
remove Whidbey when I am done.
4) I plan to install Whidbey when it comes out and uninstall all previous
versions if everything works ok.

Thank you
--
Angel Saenz-Badillos [MS] Managed Providers
This posting is provided "AS IS", with no warranties, and confers no
rights.Please do not send email directly to this alias.
This alias is for newsgroup purposes only.
Click to expand...
Click to expand...
Click to expand...
 
¤ Thank you for your response, so in your case compatibility between versions
¤ is more important than side by side behavior is this correct?

Yes, definitely. However, this isn't to say that if a version of the framework had breaking changes
which significantly impacted our applications, that the side by side behavior wouldn't be
implemented at our site.

The side by side implementation would be a fall back if we needed to modify a number of applications
in order to resolve breaking changes in a new VS.NET release.

¤
¤ There are breaking changes between v1.0 and v1.1, there will be more
¤ breaking changes when v2.0 ships. The list is as small we can possibly make
¤ it and mostly related to security issues or very bad bugs. Here is a
¤ complete list:
¤ http://www.gotdotnet.com/team/changeinfo/Forwards1.0to1.1/default.aspx
¤ http://www.gotdotnet.com/team/changeinfo/Backwards1.0to1.1/default.aspx
¤
¤ I am trying to understand whether the cost of verifying compatibility is a
¤ barrier to updating to the latest release or if it is more expensive to keep
¤ multiple development environments.

Fortunately we only had a single web application that was in production under 1.0 so the migration
to 2003 and the 1.1 framework was a non issue. The breaking changes did not affect our application.

We un installed the 1.0 framework after verifying that the application was operating properly under
1.1.


Paul ~~~ (e-mail address removed)
Microsoft MVP (Visual Basic)
 
William,
Thank you for your detailed description, I really appreciate the
information.

Angel

--
Angel Saenz-Badillos [MS] Managed Providers
This posting is provided "AS IS", with no warranties, and confers no
rights.Please do not send email directly to this alias.
This alias is for newsgroup purposes only.

William Ryan eMVP said:
Hi Angel:

Hmm, here's basically what we've done in the past. Install the beta and
start getting ready for it. When we get the new RTM Release, we made an
upgrade version of each of our apps, and tested thoroughly, still both side
by side. After testing and enough time to convince us everything was
totally compatible, we got rid of the previous version. It's not that we
don't trust the products, we just have 24/7 uptime requirements, so we have
to be as sure as possible everything will work before we make any full
transition....a decision more out of neurotic worrying than logic but in our
environment, better safe than sorry.

Anyway, within 2 months of RTM , VS 2005 will be installed on all of our
machines and we'll probably free up the space 2003 is taking.. that's what
we've done in the past anyway. We all have VS 2005 on our machines now.
Angel Saenz-Badillos said:
Thanks for your response! very much appreciated.

I should have made it clearer that when I referred to Whidbey versions of
the framework and of Visual Studio I was talking about the released version.
Would this influence your decision?

--
Angel Saenz-Badillos [MS] Managed Providers
This posting is provided "AS IS", with no warranties, and confers no
rights.Please do not send email directly to this alias.
This alias is for newsgroup purposes only.

William Ryan eMVP said:
3- is the closest but I have 2002, 2003 and Whidbey on all of my machines.
I"m using Virtual Machine for Whidbey and longhorn, not b/c I don't
Click to expand...
trust
it
but just so it's easy to install new builds and VM makes life a lot easier.

Hello group, I am trying to get a rough idea of how many people are using
Side By Side installations of .net and how it is being used. This is just
an
unofficial poll but I would like to encourage your participation so that
we
can ship a better product as we keep coming out with new releases.

POLL, please choose the option that more closely describes you:
1) I do not trust side by side installations of .net and do not plan have
multiple Visual Studios/frameworks installed.
2) I have installed Visual Studio and/or Visual Studio 2003 and plan to
install whidbey Visual Studio on my main machine.
3) I have installed Visual Studio and/or Visual Studio 2003 and plan to
install whidbey Visual Studio on my main machine for testing only. I will
remove Whidbey when I am done.
4) I plan to install Whidbey when it comes out and uninstall all previous
versions if everything works ok.

Thank you
--
Angel Saenz-Badillos [MS] Managed Providers
This posting is provided "AS IS", with no warranties, and confers no
rights.Please do not send email directly to this alias.
This alias is for newsgroup purposes only.
Click to expand...
Click to expand...
Click to expand...
 
Paul,
Thank you for your feedback, I really appreciate your comments.

Angel

--
Angel Saenz-Badillos [MS] Managed Providers
This posting is provided "AS IS", with no warranties, and confers no
rights.Please do not send email directly to this alias.
This alias is for newsgroup purposes only.


Paul Clement said:
¤ Thank you for your response, so in your case compatibility between versions
¤ is more important than side by side behavior is this correct?

Yes, definitely. However, this isn't to say that if a version of the framework had breaking changes
which significantly impacted our applications, that the side by side behavior wouldn't be
implemented at our site.

The side by side implementation would be a fall back if we needed to
Click to expand...
modify a number of applications
Click to expand...
 
Miha,
Thank you for your feedback, I was really hoping to find somebody that had
external constraints on side by side issues and your information helps a
lot.

Angel

--
Angel Saenz-Badillos [MS] Managed Providers
This posting is provided "AS IS", with no warranties, and confers no
rights.Please do not send email directly to this alias.
This alias is for newsgroup purposes only.
 
Back
Top