You can delete those folders if you don’t need the old test run results and need to free up space. That folder will contain a folder for each test run, as shown in the example below. For Visual Studio projects, you can find these on disk in the root of your solution directory in a folder named TestResults. If you run Visual Studio unit or performance test runs, the test results folders may consume significant space if you have a lot of tests or large project outputs. Then I use Source Control Explorer to selectively get those folders containing the solutions I need to work with. Tip: As a practice, I map to local folders at the project collection, team project or branch level, and then click Cancel when asked if I want to download the workspace source. But if there are parts of that team project’s source that you do not work with, you don’t need that source on disk. When you first map to a new team project in Visual Studio, by default the “Create Workspace Mapping” process in Visual Studio will map and get an entire team project. Don’t Download Source That You Don’t Need These can build up as you move from working on one release to another. Once you have gone through those, developers may be able to free additional disk space using the tips below: Delete Un-Needed Local Source Branchesĭelete from your local hard disk those source branches that are no longer in use. This Microsoft Support article covers the most common ways to free disk space: This post lists a set of strategies I have used to help customers free up hard drive space on developer machines. It usually isn’t an issue if I have ample disk and get to change hardware out every few years, but that isn’t the case for everyone. In this post, Senior Application Development Manager, Patrick King, shares some tips for freeing up disk space on a development machine.Īs a developer, I see my free disk space diminish over time.
0 Comments
Leave a Reply. |