ATTENTION: You are viewing a page formatted for mobile devices; to view the full web page, click HERE.

Other Software > Developer's Corner

Visual Studio 11 Express to only build Metro apps

<< < (3/7) > >>

Stoic Joker:
Meh... VS 2010 is lots good enough. And actually, VS 2005 was good enough.

And besides, who would actually want to pay for an IDE to write Metro apps? :P-Renegade (May 25, 2012, 04:08 AM)
--- End quote ---

Amen to that (on both points)!

Actually the thing I can't seem to figure out is what's the big deal about VS11 Express leading with Metro only? Granted I've only been using the std/pro editions of VS (for years), but I've gotten away with it by using the latest SDK with whatever VS ver I was using ... Hell I still like to use VS05 for quite a bit.

Do the VS Express editions attempt to prevent you from switching over to an updated SDK??

Renegade:
@Stoic Joker

Don't you think that they totally dropped the ball with dropping support for dynamic help in VS 2010? I liked that. It really made learning new features very easy. That was a total screw up as far as I can see.

wraith808:
It's even larger than that.  The Windows SDK will no longer build .NET apps.

from http://msdn.microsoft.com/en-us/windows/hardware/hh852363.aspx

The Windows SDK no longer ships with a complete command-line build environment. The Windows SDK now requires a compiler and build environment to be installed separately. If you require a complete development environment, including compilers and a build environment, Microsoft Visual Studio 11 Beta is available for download.

--- End quote ---

Though I like VS, I use other products, i.e. SlickEdit that hook into the SDK to build- I've even built apps completely with Notepad++ and the SDK... especially services.  This is shutting them out in the cold to be able to build.

Stoic Joker:
@Stoic Joker

Don't you think that they totally dropped the ball with dropping support for dynamic help in VS 2010? I liked that. It really made learning new features very easy. That was a total screw up as far as I can see.-Renegade (May 25, 2012, 11:34 AM)
--- End quote ---

Um... I never even noticed it was missing. I'd always just been in the habbit of hitting F1 to lookup whatever the cursor was on, and that still seems to work. Also with VS2010 they have the OTF popups that tell you what the function you're working on needs/has available for overloads ... So the whole thing is really kinda paint-by-numbers easy. I've never really worked with the .NET stuff much before, and I just started a complete ground up rewrite to combine several of our disparate internal systems into a single interface. So it's baptism-by-fire for me doing it with 2010.NET ... And its been going suprizingly well. I've even started writing my own utility class for sanitizing user input.

Stoic Joker:
The Windows SDK will no longer build .NET apps.

from http://msdn.microsoft.com/en-us/windows/hardware/hh852363.aspx

The Windows SDK no longer ships with a complete command-line build environment. The Windows SDK now requires a compiler and build environment to be installed separately. If you require a complete development environment, including compilers and a build environment, Microsoft Visual Studio 11 Beta is available for download.

--- End quote ---
-wraith808 (May 25, 2012, 12:55 PM)
--- End quote ---

Hm... Okay, that does suck ... But can you combine the SDK with the Express edition of VS? ...If that is an option then it might not be that bad overall.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version