Will VS2010 run on XP? | The Coffeehouse

alexmac

Hi,
Do you know if VS2010 will run on XP? Some of the preview bits are Vista only.

Yes I know XP is getting a bit old now but was a query from a user group I gave a talk at.

Thanks,

Alex

Dr Herbie
Horses for courses

Actually, that's a good point : I don't know of ANY businesses running Vista and the company I work for has no plans to upgrade from XP anytime soon (we run what our customers run, hell we're still on SQLServer2000).

Herbie

EDIT: to clarify when I say 'I don't know any businesses running Vista', I should have put 'I don't have any customers running Vista, or have any friends working at companies running Vista'

PaoloM
Hypermediocrity

In reply to Dr Herbie

#Apr 8th @ 7:56 AM

They'll probably won't have a need for VS 2010 as well Smiley

alexmac

In reply to Dr Herbie

#Apr 8th @ 7:56 AM

I agree with Dr Herbie I dont know of any businesses running vista either.

Dr Herbie
Horses for courses

In reply to PaoloM

#Apr 8th @ 9:13 AM

So you're suggesting that the only reason to get 2010 is to target Vista\Windows7?

Oh, come on.

I've seen the VS\TFS 2010 preview videos (we'especially excited about the branching\merging UI changes). Jusr becuase we're still writing WinForms code doesn't mean we don't benefit from the new toolings in newer versions of the IDE.

Herbie

vesuvius
Das Glasperlenspiel

In reply to alexmac

#Apr 8th @ 12:59 PM

I agree with Paolo, what would be the business need to use VS 2010 if you are targeting an OS that is most likely using Windows Forms applications?

As a Winforms developer - which I am by the way - there is very little on offer between Visual Studio 2005/2008/2010 so why would you need the upgrade?

There is a big push towards WPF/Silverlight, with the tools reaching puberty now, so for ISV's wanting to make the switch, then VS2010 targetting Windows 7 seems a logical choice.

This is why managed support is going to be need to be baked into VS 2010 and fully supported, otherwise ISV's are going to be like Business was with Vista and say "we don't need VS 2010" as there is no ROI.

figuerres
???

In reply to PaoloM

#Apr 8th @ 9:13 AM

WHoa... that's not a very good statement there....

VS should be able to run on XP, Vista and Win 7

thats in line with most other MSFT products I have used.

there may be advamntages to using the new os but XP is still not "retired"
now win say win 8 comes alonmg and XP is fully out of the mainstream then ok.

Ion Todirel
buuu

> Will VS2010 run on XP?

Definitely, why wouldn't it? Wink

PerfectPhase
"This is not war, this is pest control!" - Dalek to Cyberman

In reply to Ion Todirel

#Apr 8th @ 1:15 PM

Given that the CTP was running on 2003, I'd say it's a pretty safe bet it'll run on XP.

gadget

In reply to vesuvius

#Apr 8th @ 1:12 PM

There may be very liittle change to Winforms between Vs 2005 and 2008 but how are you going to use any of the new features like Linq or WCF if you haven't moved off of 2005. And XML literals in VB. and on and on.

We are a winforms shop but I wouldn't even consider going back to VS 2005.

As for XP vs Windows 7 or Vista. Our customer deployments are XP but all of our developers/support staff run Vista x64. If we need to test something in xp we do it in Vmware.

W3bbo
The Master of Baiters

In reply to Ion Todirel

#Apr 8th @ 1:15 PM

To push adoption of Windows 7?

Remember how Halo 2 was artificially gimped so it only ran on Windows Vista machines, despite not using Dx10 at all?

TommyCarlier
I want my scalps!

In reply to vesuvius

#Apr 8th @ 1:12 PM

At work, I use Visual Studio 2005 on Windows XP. The reason I'm still using XP (my boss has asked me if I wanted to upgrade to Vista) is to make sure that the applications I develop work great on Windows XP. We're still developing in .NET 2.0 and Windows Forms, which is a conscious decision. At home, I use Visual Studio 2008 while still developing mainly in .NET 2.0 and Windows Forms. But VS2008 gives me the C# 3 compiler, background compilation and all the other new improvements while still targeting .NET 2.0. We're planning to upgrade to VS2008 at work too, without upgrading my developer machine to Vista.

vesuvius
Das Glasperlenspiel

In reply to gadget

#Apr 8th @ 1:49 PM

It would take a very wealthy software house to upgrade their system, just so they can use Linq. Stored procedures are superior to Linq, and I find them easier to construct.

If you do need WCF, then you can use VWD Express, but likelyhood now, is you are already deeply involved in ASMX web services already, so changing your service layer again would require a wealthy software house, and customers that like their systems upgraded willy-nilly.

I have Pro C# 2005 and 2008 by Andrew Troelsen, and doubt I'm in a hurry to get Pro C# 2010. .NET is moving far to fast at present, and I still find enormous value in .NET 2.0.

I too develop in VS 2008, but from a head-versus-heart, i.e. business sense, I find it impossible to justify moving to .NET 4.0, if you are targeting XP using Windows Forms.

Yggdrasil
Pour me a cab, 'cause I can't drink no more.

In reply to vesuvius

#Apr 9th @ 12:17 AM

Read up again on what Linq gives you. I find it painful to return to .NET2.0/VS2005 because I miss Linq to Objects so darn much. The ability to query/slice/filter/join any IEnumerable<T> is a godsend.

Bass
www.spreadfirefox.com/5years/

In reply to Yggdrasil

#Apr 9th @ 9:14 AM

I am trying to understand what is fundamentally different between embedded SQL (i.e. SQL-to-Objects) and Linq other then a slightly different syntax. I know .NET/C# never supported embedded SQL but still.

Bass
www.spreadfirefox.com/5years/

In reply to TommyCarlier

#Apr 8th @ 10:49 PM

I am also using Visual Studio 2005, but I would like to change to Visual Studio 2008. Does anyone know if I can make Visual Studio 2005 compatible projects in 2008? That is an important requirement.

Harlequin
http://twitter.com/TrueHarlequin

In reply to Bass

#Apr 9th @ 10:17 AM

I doubt it. Open up a VS2005 project in VS2008 you get the conversion wizard.

As for the argument:
"The reason I'm still using XP is to make sure that the applications I develop work great on Windows XP"
...are you also testing your apps in Vista/Windows7?

vesuvius
Das Glasperlenspiel

In reply to Bass

#Apr 9th @ 10:14 AM

The difference is between Linq To SQL and Linq to Objects.

I love Linq to objects, but for data...oh well!

Bass
www.spreadfirefox.com/5years/

In reply to vesuvius

#Apr 9th @ 10:23 AM

?

Bass
www.spreadfirefox.com/5years/

In reply to Harlequin

#Apr 9th @ 10:22 AM

That's my problem. I have to use Visual Studio 2005 because it's the only way I know to have a project that opens in both in Visual Studio 2005 and Visual Studio 2008 (via the conversion wizard).

vesuvius
Das Glasperlenspiel

In reply to Bass

#Apr 9th @ 10:17 AM

Yes you can, all you do is create a .NET 2.0 application when creating the project - known as multi targeting.

Presently, I am developing an ASP.NET 2.0 application in VS 2008 which I could have done in VS 2005, but the 2008 IDE is a country mile better, and the Expression Web editor is a treat.

Bass
www.spreadfirefox.com/5years/

In reply to vesuvius

#Apr 9th @ 10:27 AM

But can you open the csproj VS2008 generates in VS2005?

vesuvius
Das Glasperlenspiel

In reply to Bass

#Apr 9th @ 10:32 AM

projects yes, but solutions no.

Bass
www.spreadfirefox.com/5years/

In reply to vesuvius

#Apr 9th @ 10:36 AM

Well that is pretty useless to me then. I need Solutions to work in both versions also.

W3bbo
The Master of Baiters

In reply to Bass

#Apr 9th @ 10:39 AM

It's always been that way through, Solution files are neither forwards nor backwards compatible (especially the binary *.suo files that contain SCC and Tasks information). It won't be a problem though since you can just include *.sln files for both VS9 and VS10 in your project. FOSS projects that are buildable on multiple platforms invariably bundle the sln/proj files for GCC, VC8, VC9, and TC. They are just metadata after all.