Is it just me, or is VS2017 ... um ... flaky?
-
As in: open VS with a tiny solution I created yesterday in VS2017 - three projects, two "just started", one a VS2013 utility project that has worked for years. Opens fine. Click on .CS file in different assembly and it locks up completely. 27% CPU usage (so that'll be a whole core looping plus some other tasks) ignores minimize, close, any click at all. Repeatable, fails every time. Quick check in PSPad and the .CS is fine - a dozen lines of code or so, nothing complex. Quick check and VS is solidly up date. So, I'll try a repair installation. 6GB download later (fortunately at 5MB/sec) and it's downloaded. Installing. Lets grind to a halt, shall we? Up to 3% now, after only ten minutes ... Is it always like this? VS used to be relatively reliable (as in you could rely on them not to fix the bugs but at least it didn't fall over). I'm so close to saying "sod it" and going back to VS2013 - it just worked!
Sent from my Amstrad PC 1640 Never throw anything away, Griff Bad command or file name. Bad, bad command! Sit! Stay! Staaaay... AntiTwitter: @DalekDave is now a follower!
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt -
As in: open VS with a tiny solution I created yesterday in VS2017 - three projects, two "just started", one a VS2013 utility project that has worked for years. Opens fine. Click on .CS file in different assembly and it locks up completely. 27% CPU usage (so that'll be a whole core looping plus some other tasks) ignores minimize, close, any click at all. Repeatable, fails every time. Quick check in PSPad and the .CS is fine - a dozen lines of code or so, nothing complex. Quick check and VS is solidly up date. So, I'll try a repair installation. 6GB download later (fortunately at 5MB/sec) and it's downloaded. Installing. Lets grind to a halt, shall we? Up to 3% now, after only ten minutes ... Is it always like this? VS used to be relatively reliable (as in you could rely on them not to fix the bugs but at least it didn't fall over). I'm so close to saying "sod it" and going back to VS2013 - it just worked!
Sent from my Amstrad PC 1640 Never throw anything away, Griff Bad command or file name. Bad, bad command! Sit! Stay! Staaaay... AntiTwitter: @DalekDave is now a follower!
Well ... it fixed it, at the cost of throwing away all my settings (indentation, screen layout ...) Annoying though, it's probably too late to get started on much now.
Sent from my Amstrad PC 1640 Never throw anything away, Griff Bad command or file name. Bad, bad command! Sit! Stay! Staaaay... AntiTwitter: @DalekDave is now a follower!
-
As in: open VS with a tiny solution I created yesterday in VS2017 - three projects, two "just started", one a VS2013 utility project that has worked for years. Opens fine. Click on .CS file in different assembly and it locks up completely. 27% CPU usage (so that'll be a whole core looping plus some other tasks) ignores minimize, close, any click at all. Repeatable, fails every time. Quick check in PSPad and the .CS is fine - a dozen lines of code or so, nothing complex. Quick check and VS is solidly up date. So, I'll try a repair installation. 6GB download later (fortunately at 5MB/sec) and it's downloaded. Installing. Lets grind to a halt, shall we? Up to 3% now, after only ten minutes ... Is it always like this? VS used to be relatively reliable (as in you could rely on them not to fix the bugs but at least it didn't fall over). I'm so close to saying "sod it" and going back to VS2013 - it just worked!
Sent from my Amstrad PC 1640 Never throw anything away, Griff Bad command or file name. Bad, bad command! Sit! Stay! Staaaay... AntiTwitter: @DalekDave is now a follower!
"Who's the more toolish? The tool, or the tool who uses it?" -- Obiwan after some gin. VS 2010 continues to rock.
-
Well ... it fixed it, at the cost of throwing away all my settings (indentation, screen layout ...) Annoying though, it's probably too late to get started on much now.
Sent from my Amstrad PC 1640 Never throw anything away, Griff Bad command or file name. Bad, bad command! Sit! Stay! Staaaay... AntiTwitter: @DalekDave is now a follower!
OriginalGriff wrote:
Well ... it fixed it, at the cost of throwing away all my settings (indentation, screen layout ...)
Fortunately these can be exported as separate settings. Over the years I've learned just how important those settings can be. My editor rules get imported on all of my machines, but I keep separate screen layout settings per-computer, as not all of my machines have the same number of monitors/resolution.
-
As in: open VS with a tiny solution I created yesterday in VS2017 - three projects, two "just started", one a VS2013 utility project that has worked for years. Opens fine. Click on .CS file in different assembly and it locks up completely. 27% CPU usage (so that'll be a whole core looping plus some other tasks) ignores minimize, close, any click at all. Repeatable, fails every time. Quick check in PSPad and the .CS is fine - a dozen lines of code or so, nothing complex. Quick check and VS is solidly up date. So, I'll try a repair installation. 6GB download later (fortunately at 5MB/sec) and it's downloaded. Installing. Lets grind to a halt, shall we? Up to 3% now, after only ten minutes ... Is it always like this? VS used to be relatively reliable (as in you could rely on them not to fix the bugs but at least it didn't fall over). I'm so close to saying "sod it" and going back to VS2013 - it just worked!
Sent from my Amstrad PC 1640 Never throw anything away, Griff Bad command or file name. Bad, bad command! Sit! Stay! Staaaay... AntiTwitter: @DalekDave is now a follower!
I dislike VS2015/17 because they induce seizures with all the crap that flashes on/off the screen as you code. I can't f*ckin stand that crap.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013 -
As in: open VS with a tiny solution I created yesterday in VS2017 - three projects, two "just started", one a VS2013 utility project that has worked for years. Opens fine. Click on .CS file in different assembly and it locks up completely. 27% CPU usage (so that'll be a whole core looping plus some other tasks) ignores minimize, close, any click at all. Repeatable, fails every time. Quick check in PSPad and the .CS is fine - a dozen lines of code or so, nothing complex. Quick check and VS is solidly up date. So, I'll try a repair installation. 6GB download later (fortunately at 5MB/sec) and it's downloaded. Installing. Lets grind to a halt, shall we? Up to 3% now, after only ten minutes ... Is it always like this? VS used to be relatively reliable (as in you could rely on them not to fix the bugs but at least it didn't fall over). I'm so close to saying "sod it" and going back to VS2013 - it just worked!
Sent from my Amstrad PC 1640 Never throw anything away, Griff Bad command or file name. Bad, bad command! Sit! Stay! Staaaay... AntiTwitter: @DalekDave is now a follower!
I disable CodeLens and refuse to install Resharper. As a result, my VS2017 runs my 80-project solution like a rocket. (I also use an SSD). /ravi
My new year resolution: 2048 x 1536 Home | Articles | My .NET bits | Freeware ravib(at)ravib(dot)com
-
Well ... it fixed it, at the cost of throwing away all my settings (indentation, screen layout ...) Annoying though, it's probably too late to get started on much now.
Sent from my Amstrad PC 1640 Never throw anything away, Griff Bad command or file name. Bad, bad command! Sit! Stay! Staaaay... AntiTwitter: @DalekDave is now a follower!
-
As in: open VS with a tiny solution I created yesterday in VS2017 - three projects, two "just started", one a VS2013 utility project that has worked for years. Opens fine. Click on .CS file in different assembly and it locks up completely. 27% CPU usage (so that'll be a whole core looping plus some other tasks) ignores minimize, close, any click at all. Repeatable, fails every time. Quick check in PSPad and the .CS is fine - a dozen lines of code or so, nothing complex. Quick check and VS is solidly up date. So, I'll try a repair installation. 6GB download later (fortunately at 5MB/sec) and it's downloaded. Installing. Lets grind to a halt, shall we? Up to 3% now, after only ten minutes ... Is it always like this? VS used to be relatively reliable (as in you could rely on them not to fix the bugs but at least it didn't fall over). I'm so close to saying "sod it" and going back to VS2013 - it just worked!
Sent from my Amstrad PC 1640 Never throw anything away, Griff Bad command or file name. Bad, bad command! Sit! Stay! Staaaay... AntiTwitter: @DalekDave is now a follower!
OriginalGriff wrote:
27% CPU usage (so that'll be a whole core looping plus some other tasks) ignores minimize, close, any click at all.
If you're still using an Amstrad PC 1640, then these things ae bound to happen.
Michael Martin Australia "I controlled my laughter and simple said "No,I am very busy,so I can't write any code for you". The moment they heard this all the smiling face turned into a sad looking face and one of them farted. So I had to leave the place as soon as possible." - Mr.Prakash One Fine Saturday. 24/04/2004
-
I dislike VS2015/17 because they induce seizures with all the crap that flashes on/off the screen as you code. I can't f*ckin stand that crap.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013I once sat through a remote coding session with a coworker of mine, who's using a Mac and leaves some Twitter feed thing running all day. VS is downright whisper quiet, compared to that thing that was constantly trying to get your attention both with visual cues and sounds. I cannot understand how he could work.
-
As in: open VS with a tiny solution I created yesterday in VS2017 - three projects, two "just started", one a VS2013 utility project that has worked for years. Opens fine. Click on .CS file in different assembly and it locks up completely. 27% CPU usage (so that'll be a whole core looping plus some other tasks) ignores minimize, close, any click at all. Repeatable, fails every time. Quick check in PSPad and the .CS is fine - a dozen lines of code or so, nothing complex. Quick check and VS is solidly up date. So, I'll try a repair installation. 6GB download later (fortunately at 5MB/sec) and it's downloaded. Installing. Lets grind to a halt, shall we? Up to 3% now, after only ten minutes ... Is it always like this? VS used to be relatively reliable (as in you could rely on them not to fix the bugs but at least it didn't fall over). I'm so close to saying "sod it" and going back to VS2013 - it just worked!
Sent from my Amstrad PC 1640 Never throw anything away, Griff Bad command or file name. Bad, bad command! Sit! Stay! Staaaay... AntiTwitter: @DalekDave is now a follower!
With Microsoft, it has always been a race between features and introduced bugs. VS 2013 seems to be the last relatively stabile version.
