VS 2010 version

Dec 17, 2012 at 8:31 PM

Is the August RTM on the downloads page the final version 4 for VS 2010?

Coordinator
Dec 17, 2012 at 8:50 PM

For right now yes but I am working on releasing a unified version valid for VS10 and VS12 both.

Cheers
Laurent 

Dec 17, 2012 at 9:00 PM

 

Ah, very good, I'm in no hurry. Thanks!

Coordinator
Dec 17, 2012 at 9:04 PM

Nice :) Just curious, what framework are you planning to work with? (Silverlight, WPF, Windows Phone?) and which version of these frameworks?

Any reason not to move to VS12?

I definitely plan to support VS10 longer, just trying to get a feeling of the reasons to stay on VS10 (and "it's too expensive to change" is a damn good reason FWIW ;)

Cheers
Laurent 

Dec 17, 2012 at 9:54 PM

Working with WPF. I've done the classic C -> C++ -> VB -> Winforms -> WPF journey for the last two decades, and having invested quite a bit of effort in learning WPF, I am not happy with Microsoft just abandoning it. I believe they will have to come back to it because corporate America is not going to jump on the Windows 8 bandwagon. I'm seeing a lot of companies in my neck of the woods (think oil and gas) that need rich desktop visualization, they are adopting WPF, and like me, they must be unhappy with MS.

Of course, I know I can do WPF 4.0 in VS 2012, but what's the point? The ALL CAPS menus and the monochrome icons that make me squint - just seems like change for the sake of change. 

I won't be surprised to see Bill Gates come out of retirement in 2013.

Well, you asked...ha ha.

Keep up the great work no MVVM Light!

Jim

Coordinator
Dec 18, 2012 at 8:26 PM

Hi,

Thanks for the details. Not sure why you have the impression that Microsoft is abandoning WPF, it is definitely not the case. WPF is and remains the best technology to build desktop applications. WinRT apps are not a replacement for WPF apps, rather a companion (very similar to a Windows Phone app, in fact). WPF is not going anywhere. We still do a lot of WPF work, for example with Kinect (often hybrid apps with some C++ components), or of course for LOB apps.

VS12 is worth a try if you want my opinion, it is faster than VS10, and quite a few features were improved. I moved all my development to VS12 now and am quite happy about it. The new design is just a matter of habit I think, I don't really notice it anymore. 

Anyway, thanks for explaining :)

Cheers
Laurent 

Jan 24, 2013 at 8:39 AM

With regards to the reason for sticking with VS2010 for us it's project continuity. I've moved to 2012 for new projects, but old ones need to be maintained in the IDE they were started in for customer interoperability. This means I need to run VS2010 and VS2012 concurrently, which is causing me some issues with MVVMLight atm.

Any idea how far off the unified version is?

Mar 7, 2013 at 8:22 PM
How is the dual Vs 2010 and Vs 2012 version going?

For me I rather just go to Vs 2012 but Microsoft made sure to make it as hard as possible for me to achieve this. I just got a windows 7 phone and have no desire to program on for windows 8 phones at this time simply because I am making applications and not games and I don't think my projects at this time will gain too much from the improvements windows 8 made and when I factor in the how many devices are actually out there I rather go after the entire market share then only those who have windows 8 phones.

Of course this would not be a problem if I could install Windows Phone SDK and have it work in Visual Studios 2012 but since I am using Windows 7 at work I can't because I can't install windows 8 sdk what has windows 7 sdk in it.

I am not sure how this is going to work if I install MVVM light 4 RT and make a project and then go home where I have a windows 8 machine what would have 4.1 installed...not sure what will happen.