main
Report a problem

Microsoft shows off new developer tools

Tom Warren   on 29 September 2008 - 22:41 · 22 comments & 7295 views

Advertisement (Why?)
Microsoft is offering the first look at the company's latest .Net and Visual Studio releases.

The company has announced the newest versions of both developer tools, known as .Net Framework 4.0 and Visual Studio 2010. No official release dates for either product were given.

Team working will be the main focus for Visual Studio 2010. Microsoft plans to upgrade the collaboration and testing tools for the development suite, along with introducing a new modeling tool that is designed to allow non-technical users to model and understand the way in which a new application may function.

"With Visual Studio 2010 and the .NET Framework 4.0, we are focused on the core pillars of developer experience, support for the latest platforms spanning client, server, services and devices, targeted experiences for specific application types, and core architecture improvements," said Soma Somasegar, senior vice president of Microsoft's developer division.

View: Vnunet

Post a comment · Send to friend Comments · There are 22 additional comments
#1 Xilo on 29 Sep 2008 - 22:43
I had some developer from Microsoft that actually works on Visual Studio and .Net come to one of my classes and gave a demo of this new Visual Studio and .Net Framework last week I think it was.

I was pretty excited about some of the stuff he was showing off.
#2 IceBreakerG on 29 Sep 2008 - 22:57
I just started working in Visual Studio 2008 and SQL Server Management Studio 2008 on my current project at work, and so far I like the new stuff. I'd be really interested to see some of the improvements they make in Visual Studio 2010 even though it's about 2yrs away.
(1 reply) #3 Skynetfuture on 29 Sep 2008 - 23:23
.NET 4.0

i bet it will be in Win7ows along with DX11 , IE8 ....etc
#3.1 Cpugeni Ω on 30 Sep 2008 - 08:54
IE8 in 2010? I dont think so, it's more likely to be IE9....
#4 Sam Symons Live on 29 Sep 2008 - 23:29
Sweet 2010 will be when I'm in my last year of Uni so I'll actually be able to use this stuff.
(7 replies) #5 cJr. on 30 Sep 2008 - 00:46
I hope Visual Studio 2010 has a new user interface. I think they may be able to take advantage of the ribbon & implement that
#5.1 Xilo on 30 Sep 2008 - 01:00
(cJr. said @ #5)
I hope Visual Studio 2010 has a new user interface. I think they may be able to take advantage of the ribbon & implement that

From what I know, MS is planning to ditch the Win32 api (at least for the editor portion) and going with something else using one of their new graphic api's I think. So, the editor will be graphics accelerated. Not sure what else they have planned.
#5.2 GreyWolfSC on 30 Sep 2008 - 01:30
(Xilo said @ #5.1)
(cJr. said @ #5)
I hope Visual Studio 2010 has a new user interface. I think they may be able to take advantage of the ribbon & implement that

From what I know, MS is planning to ditch the Win32 api (at least for the editor portion) and going with something else using one of their new graphic api's I think. So, the editor will be graphics accelerated. Not sure what else they have planned.


Sounds like maybe WPF... that could be nifty...
#5.3 MioTheGreat on 30 Sep 2008 - 02:03
(Xilo said @ #5.1)
(cJr. said @ #5)
I hope Visual Studio 2010 has a new user interface. I think they may be able to take advantage of the ribbon & implement that

From what I know, MS is planning to ditch the Win32 api (at least for the editor portion) and going with something else using one of their new graphic api's I think. So, the editor will be graphics accelerated. Not sure what else they have planned.


I very much doubt they'd ever drop the winforms designer. They'll likely be seriously improving ( It needs it! ) the WPF designer, though.
#5.4 Xilo on 30 Sep 2008 - 02:41
(GreyWolfSC said @ #5.2)
(Xilo said @ #5.1)
(cJr. said @ #5)
I hope Visual Studio 2010 has a new user interface. I think they may be able to take advantage of the ribbon & implement that

From what I know, MS is planning to ditch the Win32 api (at least for the editor portion) and going with something else using one of their new graphic api's I think. So, the editor will be graphics accelerated. Not sure what else they have planned.


Sounds like maybe WPF... that could be nifty...

Yes, that's it. I had forgotten the name. At least, I think that was what he said. It would be graphics accelerated though to provide better performance.

Last edited by Xilo on 30 Sep 2008 - 03:17
#5.5 PsykX on 30 Sep 2008 - 03:25
I totally agree. The Ribbon is a winning interface for every complicated app, and even for the simplest.
These small 16x16 icons are impossible to see on high definition resolutions, while the Ribbon interface makes it a lot more clear.
I can't wait to see that... even if in 3-4 months I'll stop doing VB because it's just for school and what I want to program in fact is stuff in XCode, I mean sometimes it's nice to see what the neighbours have to offer and compare
#5.6 Magallanes on 30 Sep 2008 - 13:17
(PsykX said @ #5.5)
I totally agree. The Ribbon is a winning interface for every complicated app, and even for the simplest.
These small 16x16 icons are impossible to see on high definition resolutions, while the Ribbon interface makes it a lot more clear.
I can't wait to see that... even if in 3-4 months I'll stop doing VB because it's just for school and what I want to program in fact is stuff in XCode, I mean sometimes it's nice to see what the neighbours have to offer and compare


I dislike the annoying ribbon bar. I usually work with macro, in excel 2003 i can access and create a new macro using :menu->tools->macros->macros but in excel 2007 i still can find how to add a single macro!.
#5.7 _dandy_ on 02 Oct 2008 - 22:16
(PsykX said @ #5.5)
I totally agree. The Ribbon is a winning interface for every complicated app, and even for the simplest.
These small 16x16 icons are impossible to see on high definition resolutions, while the Ribbon interface makes it a lot more clear.
I can't wait to see that... even if in 3-4 months I'll stop doing VB because it's just for school and what I want to program in fact is stuff in XCode, I mean sometimes it's nice to see what the neighbours have to offer and compare


No offense, but you can't possibly be doing any heavy development and ask to get rid of 16x16 icons in favor of the ribbon interface.

I have 4 monitors hooked up to my dev box, 3 of which are running at 1920x1200, and VS needs to display a lot of information at once to maximize efficiency. Still with that setup, every portion of my desktop is covered in various windows. I'm fine with the old-fashioned toolbar paradigm and I'll be majorly ****ed if they go for the space-wasting ribbon whose sole purpose, ultimately, is to duplicate menus (which are a lot more space-efficient). If I need a seldom-used function, I'll dig it out of the menu, thank you very much. Don't waste space drawing pretty translucid animated buttons and what-not in a development environment.

Last edited by _dandy_ on 04 Oct 2008 - 17:22
(1 reply) #6 zape on 30 Sep 2008 - 01:14
What happen to Visual Studio 2009?
#6.1 Emon on 30 Sep 2008 - 01:18
(zape said @ #6)
What happen to Visual Studio 2009?


Well .. the last Visual Studio release before Visual Studio 2008 was Visual Studio 2005. So by your logic we should ask "what happened to Visual Studio 2006/2007?" .. right?

It is kind of pointless to release an IDE every year, don't you think so?
#7 wrack on 30 Sep 2008 - 02:44
I want the Compact Framwork to catch up to it's big brother in functionality!
(1 reply) #8 Cpugeni Ω on 30 Sep 2008 - 09:00
More information and a few screenshots here: http://msdn.microsoft.com/en-us/vstudio/pr...s/cc948977.aspx

There is also video discussing this on MSDN Channel 9 @ http://channel9.msdn.com/posts/Dan/Norman-...am-System-2010/

Apparently they cannot decide how to pronounce it - two thousand and ten, or twenty ten.
Personally, as Mike Taulty says, it should be Visual Studio 10, which makes sense since the current 2008 IDE is Version 9, so 10 will go nicely with the version number and the year of release
#8.1 +Echilon on 30 Sep 2008 - 18:02
It's twenty ten, not twothousandandten. 1920 was nineteen twenty, not nineteen hundred and twenty.
(3 replies) #9 Magallanes on 30 Sep 2008 - 13:23
We don't need another stuff with new api (self called as framework), we need to microsoft fix the current api but instead microsoft has changed the rules every 2/3 years. Of course you also are forced to re-write all your "old" code and to renew your certification.

Microsoft is evil to the root.
#9.1 IceBreakerG on 30 Sep 2008 - 13:34
Umm, last time I checked, the only time you needed to rewrite all of your code was when they went from .NET 1.1 to .NET 2.0, and there were major changes and improvements with that. .NET 3.0 is an extension to .NET 2.0 and .NET 3.5 is an extension to .NET 3.0, so where in the last 3 releases would you need a complete rewrite?
#9.2 RealFduch on 30 Sep 2008 - 18:55
(Magallanes said @ #9)
We don't need another stuff with new api (self called as framework), we need to microsoft fix the current api but instead microsoft has changed the rules every 2/3 years. Of course you also are forced to re-write all your "old" code and to renew your certification.

Microsoft is evil to the root.

I guess the problem with you is that you know nothing Simple and true.
#9.3 MioTheGreat on 30 Sep 2008 - 22:16
(IceBreakerG said @ #9.1)
Umm, last time I checked, the only time you needed to rewrite all of your code was when they went from .NET 1.1 to .NET 2.0, and there were major changes and improvements with that. .NET 3.0 is an extension to .NET 2.0 and .NET 3.5 is an extension to .NET 3.0, so where in the last 3 releases would you need a complete rewrite?


You didn't even have to 'rewrite' everything. Most of the time, old code would 'just work', or have to be tweaked a little to go from 1.1 to 2.0. You'd get a ton of Obsolete warnings, but it still worked.

Commenting has either been disabled on this article or you are not logged in. Click here to login or register, its free!

Note: Anonymous commenting is disabled in order to keep the quality of responses to a high standard.

Advertisement (Why?)