Now I know why I don't use ASP.NET, Razor, and all that cr*p
-
Xcode with objective c rocks. They improved also the pods import. Not sure what problems you have with it, but overall can't complain at all.
Over all it's not bad. Was more thinking about just the sheer size of its footprint and sluggishness at times. I was also thinking about the issue I ran into below. My code has all been XCode via Swift (not objective-c). But, here's a problem I was _lucky_ enough to stumble into first and I was in the middle of a project and it totally crushed my app and design view. Luckily I reverted the code and was able to finally fix it via editing the design file via text editor (outside of XCode). It ended up being a bug in XCode. ios - Why do internal inconsistencies occur in Main.storyboard and how do I get around it? - Stack Overflow[^]
-
Marc Clifton wrote:
I wrote my own HTTP/S server
Ladies and Gentleman, I present to you: A Developer.
cheers Chris Maunder
Chris Maunder wrote:
I present to you: A Developer.
I resemble that remark! :laugh: 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
-
Chris Maunder wrote:
Have you played with the new ASP.NET Core stuff?
No, but I actually want to. I imagine it's a lot lighter weight, given that IIS doesn't exist (and hopefully never will) on Linux boxes.
Chris Maunder wrote:
What are you currently using?
I wrote my own HTTP/S server from core .NET classes (not "Core" stuff), use a "semantic" multithreading router, and rely heavily on Newtonsoft.Json. The rest is jQuery, Bootstrap, and maybe a wee bit of Knockout (I really have little use for MVVM models, actually, as crazy as that sounds) and lots of Ajax for a nice responsive UI experience, wrapped in some client-side libraries I put together to make life easier (less typing) and my UI poison of choice is jqWidgets (which is actually quite cool.) No Angular. No Backbone. No React. It's amazing how much can get done when you don't add several framework layers between point A (give me the value of this control) to point B (send it to the server.) 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'm amazed at the over engineering MS does... which makes it harder to learn/change/work with in some of it's stacks. I recently completed a project with a simple
HttpListenerfor the web server andVue.jsfor the client side [my first real web project after a lifetime of winforms development]. ps:Vue.jsis awesome, simple and powerful !! -
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.
-
OK, granted, the specs on the computer at work suck: 8GB RAM i5-2500 CPU at 3.30Ghz Probably a 5400 RPM hard drive that's always thrashing. (and I seem to be one of the lucky ones with 8GB RAM!!!) However: 1. 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. 2. If I try to debug, it's about a 60 second wait time, a message frequently pops up that something can't start, it tries to integrate debugging with Chrome (for elephants sake, I'm trying to debug the server-side C# code, not the Javascript, I'll use the console window in Chrome for that, thank you very elephanting much, I don't need or want integrated Javascript client debugging in the IDE) 3. If #2 happens, I have to reset the URL to localhost:[someport] 4. Now remember, I'm running this stuff as localhost, so everything is elaphanting LOCAL. Yet it takes a good 10 seconds to load a "hello world" page. The time delays are what gets me the most. So many elephanting sub-systems seem to be involved. Conversely, the web sites that I write don't use ASP.NET, Razor, or any of that garbage. The server launches instantly, the web pages come up instantly, and I'm a happy camper debugging server side code in the VS and client-side code in Chrome. My experience with Microsoft's high-level technologies for web development makes me X| Sadly, I have to use this pile of stinking dung for a simple project at work. And as I said above, the crap machine they give you here at work is probably in large part responsible for my experience. 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
Errr but if you had better hardware, what would you be developing in then? Notepad++? :confused:
-
OK, granted, the specs on the computer at work suck: 8GB RAM i5-2500 CPU at 3.30Ghz Probably a 5400 RPM hard drive that's always thrashing. (and I seem to be one of the lucky ones with 8GB RAM!!!) However: 1. 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. 2. If I try to debug, it's about a 60 second wait time, a message frequently pops up that something can't start, it tries to integrate debugging with Chrome (for elephants sake, I'm trying to debug the server-side C# code, not the Javascript, I'll use the console window in Chrome for that, thank you very elephanting much, I don't need or want integrated Javascript client debugging in the IDE) 3. If #2 happens, I have to reset the URL to localhost:[someport] 4. Now remember, I'm running this stuff as localhost, so everything is elaphanting LOCAL. Yet it takes a good 10 seconds to load a "hello world" page. The time delays are what gets me the most. So many elephanting sub-systems seem to be involved. Conversely, the web sites that I write don't use ASP.NET, Razor, or any of that garbage. The server launches instantly, the web pages come up instantly, and I'm a happy camper debugging server side code in the VS and client-side code in Chrome. My experience with Microsoft's high-level technologies for web development makes me X| Sadly, I have to use this pile of stinking dung for a simple project at work. And as I said above, the crap machine they give you here at work is probably in large part responsible for my experience. 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
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.
-
OK, granted, the specs on the computer at work suck: 8GB RAM i5-2500 CPU at 3.30Ghz Probably a 5400 RPM hard drive that's always thrashing. (and I seem to be one of the lucky ones with 8GB RAM!!!) However: 1. 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. 2. If I try to debug, it's about a 60 second wait time, a message frequently pops up that something can't start, it tries to integrate debugging with Chrome (for elephants sake, I'm trying to debug the server-side C# code, not the Javascript, I'll use the console window in Chrome for that, thank you very elephanting much, I don't need or want integrated Javascript client debugging in the IDE) 3. If #2 happens, I have to reset the URL to localhost:[someport] 4. Now remember, I'm running this stuff as localhost, so everything is elaphanting LOCAL. Yet it takes a good 10 seconds to load a "hello world" page. The time delays are what gets me the most. So many elephanting sub-systems seem to be involved. Conversely, the web sites that I write don't use ASP.NET, Razor, or any of that garbage. The server launches instantly, the web pages come up instantly, and I'm a happy camper debugging server side code in the VS and client-side code in Chrome. My experience with Microsoft's high-level technologies for web development makes me X| Sadly, I have to use this pile of stinking dung for a simple project at work. And as I said above, the crap machine they give you here at work is probably in large part responsible for my experience. 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
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
-
OK, granted, the specs on the computer at work suck: 8GB RAM i5-2500 CPU at 3.30Ghz Probably a 5400 RPM hard drive that's always thrashing. (and I seem to be one of the lucky ones with 8GB RAM!!!) However: 1. 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. 2. If I try to debug, it's about a 60 second wait time, a message frequently pops up that something can't start, it tries to integrate debugging with Chrome (for elephants sake, I'm trying to debug the server-side C# code, not the Javascript, I'll use the console window in Chrome for that, thank you very elephanting much, I don't need or want integrated Javascript client debugging in the IDE) 3. If #2 happens, I have to reset the URL to localhost:[someport] 4. Now remember, I'm running this stuff as localhost, so everything is elaphanting LOCAL. Yet it takes a good 10 seconds to load a "hello world" page. The time delays are what gets me the most. So many elephanting sub-systems seem to be involved. Conversely, the web sites that I write don't use ASP.NET, Razor, or any of that garbage. The server launches instantly, the web pages come up instantly, and I'm a happy camper debugging server side code in the VS and client-side code in Chrome. My experience with Microsoft's high-level technologies for web development makes me X| Sadly, I have to use this pile of stinking dung for a simple project at work. And as I said above, the crap machine they give you here at work is probably in large part responsible for my experience. 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
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)
-
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 :D I can have 4-5 instances of VS 2013/resharper without a blink running in parallel with a 16GB VM :D Totally worth it :D
-- Log Wizard - a Log Viewer that is easy and fun to use!
-
OK, granted, the specs on the computer at work suck: 8GB RAM i5-2500 CPU at 3.30Ghz Probably a 5400 RPM hard drive that's always thrashing. (and I seem to be one of the lucky ones with 8GB RAM!!!) However: 1. 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. 2. If I try to debug, it's about a 60 second wait time, a message frequently pops up that something can't start, it tries to integrate debugging with Chrome (for elephants sake, I'm trying to debug the server-side C# code, not the Javascript, I'll use the console window in Chrome for that, thank you very elephanting much, I don't need or want integrated Javascript client debugging in the IDE) 3. If #2 happens, I have to reset the URL to localhost:[someport] 4. Now remember, I'm running this stuff as localhost, so everything is elaphanting LOCAL. Yet it takes a good 10 seconds to load a "hello world" page. The time delays are what gets me the most. So many elephanting sub-systems seem to be involved. Conversely, the web sites that I write don't use ASP.NET, Razor, or any of that garbage. The server launches instantly, the web pages come up instantly, and I'm a happy camper debugging server side code in the VS and client-side code in Chrome. My experience with Microsoft's high-level technologies for web development makes me X| Sadly, I have to use this pile of stinking dung for a simple project at work. And as I said above, the crap machine they give you here at work is probably in large part responsible for my experience. 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
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
-
OK, granted, the specs on the computer at work suck: 8GB RAM i5-2500 CPU at 3.30Ghz Probably a 5400 RPM hard drive that's always thrashing. (and I seem to be one of the lucky ones with 8GB RAM!!!) However: 1. 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. 2. If I try to debug, it's about a 60 second wait time, a message frequently pops up that something can't start, it tries to integrate debugging with Chrome (for elephants sake, I'm trying to debug the server-side C# code, not the Javascript, I'll use the console window in Chrome for that, thank you very elephanting much, I don't need or want integrated Javascript client debugging in the IDE) 3. If #2 happens, I have to reset the URL to localhost:[someport] 4. Now remember, I'm running this stuff as localhost, so everything is elaphanting LOCAL. Yet it takes a good 10 seconds to load a "hello world" page. The time delays are what gets me the most. So many elephanting sub-systems seem to be involved. Conversely, the web sites that I write don't use ASP.NET, Razor, or any of that garbage. The server launches instantly, the web pages come up instantly, and I'm a happy camper debugging server side code in the VS and client-side code in Chrome. My experience with Microsoft's high-level technologies for web development makes me X| Sadly, I have to use this pile of stinking dung for a simple project at work. And as I said above, the crap machine they give you here at work is probably in large part responsible for my experience. 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
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.
-
Marc Clifton wrote:
I wrote my own HTTP/S server
Ladies and Gentleman, I present to you: A Developer.
cheers Chris Maunder
No kidding! :cool:
-
Sounds exactly like my box (before I up'ed to SSD - definite improvement and 16G - no noticable change) but even before the up's it was never that slow and never thrashed even when compiling in running in full 'dev mode' (VS13, MySQL server and clients, NotePad++, browser - many tabs, email excel and word all at the same time.)! Disable the bloat services and useless task scheduler entries start with superfetch - it on purposly fills all memory with useless apps: MS says it 'loads the apps you use most' - that's bullshit, after months of use I caught it still loading [ms] apps I never used even once, and not loading a lot I did use every day. Everything got faster without it. It's useless, even without SSD the advantage (even if it worked properly) would be negligable. Absolutely avoid chrome like it has leprosy. Disable stupid crap, like the Adobe Reader update checker. If you trust yourself turn off any anti-virus full-time read/write-to-disk scanning (in fact mine's on-demand only) - just scan anything you download as and when. Unless you must have it SQL Server is a hog. (BTW: Only need Compact Edition for VS to work) Even now with firefox, and a couple of explorer windows and taskman there's only 29 processes in my taskman list - before clean up was closer to 40 and it seemed even moving the mouse would rattle the disk. (Mostly that was the superfetch effect - swapping active apps in and out to save the precious pre-loaded ms crapolapps.) 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.
Sin tack the any key okay
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! ;-)
-
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
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.
-
OK, granted, the specs on the computer at work suck: 8GB RAM i5-2500 CPU at 3.30Ghz Probably a 5400 RPM hard drive that's always thrashing. (and I seem to be one of the lucky ones with 8GB RAM!!!) However: 1. 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. 2. If I try to debug, it's about a 60 second wait time, a message frequently pops up that something can't start, it tries to integrate debugging with Chrome (for elephants sake, I'm trying to debug the server-side C# code, not the Javascript, I'll use the console window in Chrome for that, thank you very elephanting much, I don't need or want integrated Javascript client debugging in the IDE) 3. If #2 happens, I have to reset the URL to localhost:[someport] 4. Now remember, I'm running this stuff as localhost, so everything is elaphanting LOCAL. Yet it takes a good 10 seconds to load a "hello world" page. The time delays are what gets me the most. So many elephanting sub-systems seem to be involved. Conversely, the web sites that I write don't use ASP.NET, Razor, or any of that garbage. The server launches instantly, the web pages come up instantly, and I'm a happy camper debugging server side code in the VS and client-side code in Chrome. My experience with Microsoft's high-level technologies for web development makes me X| Sadly, I have to use this pile of stinking dung for a simple project at work. And as I said above, the crap machine they give you here at work is probably in large part responsible for my experience. 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'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.
-
R. Giskard Reventlov wrote:
though at least I have a 256GB SSD drive which helps
I agree. I think that is probably the most important feature of all in speed with Windows and Visual Studio especially. I just upgraded to an SSD from an HDD at home and the change has been extremely dramatic. Also, at work we all have SSDs and it makes everything far better. A lot of software is I/O killer -- especially VStudio.
I agree as well. Simply replacing the HDD with an SSD on my personal laptop literally made a world of difference. Also, much less expensive than replacing an otherwise very good laptop with a very expensive top of the line laptop.
-
OK, granted, the specs on the computer at work suck: 8GB RAM i5-2500 CPU at 3.30Ghz Probably a 5400 RPM hard drive that's always thrashing. (and I seem to be one of the lucky ones with 8GB RAM!!!) However: 1. 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. 2. If I try to debug, it's about a 60 second wait time, a message frequently pops up that something can't start, it tries to integrate debugging with Chrome (for elephants sake, I'm trying to debug the server-side C# code, not the Javascript, I'll use the console window in Chrome for that, thank you very elephanting much, I don't need or want integrated Javascript client debugging in the IDE) 3. If #2 happens, I have to reset the URL to localhost:[someport] 4. Now remember, I'm running this stuff as localhost, so everything is elaphanting LOCAL. Yet it takes a good 10 seconds to load a "hello world" page. The time delays are what gets me the most. So many elephanting sub-systems seem to be involved. Conversely, the web sites that I write don't use ASP.NET, Razor, or any of that garbage. The server launches instantly, the web pages come up instantly, and I'm a happy camper debugging server side code in the VS and client-side code in Chrome. My experience with Microsoft's high-level technologies for web development makes me X| Sadly, I have to use this pile of stinking dung for a simple project at work. And as I said above, the crap machine they give you here at work is probably in large part responsible for my experience. 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.
-
OK, granted, the specs on the computer at work suck: 8GB RAM i5-2500 CPU at 3.30Ghz Probably a 5400 RPM hard drive that's always thrashing. (and I seem to be one of the lucky ones with 8GB RAM!!!) However: 1. 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. 2. If I try to debug, it's about a 60 second wait time, a message frequently pops up that something can't start, it tries to integrate debugging with Chrome (for elephants sake, I'm trying to debug the server-side C# code, not the Javascript, I'll use the console window in Chrome for that, thank you very elephanting much, I don't need or want integrated Javascript client debugging in the IDE) 3. If #2 happens, I have to reset the URL to localhost:[someport] 4. Now remember, I'm running this stuff as localhost, so everything is elaphanting LOCAL. Yet it takes a good 10 seconds to load a "hello world" page. The time delays are what gets me the most. So many elephanting sub-systems seem to be involved. Conversely, the web sites that I write don't use ASP.NET, Razor, or any of that garbage. The server launches instantly, the web pages come up instantly, and I'm a happy camper debugging server side code in the VS and client-side code in Chrome. My experience with Microsoft's high-level technologies for web development makes me X| Sadly, I have to use this pile of stinking dung for a simple project at work. And as I said above, the crap machine they give you here at work is probably in large part responsible for my experience. 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
-
OK, granted, the specs on the computer at work suck: 8GB RAM i5-2500 CPU at 3.30Ghz Probably a 5400 RPM hard drive that's always thrashing. (and I seem to be one of the lucky ones with 8GB RAM!!!) However: 1. 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. 2. If I try to debug, it's about a 60 second wait time, a message frequently pops up that something can't start, it tries to integrate debugging with Chrome (for elephants sake, I'm trying to debug the server-side C# code, not the Javascript, I'll use the console window in Chrome for that, thank you very elephanting much, I don't need or want integrated Javascript client debugging in the IDE) 3. If #2 happens, I have to reset the URL to localhost:[someport] 4. Now remember, I'm running this stuff as localhost, so everything is elaphanting LOCAL. Yet it takes a good 10 seconds to load a "hello world" page. The time delays are what gets me the most. So many elephanting sub-systems seem to be involved. Conversely, the web sites that I write don't use ASP.NET, Razor, or any of that garbage. The server launches instantly, the web pages come up instantly, and I'm a happy camper debugging server side code in the VS and client-side code in Chrome. My experience with Microsoft's high-level technologies for web development makes me X| Sadly, I have to use this pile of stinking dung for a simple project at work. And as I said above, the crap machine they give you here at work is probably in large part responsible for my experience. 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.
-
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