Posted By: Brian Keller | May 20th @ 9:49 AM | 201,334 Views | 67 Comments
Update: Beta 2 is here! Check out 10-4 Episode 33: Downloading and Installing Visual Studio 2010 Beta 2.

Visual Studio 2010 Beta 1 is here! In this episode of 10-4, Brian Keller takes us through downloading and installing Visual Studio 2010 Team Suite Beta 1 and Visual Studio 2010 Team Foundation Server Beta 1. This time-compressed video will take you through all of the key things you need to know to get up and running quickly with beta 1.

This video references several important URL's. Those URL's, as well as some other handy links for beta 1, are as follows:
- Download instructions for all files in this video
- More information about the Windows Server 2008 VHD
- Beta 1 home on MSDN
- Beta 1 forums
- Visual Studio Connect site (report bugs / suggestions)
- Common TFS 2010 Beta 1 Installation Problems
- Visual Studio 2010 and .NET Framework 4 Training Kit

Special thanks to Charles Sterling, program manager for Visual Studio Team System, for his tireless efforts behind the scenes to help make this video happen.
Rating:
5
1
lostasif
lostasif
Asif Mushtaq

HI ..... Its great ....

Please tell me that can we install Visual Studio 2010 on Windows XP...

Currently the downloads are not available Sad

Mubshir Raza Ali
Mubshir Raza Ali
www.mrmubi.com

Of course you can on XP SP2!


Mubshir | www.mubshir.com


downloads are already available..but they're not on the main pages yet

http://www.microsoft.com/downloads/details.aspx?FamilyID=3296bb4f-d8ba-4cfd-aa95-a424c5913f6b&displaylang=en

swe
swe

I have a dream, that one day installing vstudio will be as simple as installing silverlight, i have a dream...

pkz
pkz

Are VHDs being created so we can download them instead?

al6
al6

Pure disappointment ...

I had hoped to dive into the new C++0x, but it turned out quickly that Visual Studio 2010 has an extremely poor support for this standard. GCC 4.4 under Linux has implemented ALL standard header files, while Visual Studio 2010 does not have a single one... heavily worked Micro$oft!

The actual languages we work in would surely be given the highest priority of all, but apparently it's not the way you are working. The most I see is a performance loss make up with a non-standard parallel library.

Microsoft Communities