
There could be certain projects in your solution such as setup projects or projects which are not directly required to execute your start up project and can be excluded from build.
Make a project in visual studio 2017 for mac generator#
You can refer to Precompile your MVC Razor views using Razor Generator to try it yourself. However, MVCBuildViews comes with performance penalty so pre-compiling MVC views is the most preferred approach to manage MVC view effectively. We can build MVC views during MVC project build, using MVCBuildViews as true. You can even set it to quiet if you need not see output or occasionally you may set it to detailed or even diagnostics to troubleshoot issues in build depending upon the requirement.īy default, MVC views are compiled at runtime. This will show minimum build detail during build in build output window. Again referring to the same screenshot provided in tip #1, set the MSBuild project build output verbosity to " Minimal". However, updating this setting would also decrease the build overhead and reduces the build time. You can set the build verbosity based on your choice.

Refer Build the currently selected project. This could be especially helpful when there are a large number of projects and you would like to build and run startup project only without building all the projects in solution even if they are not dependent and further those unrelated project could include pre or post build tasks. While being on the "Build and Run" settings mentioned in the previous step, check "Only build startup and dependencies on Run". Only Build Startup and Dependencies on Run This can be set in Visual Studio by Tools -> Options -> Projects and Solutions -> Build and Run. Set this value to an optimum level for your machine, e.g., for i7 processor which can execute up to 8 threads, you can set this setting to 8. Although, there could be project dependencies set in your project which will allow some project to build in particular order, still this setting would automatically deduce the parallelism among the projects during build. This is a magical setting which builds project in your solutions in parallel. I will start with making configuration changes in Visual Studio first and then will touch some project level settings followed by easy architectural changes and finally with some other options which are worth mentioning.

Use of improved hardware like processor, hard disk, RAM, etc.įor the purpose of this tip, we will mainly focus on #1, Optimizing Visual Studio settings, while touching briefly on #2, Project architectural changes.Broadly, the improvement factors can be categorized as below: Personally, I felt that when an application starts taking more than a minute to build, then it's time to sit down and think about making appropriate adjustments so that the application build time remains in acceptable limits. To overcome such limitations, there are number of tips which can be used to quickly improve the application build times and thereby improving development productivity many folds. However these are not preferred approaches, if one wants to see the improvement instantly. Secondly, making architectural changes in ASP.NET project like separating project logically, minimizing number of assemblies and creating separate solutions can also be considered as long term strategies for the same. While buying a faster processor, better hardware and increasing RAM sizes are always options to consider to improve performance. With increasing business demands, ASP.NET projects become more and more complex and 'large' resulting in higher project build and load times.
