Visual Studio 2013 update WTFs
-
I was updating various components for Visual Studio 2013 today 'cause I got tired of VS periodically bugging me about updating components (I felt I had to spell this out due to pedantry).
The WTFs I ran into were:
- Most components require you to download an external executable instead of using the integrated updater.
- The one component that DID use the integrated updater required me to relaunch Visual Studio as Administrator instead of opening a new elevated thread with a UAC prompt.
- Windows Phone 8.1 Emulator...
OK, #3 on that list requires it own section.
After installing all the other updates, Windows Phone 8.1 Emulator is the only one left to install:
As you can see, I'm running version 1.0 while the latest version is 8.1.0.0. OK, that's a bit weird.So, I download the installer for it, run the installer and get this gem:
So, apparently Visual Studio 2013 comes with a Windows Phone 8.1 emulator that runs on Windows 7 64-bit, but the updated version only runs on Windows 8.1?Why are you even offering me an "upgrade" I can't install?
Edit: After reading other peoples comments, it turns out the Windows Phone 8.1 emulator installed by Visual Studio 2013's installer isn't even compatible with Windows 7. Why did the installer install it then?
-
Been there, cursed that
-
Arguably you need this a lot more on Windows 7 than Windows 8 in the first place...
-
So, apparently Visual Studio 2013 comes with a Windows Phone 8.1 emulator that runs on Windows 7 64-bit,
Does it really? I mean, have you tried it? Just curious.
-
Does it really?
No it doesn't. No WP8 emulator will run on Win7; they all require Win8.I may be remembering wrong, but I'm fairly sure I'm not.
-
Does it really? I mean, have you tried it? Just curious.
Nope, never had the need to to try it.
-
No it doesn't. No WP8 emulator will run on Win7; they all require Win8.
I may be remembering wrong, but I'm fairly sure I'm not.
I guess the WTF would be the Visual Studio 2013 installer installing something I can't use in the first place.
-
No you are correct. The reason it requires Win 8.1 is that it requires Hyper-V to be installed which isn't a feature of 7.
@powerlord maybe worth reporting this to MS.
-
I felt I had to spell this out due to pedantry.
And yet, like some kind of moron, you still spelled pendantry wrong.
-
Just wait till you look at some of the "start" shortcuts. It installs ones for 2012 command line tools (which don't exist, until you happened to do a side-by-side with 2012). And all the 2013 ones? Not there. The installer totally screwed up on creating the Tools folder.
The thing that really annoying about that damn update window - there's no way to say 'don't show me again'. Basically, it wants you on 8.1 (with virtual mode enabled in the bios) and a full install. (I don't do web dev - I don't want ISS. Fuck you!)
-
The reason it requires Win 8.1 is that it requires Hyper-V to be installed which isn't a feature of 7.
Yeah, and when it installs it does not tell you (although I should have known) that it would fuck up anything else using virtualization on your system. VMWare Workstation has not worked properly since that install and I CBA to fix it. I just want Win10 so I can leave that crap behind me...
-
Not there. The installer totally screwed up on creating the Tools folder.
I have one of those, although it seems to just link to--as you say--the '12 tools. And since Start doesn't seem to support nested folders, it just opens an Explorer folder on the desktop.
-
Just wait till you look at some of the "start" shortcuts. It installs ones for 2012 command line tools (which don't exist, until you happened to do a side-by-side with 2012). And all the 2013 ones? Not there. The installer totally screwed up on creating the Tools folder.
The 2013 ones are there on mine, but it didn't add them as shortcuts (instead the Tools folder is a shortcut, whoops)... of course, I didn't install it until after Update 3 was out and used the combined installer.
But yes, it did create the 2012 command-lines tools under Microsoft Visual Studio 2012 as well despite me only have 2008 and 2010 installed at work.
Makes me think I should install it at home and see what it does (I only have 2010 at home).
-
If you are just installing updates and not bothering to check that they work properly when it is on a work machine, well that is your cockup ... if it is a home machine and it is new software well ... you should expect things could go wrong and it is experimentation ... it isn't like VMs are difficult to run these days.
It is hardly surprising that a version of VS where most devs (and the software platform it is targeting) use it on Windows 8+ doesn't have as many bugs reported on an older OS like Windows 7.
learnt the hard way by killing my work machine, when "trying out VS 2012 beta".
-
Start supports nested folders, its just that Tools itself is a shortcut instead of a folder.
-
Start supports nested folders,
What's it look like, though? I don't have anything installed that does that.
-
well that is your cockup
Yeah, I said as much:
(although I should have known)
I did not expect a mistake like that to be terminal though... Seriously, VMWare Workstation runs like shit now.
-
When I switched to VS 2013 Community, I decided to do it the clean way - Removed VS2010 completely first. I faff around with XNA a lot, and everything I could find on forcing XNA into 2013 required the updated WP8 Emulator, which I apparently couldn't install because Windows 7. In the end I had to reinstall VS2010, install XNA, copy XNA into VS2013 and change some numbers, then uninstall VS2010 again to get it working.
(I could just stop using XNA, but fuck that)
-
It just keeps expanding to the right. Think Reddit comments.
-
Sorry for sounding harsh had a few beers and end up sounding a lot more terse.
I installed one of the beta releases on my work machine and was bitten by the "it is kinda .net 4.0, but isn't" and after that it really isn't worth risking bricking your machine.
-
I installed one of the beta releases on my work machine and was bitten by the "it is kinda .net 4.0, but isn't" and after that it really isn't worth risking bricking your machine.
Man, that's a fucked up OS where installing an IDE can fuck everything up.
-
I installed one of the beta releases on my work machine and was bitten by the "it is kinda .net 4.0, but isn't" and after that it really isn't worth risking bricking your machine.
To be honest, the only reason I'm installing 2013 anywhere is because a C++ project I sometimes need to build (from the command line) needs C++11 support... which didn't exist in VS until 2013.
-
This is what it looks like in the Start Menu for VS2010:
Also, before someone ask, I have no idea why corporate pushed QuickTime out to all machines yesterday.
-
(WINDOWS 8) START. NOT START MENU.
Do you even read?
Filed under:We need a "missed the point entirely" badge.
-
No WP8 emulator will run on Win7; they all require Win8.
More specifically the VS2012 one requires Win8 and the VS2013 one requires Win8.1.
That's big part of a reason we are still using VS2012. We have this Jenkins slave running Win8 for building our WP8 target. Since people sometimes need to log in there and test something out (especially since most of us still have Win7 or workstations), it uses a hack (and so do all our Win7 build computers) that allows multiple people being logged in at the same time via RDP (so we don't have to fiddle with server version). When it offered upgrade to Win8.1, that hack was not available for them and since then (might be a year already) we just didn't bother checking again.
C++11 support... which didn't exist in VS until 2013
It does exist in 2012 already. At least most of it.
-
Sorry for sounding harsh had a few beers and end up sounding a lot more terse.
I am seeing a pattern here. You are kind of a dick when you drink, eh?
No judgment, I am the same way. :)
-
(WINDOWS 8) START. NOT START MENU.
Do you even read? <hr/>I do read. Windows 8 wasn't mentioned anywhere in this reply chain until you just mentioned it.
-
This is what it looks like in the Start Menu for VS2010:
I know what the start menu looks like with nested folders. I was talking about the screen, since it sounded like whoever was saying you can have them.
-
-
We have this Jenkins slave running Win8 for building our WP8 target.
Ah, so you guys are TWRTF what with not using a server OS.
Also fuck you discotoaster.
-
I do read. Windows 8 wasn't mentioned anywhere in this reply chain until you just mentioned it.
Actually, it had been repeatedly mentioned, plus we were talking about it in at least on other thread, plus the menu's supported nested folders probably since WIn95, so that should have been unremarkable enough I buttumed you knew I was asking about 8.
-
Windows 8 wasn't mentioned anywhere in this reply chain until you just mentioned it.
Not only is Win8 mentioned in the OP, it's also here
@Yamikuronue said:Arguably you need this a lot more on Windows 7 than Windows 8 in the first place...
and here
@RaceProUK said:No WP8 emulator will run on Win7; they all require Win8.
and here
@lucas said:No you are correct. The reason it requires Win 8.1 is that it requires Hyper-V to be installed which isn't a feature of 7.
and here
@dcon said:Basically, it wants you on 8.1
and here
@lucas said:It is hardly surprising that a version of VS where most devs (and the software platform it is targeting) use it on Windows 8+ doesn't have as many bugs reported on an older OS like Windows 7.
and here, twice
@Bulb said:More specifically the VS2012 one requires Win8 and the VS2013 one requires Win8.1.
and you even quoted one of them
For some reason, this post isn't linked to the correct one... @discoursebot
-
And yet, like some kind of moron, you still spelled pendantry wrong.
Surely that's "moran".
-
@RaceProUK - Days Since Last Discourse Bug: -1
-
Surely that's "moran".
Since I was going for a joke, and not actually complaining about his spelling, I didn't see the need to insert my own mistake.
-
Very discoursistent of you.
-
When I reply to a post, I use the reply chain for context, not unrelated posts in the same thread.
That's why posts that are replies have that reply icon, so you can check it for context. And then up the up arrow for further context since it only includes the last 3 posts for the reply chain.
-
This post is deleted!
-
Erm... weren't you meant to reply to @Polygeekery?
-
I don't even think that reply would make sense in comparison to something I have said?
Maybe DiscoEmail shit itself?
-
Glancing back over this thread, I have no clue who he was replying to...
-
No @boomzilla, disco mail must be fucked. Will correct it when I get back onto a proper computer.
-
I'll take your word for it. I have all email turned off here.
-
Not only is Win8 mentioned in the OP, it's also here
Listing all the places Win8 was already mentioned is a bit above and beyond the call, bro.
-
Lets try again.
The reason why the installation killed development environment was that our project heavily relied on Structure map to expose non-public members via reflection. Installing VS2012 installs 4.5 as part of the installation. The private methods had changed between .NET 4.0 and 4.5 beta, 4.5 identifies itself as v4.0 so structureMap was trying to call a private method that wasn't there.
The TRWTF was structureMap.
-
Oh. I thought it was more like @Polygeekery borking VmWare. I can't cry too many tears for people who use reflection to call private methods that they shouldn't. Given that, I'm sure that project was full of WTF.
-
I updated MSVC2013 to update 4 today.
It installed 2 GBs - almost all stuff I couldn't even dread to need - all of which were 100% required with no way to even change the installation directory from my C:/ SSD.
Thanks, Microsoft.
-
VMWare Workstation has not worked properly since that install and I CBA to fix it. I just want Win10 so I can leave that crap behind me...
Doubt it'll help - the way Hyper-V works, it's utterly incompatible with any other virtualizer.
@created_just_to_disl said:It installed 2 GBs - almost all stuff I couldn't even dread to need - all of which were 100% required with no way to even change the installation directory from my C:/ SSD.
I bought myself a 1TB SSD for New Year's. No more worrying about what goes onC:W:.
-
Doubt it'll help - the way Hyper-V works, it's utterly incompatible with any other virtualizer.
I uninstalled Hyper-V and it still runs like shit. Next time around, I just won't install Hyper-V. It is rubbish in comparison.
-
@created_just_to_disl said:
It installed 2 GBs
But how much of that was new stuff compared to updates? Probably not anywhere near as much as you think...