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.
Related
how start smartstore.net in visual studio localhost without any error
i download github code and open project file from
SmartStoreNET-3.x\src\SmartStoreNET.sln
The download link https://github.com/smartstoreag/SmartStoreNET
I use visual studio 2015 enterprise edition and windows 10.
First, you must be change the "Solution Configuration" to Debug mode, and second change the "Solution Plataform" to Any CPU.
This work for me.
I recently went through this integration/configuration procedure trying to get a local instance of SmartStore.NET up and running with demo data. I was able to get there eventually, but the development environment setup was by far the most tricky.
I would suggest starting with these two links:
http://docs.smartstore.com/display/SMNET30/Installing+SmartStore.NET
http://docs.smartstore.com/display/SMNET30/How+to+build+SmartStore.NET
I have a hunch you're issue may be your development environment configuration is not fully correct. Check out this page for more details about requirements:
Technology and Prerequisites
http://docs.smartstore.com/pages/viewpage.action?pageId=35555597
*NOTE: they reference ASP.NET 4.5.1 but I had to use 4.61 to take advantage of some newer features in C# 7.0 - Tuples, and several others)
Probably the most significant discovery I found was their were dependency issues when trying to restore the NuGet packages referenced in the solution. I had to go through this process maybe 4 or 5 times to finally get the app running locally.
Once all of this was complete, getting it working in 2015 required little effort.
I would also suggest narrowing your question to more specific problems. (that's just me)
In my Visual Studio 2015 MVC project, when I right-click a menu under the Views folder
and select Add -> View... the dialog is painfully slow to appear (about 60 seconds slow).
Some contextual information that might be helpful:
Visual Studio 2015 Community Edition
Running on a Parallels VM w/8GB (so it probably shouldn't be this slow)
The project I'm working in has been upgraded from MVC 3 -> 4 -> 5.
ReSharper 10.0.1
I reinstall my operate system, the problem seems resolved. But it came again when my project rewrite the router in MVC5. So I guess the problem is in MVC Router.
If you build a new project, the problem will resolve. So check you MVC project, Especially if you have override your Router in MVC5.
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!
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'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.