![]() This code is now optimized to reuse data structures already available in the Visual Studio process. This process now starts after the solution has loaded, so you can start coding faster.Īs another example, Visual Studio used to synchronously initialize the out-of-process C# language service. The rest of the components initialize asynchronously afterwards.įor example, Visual Studio previously scanned git repositories during solution load to light up the source control experience. Only critical code that enables navigation, editing, building, and debugging will run during solution load. We are changing this to make Visual Studio developers productive as quickly as possible. Historically, many components and extensions used solution load to perform initialization work, which added to the overall solution load time. Another big effort is to get unneeded components out of the way of solution load. Parallel solution load is part of the work we’re doing to improve solution load. ![]() A customer with a very large, 400+ project solution told us that their solution now loads 2-4 times faster! Solution load is getting leaner NET solutions experienced even larger improvements, and now load twice as fast as previous versions. We saw that, in aggregate, customers experienced a 25% improvement in solution load times in version 15.6, across all solution sizes. We continuously monitor solution load telemetry coming in through the Customer Experience Improvement Program. We wanted to leverage the power of all the CPUs during solution load by loading projects in parallel. Many Visual Studio customers have machines with at least 4 CPU cores. We’ve enabled parallel project load for large solutions that contain C#, VB. With version 15.6 we wanted to go one step beyond optimizing IntelliSense calculation. IntelliSense data was cached, so subsequent loads of a solution didn’t require a design-time build. Solutions that were opened for the first time on a machine loaded significantly faster because of this parallelization. In the previous version of Visual Studio 2017, version 15.5, we optimized the calculation of IntelliSense data by parallelizing the design-time build that produces the data. During the first load of a solution, Visual Studio calculates all the IntelliSense data from scratch.
0 Comments
Leave a Reply. |