Who is upset--yes upset--at the frequent changes to VisualStudio--now it's VS 2012!

[RayLopez99]

Every time they come out with another Visual Studio my code breaks. Usuallyit's fixable but I take the lazy way out (and I'm too busy) and just get another server to house any new software. Right now I have two servers running, one for VS 08 and one for VS 10. Might have to get a third once VS 2012 is officially released. With virtual OSes it's becoming much cheaper todo this, but still it's a pain and an expense.

Who else wishes Microsoft would just stick to issuing service packs insteadof coming out with brand new Visual Studios?

RL

 

[Jeff Gaines]

Who else wishes Microsoft would just stick to issuing service packs
instead of coming out with brand new Visual Studios?

Why do you treat upgrading as compulsory?

 

[Alain Dekker]

I'm still using Word and Excel 97 (far better than Office 2007 for simple
tasks), Visual Studio 2003.NET/2005 and Windows XP. We only upgrade if we
have to. The pain of upgrading is non-trivial. I know a colleague (using
Embarcadero Delphi) who upgraded from Delphi7 to Delphi XE2 and after
slogging through the pain of the upgrade, the EXEs produced were 3 times the
size and half the speed. What's the point?

I agree with the OP. Ideally, software companies (and particularly
Microsoft) should just issue SPs. Unfortunately, in the real world they only
generate income from new sales which means getting people to upgrade. They
offer the carrot of new features and bug fixes and the stick of discontinued
support to coerce people to upgrade.

A sad reality...but Jeff is also right. Unless there is a compelling reason
to do so...don't upgrade.
Alain

 

[Brian Cryer]

Every time they come out with another Visual Studio my code breaks.
Usually it's fixable but I take the lazy
way out (and I'm too busy) and just get another server to house any new
software. Right now I have two
servers running, one for VS 08 and one for VS 10. Might have to get a
third once VS 2012 is officially
released. With virtual OSes it's becoming much cheaper to do this, but
still it's a pain and an expense.

Who else wishes Microsoft would just stick to issuing service packs
instead of coming out with brand new
Visual Studios?

Yes, I agree that I prefer for Microsoft to issue service packs to fix the
bugs in Visual Studio rather than having to wait for the next version.

Re updates breaking code, I have a number of Visual Studio projects, some of
which have been rolled forward from Visual Studio 2005, to 2008 and now
2010. (Not yet tried 2012.) I don't recall things ever breaking, if anything
did then it certainly wasn't significant. Yes I have warnings that some
things I'm using are now obsolete, and yes I've had things break when I
moved from 2003/IIS 6 to 2008/IIS7. Perhaps you and I are using different
parts of the framework and I've just been lucky? Thinking about it, I have
known it to break third party plugins, but that is all.

When VS 2012 is finally released (and I'm not going to both to look at the
pre-release candidate), I expect to upgrade all of my projects to VS 2012
and I going by past experience I wouldn't expect any issues. It is certainly
easier from a management perspective to have all projects on the same
version of Visual Studio.

Even if you do have issues with Visual Studio then you shouldn't need
multiple servers. Even with IIS 6 you could have multiple applications each
using a different .net framework. So I'd suggest you take a long hard look
at why you have multiple servers because I can't see any reason why you
should need them. It might also be worth looking at what your issues are
when you upgrade, because your experience does seem to be unusual.

 

[Arne Vajhøj]

Every time they come out with another Visual Studio my code breaks.
Usually it's fixable but I take the lazy way out (and I'm too busy) and
just get another server to house any new software. Right now I have two
servers running, one for VS 08 and one for VS 10. Might have to get a
third once VS 2012 is officially released. With virtual OSes it's
becoming much cheaper to do this, but still it's a pain and an expense.

It is relative rare that a new .NET version break old .NET code.

What problems do you encounter?

And even if it does break, then VS can build using the old .NET
version, so you can use the latest VS but keep the .NET version.

Who else wishes Microsoft would just stick to issuing service packs instead
of coming out with brand new Visual Studios?

Give the above: not me.

Arne

 

[RayLopez99]

On 7/17/2012 1:39 AM, RayLopez99 wrote:
> Every time they come out with another Visual Studio my code breaks.
> Usually it's fixable but I take the lazy way out (and I'm too busy) and
> just get another server to house any new software. Right now I have two
> servers running, one for VS 08 and one for VS 10. Might have to get a
> third once VS 2012 is officially released. With virtual OSes it's
> becoming much cheaper to do this, but still it's a pain and an expense.

It is relative rare that a new .NET version break old .NET code.

What problems do you encounter?

And even if it does break, then VS can build using the old .NET
version, so you can use the latest VS but keep the .NET version.

My Silverlight broke...maybe it was a Third Party library function like theother poster said... but I did not realize you could build to a previous version...I will try and remember this...but just loaded Visual Studio 2010 and I don't see this...where is it Mr. Arne? Not under Configuration Manager? Build | Configuration Manager yields nothing...

Give the above: not me.

Arne

Please tell me where. Long live Finland and/or Hungary!

RL

 

[Brian Cryer]

My Silverlight broke...maybe it was a Third Party library function like
the other poster said... but I did not
realize you could build to a previous version...I will try and remember
this...but just loaded Visual Studio 2010
and I don't see this...where is it Mr. Arne? Not under Configuration
Manager? Build | Configuration Manager
yields nothing...


Please tell me where. Long live Finland and/or Hungary!

Open up the properties for your project and it will be burried under there.
Look for "Target framework", and it will probably be under "Application" or
"Build" settings depending on the type of project.

Silverlight has also gone through a number of versions, but I don't
personally have any experience upgrading from one version to another, but it
sounds like that might perhaps be your problem not Visual Studio.

 

[Arne Vajhøj]

My Silverlight broke...maybe it was a Third Party library function like the other poster said...

SL is not specific enough to comment on.

but I did not realize you could build to a previous version...I will
try and remember this...but just loaded Visual Studio 2010 and I
don't see this...where is it Mr. Arne? Not under Configuration
Manager? Build | Configuration Manager yields nothing...

In my version:

project
properties
application
target framework

to change the .NET version

project
properties
build
advanced
language version

to change C# version.

Please tell me where.

See above.

Long live Finland and/or Hungary!

????

Arne

 

[RayLopez99]

Open up the properties for your project and it will be burried under there.
Look for "Target framework", and it will probably be under "Application" or
"Build" settings depending on the type of project.

Silverlight has also gone through a number of versions, but I don't
personally have any experience upgrading from one version to another, but it
sounds like that might perhaps be your problem not Visual Studio.

Yes, that's it! Thanks to Arne too! I found it...you can indeed go one step down Visual Studio 2010 allows to go from SL 4 to SL3.

This is good but I am going to stick to developing on separate computers for each version of the language in question since that's the way I set up stuff to work...but maybe I'll try this method as well, and hope it works...

Long live the UK! Go Team GB!

RL

 

[RayLopez99]

On Wednesday, July 18, 2012 6:16:41 PM UTC-4, Arne Vajhøj wrote:

[useful stuff]

But I just realized while this is good for you to develop 'down' one version, it does not solve my problem of 'upgrading'.

Let me explain: I wrote a program in VS 2008 in Silverlight 2 I think it was. Then I converted it to SL3 no problem. Then in VS 2010 I converted it(or tried to): SL 4 but it broke. Library reference stuff. That's what Imean. But I thank you for this suggestion, which is also good.

See above.

> Long live Finland and/or Hungary!

????

Arne

That's my running joke with you Arne--your name, it reminds me of Finland or Hungary.

RL

 

[Arne Vajhøj]

On Wednesday, July 18, 2012 6:16:41 PM UTC-4, Arne Vajhøj wrote:

[useful stuff]

But I just realized while this is good for you to develop 'down' one version, it does not solve my problem of 'upgrading'.

Let me explain: I wrote a program in VS 2008 in Silverlight 2 I think it was. Then I converted it to SL3 no problem. Then in VS 2010 I converted it (or tried to): SL 4 but it broke. Library reference stuff. That's what I mean. But I thank you for this suggestion, which is also good.

You should be able to stay at SL3 in VS 2010.

project
properties
silverlight
target version

Arne

 

[RayLopez99]

You should be able to stay at SL3 in VS 2010.

project
properties
silverlight
target version

Arne

Yes I know. But I want to 'upgrade' it to SL4 and it breaks... but no big deal.

In other news...I am going through a book that I skimmed over quickly a while ago, called C# 3.0 Design Patterns by J. Bishop. Pretty good on "Gang of Four" design patterns. So, maybe there are a few things I don't know about programming? Like the Decorator class...I see why they use it...escapedme the first time.

RL

 

[Arne Vajhøj]

Yes I know. But I want to 'upgrade' it to SL4 and it breaks... but no big deal.

If you want to upgrade from SL3 to SL4 and your code does not
work with SL4, then there is very little that VS can do about it.

In other news...I am going through a book that I skimmed over quickly
a while ago, called C# 3.0 Design Patterns by J. Bishop. Pretty good
on "Gang of Four" design patterns. So, maybe there are a few things
I don't know about programming? Like the Decorator class...I see why
they use it...escaped me the first time.

There is always something to learn.

Arne