|
They could update updater silently when updating VS. I don't care about version of updater but have been annoyed by the stupid slow splash.
|
|
|
|
|
My problem with the updater is the totally unnecessary hash rechecking of every file when updating the distribution which takes forever...
The incremental growing of the distribution I fixed with VS 2017 Offline Installation Folder Cleanup[^]
|
|
|
|
|
so we have windows updating so often, vs updating so often, chrome updating so often (it checks hourly which for mine just makes the devs look bad) but at least once a week ...
What happened to the beta test and only releasing stable versions/updates? Look at the number of problems that have happened
and of course some big head's gonna reply "I've never had problems" - but so many other people have so please shut up.
Best solution: is stay back 1 major version (unless really problematic and no workarounds), gives you a chance to get work done.
It's simple maths: bleeding edge = lower productivity.
It's why kiddie software developers get a bad rap: too busy polishing their tools rather than using them.
(It's one of the reasons why corporations set policy regarding versions and upgrades - because history has proven bleeding edge is one of the worst places that delays / issues are introduced.)
Unless there's some real compelling reason to upgrade: be smart, be serious about work and stay off bleeding edge.
Signature ready for installation. Please Reboot now.
|
|
|
|
|
I'm afraid I can't give a cogent response to that: I have to go and polish my tool before I use it! 
|
|
|
|
|
Still using VS2012 on the personal machine. Must be missing a few GB worth of JavaScript libraries 
Bastard Programmer from Hell 
If you can't read my code, try converting it here[^]
|
|
|
|
|
I find the updates extremely welcome. I've been impressed with VS 2017 (Okay, except for the standard library team punting filesystem.)
|
|
|
|
|
No, they don't update to add comments. They do to add bugs, for all those that have to update Visual Studio after the last version broke. Just to annoy me, they do it.
Once they removed something in the STL (C++), which hit a colleague.
Once they changed something in the Xaml Compiler breaking my workaround around some other Xaml bug (that one is still existant - since VS 2013).
Once they broke MsBuild so bad, breaking our whole deployment chain.
And I only told you VS 15.4 and newer, meaning last three months.
I would never have gotten past 15.3 myself if VS hadn't broken itself while I was on christmas holidays. Came back, couldn't even open a solution anymore.
Damn thing...
|
|
|
|
|
There is literally no need to reinstall, you simply run the updater and off you go.
The flag is there to cover their asses, they are telling you they have fixed a bug and if you ignore the notification they cannot be held accountable for loss of revenue or loss of man hours.
Banshee for windows YAY !!!
http://sourceforge.net/projects/banshee32
|
|
|
|
|
I don't mind the updates.
What annoys the elephant out of me is that the process consumes wifi bandwidth and thrashes to c-drive to the point where the system becomes virtually dead in the water for anything else I want to do. 
Cheers,
Mike Fidler
"I intend to live forever - so far, so good." Steven Wright
"I almost had a psychic girlfriend but she left me before we met." Also Steven Wright
"I'm addicted to placebos. I could quit, but it wouldn't matter." Steven Wright yet again.
|
|
|
|
|
Depends which way you look at it: you can either see it that they're continually releasing fixes for continually buggy releases... or you can see it that they fix bugs which are bound to happen in anything that complex very quickly. For me, it's the latter: I'd rather they fix a bug immediately than let me run buggy software until the fixes are all released at once. I only wish Windows updates worked like that.
|
|
|
|
|
I tend to view pretty much everything in life as double-sided. Very few things are bad with no good, or good with no bad. I just checked. Seems updates to extensions have "always ignore" as an option. The VS update itself doesn't.
Not sure if "always ignore" means never ever again tell me about an update for that extension. What I've found works best for other software products is a combination of "ignore THIS update" (but tell me when another one comes out), and "ignore THIS update for xxx days". The later option is pretty rare. The VS update notifications flag probably makes the later unnecessary.
Those developers who are looking for something to be fixed want an update as soon as possible. Those who are not encountering any problems (because they're probably working in a different coding area) "most likely" just want to know when the next actual feature set is released -- and whether any of the new features apply to what they do. That's pretty much my M.O. unless I'm looking for an excuse to do something other than code, so I run updates.
I think the VS update process "suffers" from VS being so big and all-encompassing. Most developers are unlikely to use maybe even 10% of the total VS product -- and I'm referring to Community edition. With the grander editions, it's probably even less.
Might be nice if Microsoft were able to better figure out whether a given update even matters to a developer, as in, whether the developer even really uses the portion of VS that's impacted. (Hey Cortana, wanna take a shot at that?  )
Trying to only update the pieces a given developer uses is probably too high-risk. I see that as a test nightmare for Microsoft and ultimately bug-prone. Is VS still stable if only Widget-3 and Widget-7 get updated after previously only having updated Widget-5 and Widget-10 but not Widget-1 and Widget-6? However, simply deciding whether a given developer even uses the code being updated but then requiring a full product update if desired doesn't create those problems.
The "friendliest" would be to sort "here's updates we don't think you need" to the bottom of the list in their own group and not add them to the flag count.
|
|
|
|
|
They're taking after Android SDK, which seems to update daily.
|
|
|
|
|
I agree, while I favor a frequent cycle of smaller updates, too much is too much. Once every other month is more than enough and I think will help improve code quality as you then will have more time to test decently before shipping.
|
|
|
|
|
Why do you feel the need to actually install every update? Until and unless there is an actual benefit that outweighs the delay in and risk to your development cycle, it is in fact a bad thing to do. Just because there are a couple of fixes in areas that you didn't use anyway is not a benefit.
GOTOs are a bit like wire coat hangers: they tend to breed in the darkness, such that where there once were few, eventually there are many, and the program's architecture collapses beneath them. (Fran Poretto)
|
|
|
|
|
It would be super awesome if there was a way to script out the action of "check for all updates to VS2017 and download and install any that are found, including for extensions." And then I could just set the script up to run over night each night or something.
M$ better get on that...
|
|
|
|
|
Message Removed
modified 3-Feb-18 15:55pm.
|
|
|
|
|
because it's small and gets the job done. Besides, I keep misplacing my phone, mainly by putting mail on top of it 
So, I need iTunes - 250+MB 
Charlie Gilley
Do not make me angry or I will channel my inner rage panda
"Where liberty dwells, there is my country." B. Franklin, 1783
“They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
modified 11-Feb-18 13:05pm.
|
|
|
|
|
So ... you keep losing track of your phone, so you are going to replace it with something even smaller and easier to lose? O...Kay. 
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
lol, there is a method to my madness.
The nano is just another music device - no bluetooth but it has an old school min-iDIN connector I can use to hook up to a set of portable speakers.
Charlie Gilley
<italic>Stuck in a dysfunctional matrix from which I must escape...
"Where liberty dwells, there is my country." B. Franklin, 1783
“They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
|
|
|
|
|
And at least he can call his phone to get it to ring if he misplaces it.... 
Cheers,
विक्रम
"We have already been through this, I am not going to repeat myself." - fat_boy, in a global warming thread
|
|
|
|
|
I have an iPod Nano generation 2 out in my car, connect to my Alpine sound system which includes iPod controls. The 2GB device stores about 150-175 songs. It does amazingly well despite some of the temperature extremes it's subject to. Below 15°F or above 90°F it occasionally needs a hard reset to reconnect with the sound system.
I still miss my iPod Classic. Its 120GB was just big enough to store my entire music collection for listening at work. It died a while back, so now I'm using my Nexus 7 tablet. Unfortunately its 32GB onboard Flash isn't big enough for all of my music, so I occasionally have to swap things out.
Software Zen: delete this;
|
|
|
|
|
Gary R. Wheeler wrote: I still miss my iPod Classic. Its 120GB was just big enough to store my entire music collection for listening at work. It died a while back, so now I'm using my Nexus 7 tablet. Unfortunately its 32GB onboard Flash isn't big enough for all of my music, so I occasionally have to swap things out.
Fortunately MicroSD cards have caught up nowadays and will be able to handle your 120GB worth of music.
I'm assuming the Nexus 7 has a MicroSD slot...or have they followed into Apple's footsteps?
|
|
|
|
|
dandy72 wrote: I'm assuming the Nexus 7 has a MicroSD slot
Unfortunately no. 
Software Zen: delete this;
|
|
|
|
|
Wow.
That's the dealbreaker that would make me leave the device on the shelf and move on to something else.
That, and the lack of a headphone jack. And non-replaceable battery.
I'm not sure what they'll think of next, but I'm sure they'll outdo themselves.
Meanwhile, I'm still rockin' my Lumia. Y'know, the dead platform, that still gets updates?
|
|
|
|
|
I've been pretty happy with my Nexus 7. It's the generation 2, which came out in 2013. While the battery isn't replaceable, that's not been an issue thus far. I get 2-3 work days of audio play out of it before I need to recharge. It includes a headphone jack, a must for using it in the work environment.
Software Zen: delete this;
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
