We have a pretty big ASP.NET MVC project with a lot of Areas, controllers etc. Everything was fine until I installed the project on my laptop - Windows 8.1, Intel Core i5, 12 GB RAM, 7200 HDD. The project starting time (F5) become extremely slow. I'm waiting for 3-5 minutes until the home page appears in the browser. First I thought that the problem is in my laptop, and I rent a VPS - Windows Server 2012, Intel Xeon 4 core, 14GB Ram, SSD. But the situation is the same - I'm waiting for a while before the first page appears.
What I've tryed:
batch="false" in Web.config (compile optimization was also disabled/enabled)
Disabled Resharper
Disabled IntelliTrace
Disabled MiniProfiler for EF
Disabled Firewall
No anti-virus software
Enabled the concurrent build in the Resharper's God Mode
The RAM disk was also used
dotTrace profiler shows that over 70% of execution time takes the unmanaged code
Debugging symbols caching
The problem has already appeared on PCs of a couple of my collegues. Situation is the same - Windows 8.1, pretty powerful hardware - impossible to work with Visual Studio. Please, if anybody knows where the problem is let us know.
P.S. We use Visual Studio 2013 Update 4, ASP.NET MVC 5, EntityFramework 6.
This works fine for me: Start a 2nd instance of VisualStudio with a minimal Webapp in IIS Express in debug mode and let it still run while working with your 1st Instance VS and do your work!
Related
I am debugging an ASP.NET MVC app from Visual Studio 2013. When I start the debug process from Visual Studio, IIS Express where app is hosted gets stuck (my app is not started). It often happens to me. In this situation, I manually stop IIS Express from the tray icon. Even stopping IIS Express from the tray icon I often need to stop manually the debugging from Visual Studio through the stop button. Once debugging is stopped, If I try to debug again it does not work, well, sometimes works and sometimes not, it is random. I have verified that if I clear all browser history and cookies, it works in most cases except for some time. Also I have observed that Visual Studio 2013 takes a long time to boot IIS Express where my ASP.NET MVC app is hosted. Finally, I have observed that my ASP.NET MVC app hosted in IIS Express sometimes is not being displayed correctly when debugging from Visual Studio, I mean, it is displayed without css styles being applied, it seems like css styles are missed. In this case, if I stop debugging and start it again it works.
So How can I improve or solve these kind of weird issues?
IIS Express gets stuck and css styles sometimes not being applied when
debugging an ASP.NET MVC application from Visual Studio 2013
This is a quite strange issue and l suggest you could try these suggestions
Suggestion
1) delete all caches under C:\Users\Administrator\AppData\Local\Microsoft\VisualStudio\12.0\ComponentModelCache, C:\Users\Administrator\AppData\Local\Temp and C:\Users\Administrator\AppData\Local\Microsoft\WebsiteCache.
2) close VS Instance, delete .vs hidden folder,bin,obj folder under the physcial path of the solution and then reopen your project
3) If you have IntelliTrace, please disable Enable IntelliTrace under Tools-->Options-->IntelliTrace-->General.
4) try another port like 56000 by right-clicking on the project-->Properties-->Web--> project url.
5) disable any third party extensions by Tools-->Extensions and Updates or just use devenv /safemode in developer command prompt for vs2013.
6) try to reinstall IIS on the control panel and if your IIS is not 10.0, I suggest you could download and use it.
In addition, VS2013 is too old and Microsoft does not continue to maintain it. So l suggest you could download and use the latest VS2019. It has more optimization and stronger performance than the previous VS and fixes some remaining issues from previous releases.
I have an MVC 5 app running in Visual Studio 2014 Update 4.
My app is running fine in VS2013. But very often (about 4 out of 5 times) the debugger suddenly detaches from the process.
While the website keeps running, I don't get (of course) any debug information / breakpoints anymore.
Does someone have a solution or a way to troubleshoot this?
I am developing an app for my company using ASP MVC 3.0. It uses Windows Authentication to log the user in, and the User.IsInRole method or the AuthorizeAttribute.
Currently, I am having issues with initial load and response times, but ONLY for users who happen to be running Internet Explorer 8 on Windows 7. These users are experiencing load times of around 20 seconds. All other users have had no issues when running on Internet Explorer 8 on Windows XP and experience load times of less than a second.
I'm fairly certain it is an Internet Explorer 8 issue, as downloading Google Chrome on a Windows 7 PC has instantaneous load times. The most mind boggling part though, is that I am running a Windows 7 PC and have IE 8 and am not running into these issues and have instant loading.
Any help would be greatly appreciated.
Unfortunately, I was unable to figure out what the root cause of this problem was. So, I thought I would at least post the solution that I used to get around it.
Fortunately, we had a second server for hosting. I migrated over to this server and housed it there and it seemed to work fine. More than likely, the problem with the original server could be the way it was set up, installed or some type of firewall issue that we had.
Right now our team's ASP.NET MVC 2.0 web project takes about 4 minutes to do build on debug. We have the following things included on our project:
t4MVC templates
compiling the asp.net mvc's views on all builds
My work pc is a
Intel core 2 duo T7250 # 2.00 Mhz.
Windows 7 32 bit ultimate
4 gb ram
I am also getting the same build times, on my desktop
Intel core 2 Duo E6550 Conroe 2.33GHz
6gb ram
ocz ssd drive
I do not see any difference between my desktop and laptop? I am guessing that it CPU bound? I may need to upgrade my box?
I did set this to false, and the build times went from 3 minutes before now down to 5 seconds.
<MvcBuildViews>false</MvcBuildViews>
I believe the problem is the compiling the asp.net mvc views. I am still need to see why it takes so long?
Have you tried building the project with msbuild instead of from visual studio? this may give you a clue where the bottlenecks are.
See also:
How to troubleshoot long builds in Visual Studio?
Very long build time in Visual Studio.
I had tried all of the options given too me. I upgrade my machine # home and can build under 15 seconds with true. I am guessing that it is a CPU bound problem.
I'm running Visual Studio 2008 Professional SP1 on Windows 7 Ultimate x64 RTM. I'm using the ASP.NET MVC that you get from the Web Platform Installer.
When I step through my program and pause on any line for longer than a few seconds the debugger suddenly stops and the following message is printed in the Debug Output:
The program '[4232] WebDev.WebServer.EXE: Managed' has exited with code 0 (0x0).
It does not happen 100% of the time, but it's often enough to be extremely frustrating. This behavior happened in the W7 RC releases as well but never under Windows XP Pro x86.
Hard to say what's going on, but if this were happening to me the first thing I would do is click on Debug-> Exceptions, and go make sure all the possible culprits are checked off under Managed Debug Assistants and Common Language Runtime Exceptions.
IIS has a ping timeout to the process that host your site. I think the default is 90 seconds.
While in IIS, right click on the application pool that is running your application and select "Advanced Settings...". Scroll down to "Ping Maximum Response Time" and change it to a greater value. On my development machine, I use 600 which is 10 minutes.