|
You won't notice a difference with 16GB of RAM until you have 3 instances of Visual Studio, database management software, Outlook, Firefox (with 20 tabs open), Chrome (streaming Pandora and level 2 stock data), and a remote connection to a server all open at the same time. The highest I've gotten my work machine to was nearly 12GB 
if (Object.DividedByZero == true) { Universe.Implode(); }
Meus ratio ex fortis machina. Simplicitatis de formae ac munus. -Foothill, 2016
|
|
|
|
|
Lopatir wrote: I've got an old i3 laptop that outperforms one i7 machine a client provides for me at their office - but then again they loaded it with "speed up" utilities - what a joke those things are.
That's really a hoot - more code to "speed up" a machine. If you've ever written assembly you know that more code never means more speed! 
|
|
|
|
|
Don't debug. Build, refresh page. If something goes wrong, set breakpoint and instead of F5 use one of those VS AttachTo AttachTo-Next - Visual Studio Marketplace extensions for debugging. Makes for a pleasanter experience. Not perfect but better than F5. Debug JS in Chrome dev tools or whatever.
Kevin
|
|
|
|
|
My company forced upgraded me to a lower spec computer than what I had prior... (upgraded meaning Win10 on a slower machine instead of Win7 on a faster one).
Before I gave up the old machine, I managed to discover that the company webpage had it documented as a lower end laptop than what it was, and I had the hardware guy here remove the 'incorrect' components and put them in my downgraded (I mean upgraded) laptop. I think I almost made it out with an equal exchange.
But yah... those load times when working on a project really break up any attempt at work. It is just long enough for my mind to wander and think about something else. So instead of losing 1 minute every time I hit F5... I really lose about 10 
|
|
|
|
|
I never had this problem with VS 2010. Recently, I was forced to upgrade an ASP.Net app (to keep up with report version) and started using VS 2015. My inner loop suddenly got unpleasantly disrupted watching the indeterminate wait cursors. 4GB of memory doesn't go far with VS 2015! 
I'm waiting for the dust to settle with VS 2017. I'm actually past due for new hardware, but this 7.5 y/o rig still handles most of my needs quite well. (OK, the SSD was put in just a year and a half ago...huge difference!) 
"Go forth into the source" - Neal Morse
|
|
|
|
|
Up to VS2012 there wasn't a (big) problem. VS2013 onwards seems to hog resources and take forever to load even a simple web page. This makes the code/test/fix/test cycle painful.
We're philosophical about power outages here. A.C. come, A.C. go.
|
|
|
|
|
I have a 5-year-old Dell XPS 8300 that has an "old" i7/2600. It's always been what us older developers call a "screamer" but after putting a 1TB SSD and 16GB of main into the thing it's REALLY a screamer (running Windows 7). I figure this machine will probably do it for the duration. Visual Studio flies on it.
|
|
|
|
|
Errr but if you had better hardware, what would you be developing in then? Notepad++? 
|
|
|
|
|
Loading all those assemblies, of which you may only use 1%, will certainly take time. Try .net core and only load what you need
You can disable client side debugging in VS2017
This may help a little. For a complete fix you may need to change your computer and employer as well.
|
|
|
|
|
Well it sure isn't Quick, but I've never really experienced anything like what you have there... My guess it's the hardware that is the main culprit.
I have a Core i7-4700MQ at 2.4 GHz, 32GB RAM and a SSD on my work laptop. I guess I'm one of the lucky ones.
Wexelblats algorithm:
Pick two: 1. Good, 2. Fast, 3. Cheap
|
|
|
|
|
Hehe :P
I used to have something like that until a year ago, when I switched to Lenovo Thinkpad P70 (64GB of RAM, insanely fast SSD + 4k monitor). Cost a $ton, but totally worth it 
I can have 4-5 instances of VS 2013/resharper without a blink running in parallel with a 16GB VM
Totally worth it
-- Log Wizard - a Log Viewer that is easy and fun to use!
|
|
|
|
|
At this speed, by the year 3500, if you hit F5, you can just forget about the whole thing, go live and die, and leave the debugging to your children.
Also, I think that Visual Studio processes that people will use must be lauched by their grand-parents when the programmer's parents are still in foetus stage. By the time one can program, 2 generations later, the start pages of all instances will be ready to go.
If you accidently close an instance, be careful... but you still have more probably. But if you need to reboot that pc, oops...
There is no cloud! It's just someone else's pc! (Read it somewhere)
|
|
|
|
|
Marc Clifton wrote: It takes for flipping ever (a good 30 seconds) for Visual Studio to launch the website as it interfaces through IIS and loads a hundred System.Microsoft.sh*t assemblies.
You're lucky. The solution I work with has 63 projects, when I fire up the project, I go for a walk, chat a little with co-workers and usually return after 10 minutes. My entire PC slows down. But I blame this mostly because of my cheap 5400 RPM HD. I wish I could purchase an SSD using my own money.
But in the end, I am glad I use Visual Studio (2015) for this project. A project with this size and complexity would be a lot harder to maintain if not having this many features VS can provide. It saves me a lot of time in the end.
Marc Clifton wrote: If #2 happens
I don't have this problem, I think you may be running into some configuration issue. Just disable client-side debugging, you'll probably start the project faster too.
Marc Clifton wrote: And as I said above, the crap machine they give you here at work is probably in large part responsible for my experience.
Yep
To alcohol! The cause of, and solution to, all of life's problems - Homer Simpson
Our heads are round so our thoughts can change direction - Francis Picabia
|
|
|
|
|
The machine they give you at work is COMPLETELY responsible for your trouble. ASP.Net and its related technologies really are first-class in their capabilities. Of course, I'm still using the 2008 version of all this so maybe they've added some bloat in more recent versions.
|
|
|
|
|
ClockMeister wrote: I'm still using the 2008 version of all this so maybe they've added some bloat in more recent versions.
I remember 2008 was fairly speedy, though I kept getting annoyed at the rendering time of the pages even then because of the template engine.
On the other hand, I'm using the new and shiny VS2017! Haven't tried VS2008, which I think is installed somewhere, but certainly not on the office machine -- my only other option in VS2015.
Marc
Latest Article - Merkle Trees
Learning to code with python is like learning to swim with those little arm floaties. It gives you undeserved confidence and will eventually drown you. - DangerBunny
Artificial intelligence is the only remedy for natural stupidity. - CDP1802
|
|
|
|
|
Hey Marc,
I've got VS2017 in a Windows 10 VM (neither of which I do anything but fiddle with). I do some coding in VS2010 (C# & VB.Net) but for my own stuff I stick with VS2008/Active Reports 6/SQL Server (2008->2014). Most of my work is desktop / back end stuff and a spattering of ASP.Net - I really don't have any reason to upgrade my tools (especially since I pay for them myself). The output from my 2008 released stuff works on everything from XP on up through 10 - I just don't see any point in spending coin for upgrades to something that does the job just fine.
The bottom line here is, basically, "If it ain't broke, why fix it?" 
 Olde Country Programmer (Clockmeister)
|
|
|
|
|
I'm sure you know your setup but it sounds like you need either a reloading of your system or you need to disable some sort of scanning software. I've done so with my stuff (almost exactly the same specs as yours) and I have great load times.
|
|
|
|
|
kristopher.baker wrote: I'm sure you know your setup but it sounds like you need either a reloading of your system or you need to disable some sort of scanning software. I've done so with my stuff (almost exactly the same specs as yours) and I have great load times.
Can't. This is a company computer, and it's loaded with all sorts of BS scanners, admin alert crap, etc. Heck, they're probably watching me remotely without my knowing right now!
Marc
Latest Article - Merkle Trees
Learning to code with python is like learning to swim with those little arm floaties. It gives you undeserved confidence and will eventually drown you. - DangerBunny
Artificial intelligence is the only remedy for natural stupidity. - CDP1802
|
|
|
|
|
Appreciate your need to rant, since we've all been there and it's probably quite cathartic.
Ideally you wouldn't need to have cycles of starting web pages to test your serverside code, it should be covered by a suite of unit tests that can be run without starting up the entire application.
Secondly I confirm what someone else mentioned here about trying more recent versions of ASP.Net / ASP.NET Core since it's designed to compete on performance with open source equivalents - part of this is creating a level playing field by allowing you turn off all the features that you don't want, allowing for a like for like comparison.
We sometimes don't realise how many things you get for free with ASP.Net / IIS... so if you don't want those features, turn them off... and make sure you apply effective testing practices to streamline your development.
|
|
|
|
|
srcard wrote: it should be covered by a suite of unit tests that can be run without starting up the entire application.
Quite true, except that having hardly ever used Razor, I just wanted to verify that the parameters were coming in correctly from the AJAX POST handler. But I totally agree, anything "real" should be unit testing.
srcard wrote: so if you don't want those features, turn them off.
I'll poke around, I certainly don't need much for local build testing -- just serve the darn page!
Marc
Latest Article - Merkle Trees
Learning to code with python is like learning to swim with those little arm floaties. It gives you undeserved confidence and will eventually drown you. - DangerBunny
Artificial intelligence is the only remedy for natural stupidity. - CDP1802
|
|
|
|
|
Use the "built-in" IIS Express server for testing?
[Project | Web | Servers | Express vs local etc]
"(I) am amazed to see myself here rather than there ... now rather than then".
― Blaise Pascal
|
|
|
|
|
Gerry Schmitz wrote: Use the "built-in" IIS Express server for testing?
Hah, I forgot about that. Will give it a try (If it's not doing it already, I think it might be.)
Marc
Latest Article - Merkle Trees
Learning to code with python is like learning to swim with those little arm floaties. It gives you undeserved confidence and will eventually drown you. - DangerBunny
Artificial intelligence is the only remedy for natural stupidity. - CDP1802
|
|
|
|
|
I rarely feel a need to comment but I had to jump in on this one. Please understand, I am not excusing Microsoft and Visual Studio does have some problems and flaws. In this case though, I doubt Visual Studio/Microsoft is the complete problem.
You are correct about some delay, it should be about 1 to 10 seconds and no more, and that is on my development machine. The machine is running 16G ram with a quad core processor at 3.6G. That is my work dev machine. My home dev machine is about half that and is at least 6 years old. My home dev machine has the same delay time. The problem I suspect you are encountering is with where you working directory is located. I used to encounter this problem when the default working directory is set to a location that is, in reality, a networked drive. This is a common habit at most work location as the average use is set so their personal working folders go to a networked drive where it is backed up into the corporate backup. At least in my experience that is common and how most work computers are set. When you do this with Visual Studio, which uses the default Documents folder, for its default working directory you end up compiling all of your resources across a network and through a network drive. I have, and I mean for years, found I get your exact same problems whenever this is the situation. As such, I moved my working directory to the local hard drive and the problems go away.
My standard when I set up a development machine is I move all my development to C:\Development for a folder name. Within that folder I have the year of Visual Studio I am using, i.e. 2012, 2015, 2017 or whatever, than each project in the year. It is easier to organize locally and easier to find everything. If your problem is what I think it is, than it should also eliminate the really slow drag you are seeing and the false starts. Like I said, this is just what I suspect is the problem but it is what I usually run into. I am also not excusing Microsoft. It is a really stupid problem to have and it shouldn't be an issue but it does seem to be. Try moving where the applications are for just one, as a test, and you can see if it is worth changing all of the settings in the option menu.
|
|
|
|
|
VS 2017 is a lot faster - if you're on 2015, I think you can upgrade and still work with projects created in 2015.
|
|
|
|
|
I get the following configured
use a Local IIS, not Express
disable Browser Link
no need to have it running in debug to View the web site
If Server changes (cs, controllers) - then build and will take a few seconds for IIS to re load site
If only client side (cshtml, javascipt, css, html) changes - no need to build. Simply Save file, refresh web page, done.
I use chrome - in dev tool network tab, make sure disable cache is on, else that refresh page might not get the changes.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
