Posted By: itprochris | Aug 29th, 2005 @ 4:28 AM
page 1 of 1
Comments: 15 | Views: 4621
itprochris
itprochris
Holiday Avatar made with C9IAC

Will my investment in Visual Studio 2005 be worth it when WIndows Vista comes along? Will the .net framework 2.0 work on vista, or will new tooks become available (and when)?

Thanks

Sven Groot
Sven Groot
My name has 9 letters. Coincidence? I think not...
The .Net Framework 2.0 will not only work on Vista, it's included with it.
itprochris wrote:
Will my investment in Visual Studio 2005 be worth it when WIndows Vista comes along? Will the .net framework 2.0 work on vista, or will new tooks become available (and when)?


Speculation:

There certainly isn't enough time in the schedule for a major version change to the .NET Framework. There's probably not enough time for even a minor version update. Remember that Vista is supposed to RTM about a year after .NET Framework 2.0/VS2005/SQL Server 2005 do. I'd guess that version 2.0, possibly with a service pack, will release with Windows Vista.

The Windows Presentation Framework (formerly "Avalon") and Windows Communication Framework (formerly "Indigo") are both based on .NET 2.0 - the programming interface is through managed code, and some of the implementation is also managed code.

Visual Studio 'Orcas' was originally supposed to accompany Windows Vista, but it might now be later than this, I think. As far as I'm aware the linked document is the latest official word on post-2005 versions of Visual Studio.
All the code you write in 2.0 should work perfectly right without modification under Vista. Other wise there would be no point in .net .
I'm currently using VS 2005 Beta 2 on Windows Vista Beta 1 and it works fine.
when .net framework 2.0 is released will we be able to write apps for it in vs2003 ? prob silly question as i had contemplated upgrading to vs2005 but dont know when i will be able to. Im wondering if .net 2.0 will have full support for vs2003, (sorry newbie programmer here Tongue Out)
I may be wrong, but I'm pretty sure VS 7 only does .NET Framework 1.0,  VS 2003 only does 1.1, and VS 2005 only does 2.0.
I am currently using vs 2005 to develop c# .net 2.0 code on my xp desktop.  The end result resides on a windows server 2003.  I am planning to upgrade my xp to vista rc1 with vs 2005.  Can I continue to support my c# .net 2.0 code base that is running on the windows server 2003?
Although RC1 is pretty stable, I'd strongly advise against using it on a machine you are dependant on.
figuerres
figuerres
???
brussell wrote:
I may be wrong, but I'm pretty sure VS 7 only does .NET Framework 1.0,  VS 2003 only does 1.1, and VS 2005 only does 2.0.



actually there is a tool to help and you just need to target the 1.1 framework.

I am sure there is more to mit than that but it sounds like 05 can build a 1.1 / 1.0 app.

here is a link with more info:

http://www.hanselman.com/blog/BuildingNET11ProjectsUsingVisualStudio2005.aspx
SecretSoftware
SecretSoftware
Code to live, but Live to code.
VS2005 is not compatible with Vista RTM because of the new limited user thing.

Orcas still not stand alone install.
Sven Groot
Sven Groot
My name has 9 letters. Coincidence? I think not...
Nonsense. Despite what the VS team says, 95% of VS2005 works just fine in Vista even with limited rights, and when you find something that doesn't work, you can always elevate.
SecretSoftware
SecretSoftware
Code to live, but Live to code.
Sven Groot wrote:
Nonsense. Despite what the VS team says, 95% of VS2005 works just fine in Vista even with limited rights, and when you find something that doesn't work, you can always elevate.


I like things to work, so I focus on programming. Me not like to be bothered by popups (hey devenv is not compatible).

Imagine debugging a large app. And each time you start debugging it wants you to elevate. This is pain in the you know what.
Hmm I've been debugging large C# and C++ apps for a few weeks now on Vista and have never had a popup request...

In fact I haven't even come across a situation where I needed to elevate.  The VS2005 page list of "incompatabilities" consists mostly of rarely used features, and even then you can just elevate once and never have to think about it again for that session.
Sven Groot
Sven Groot
My name has 9 letters. Coincidence? I think not...
I've been running VS2005 as a limited user on XP (and now Vista) for years. I can count the number of times I've come across something that doesn't work on one hand.
page 1 of 1
Comments: 15 | Views: 4621
Microsoft Communities