Ok thanks for all the info. I didn't notice any de-activations or nag messages, so I'll continue using it as is :)
Jun 21, 2015 at 2:06 PM
And that is what happens when you release one console with a x86 architecture, then switch to one based on a PowerPC architecture, and then back to a x86-64 architecture. You basically throw easy-ish backwards compatibility out the window between three consecutive consoles with stupid decisions like that.
Jun 15, 2015 at 6:55 AM
Hmm, so far I don't need any of those features mentioned (Office, SharePoint, server software etc), so I should be ok. I guess if I do find something I rely on but no longer have access to, I can always make the case that I need a higher subscription.
Jun 13, 2015 at 8:35 AM
The renewal price for Ultimate is $2,569, and the renewal price for Pro is $799. So the difference is only $1,770. My previous subscriptions seem to run for 3 years so I assume that price is also for 3 years. Maybe as a big company they can even get volume discounts on top of that, not sure.
So I don't think that's a lot to ask for considering it is dwarfed by the total cost of employing a developer for the same time period.
Jun 12, 2015 at 9:43 AM
I don't use any of those so I should be ok there.
Well, right now almost all of my dev work is targeted towards Linux, so I don't have a valid reason to demand anything fancy on the Windows side. However, unlike the other devs around here, I built up an extensive managed test framework for testing my code in a cross-platform way. So I depend heavily on VS even for my Linux dev work. For instance I can do complicated API performance testing with the main test app running on Windows, and a small remote component that runs on Linux.
TBH, I guess I should be happy it got renewed at all :P
Jun 12, 2015 at 8:15 AM
So my company just renewed my MSDN subscription from VS Ultimate with MSDN to VS Professional with MSDN.
I went through the feature matrix and from what I can tell, it doesn't look like I'll lose anything that I depend on. The main thing I'll lose is CodeLens, which I've used a few times but didn't find too useful. I'm not really using IntelliTrace, so that shouldn't be a problem either.
From what I can tell, I won't lose these things I do depend on:
- Profiler for both C# and C/C++ code (mostly sampling)
- Ability to create VS plugins
- Unit testing
Did I miss anything?
BTW, how does this work? Will I be forced to uninstall VS Ultimate and have to re-install VS Professional, or does it just downgrade itself in place (disable some features)?
I guess the good news is that it will probably load faster and use less resources :S
@BitFlipper: And soon there will be first-class support for C++ GDB debugging built into VS2015: http://blogs.msdn.com/b/vcblog/archive/2015/04/29/debug-c-code-on-linux-from-visual-studio.aspx
Thanks for the info, I'll need to keep an eye on that. VGDB works OK but first class support will always be better.
Sorry for the negative tone, but seriously...
Why are we discussing UI design 101 wrt a mature OS like Windows? Anyone with even a passing familiarity with UI design could have told you that taking away borders in a windowed environment was not going to end well. At least adding drop shadows back to all windows alleviated the problem somewhat.
However we see drop shadows becoming ineffective on dark backgrounds. What happens if the windows themselves have dark backgrounds? Let's say I have a few overlapping windows which happen to have dark backgrounds (there are apps like that). Now let's say I want to resize one of them by dragging the edge. But now it becomes more difficult since I need to guess where the edge runs. Not to mention having the windows blend together in the first place.
The right thing MS should have done is to leave the tried and true UI design in place when working in a windowed environment, and when the app runs in fullscreen like on a phone or tablet, then have minimal chrome. We already have the ability to let the OS render the chrome, so the app is already portable between different environments. How does such a design exclude a write-once-run-anywhere goal?
And this keep-trying-different-things-until-something-kinda-works shows how misguided this whole thing has been.