I suggest you ...

Cleanup of workspace

For faster unit-testing, I am using a RAM-drive as workspace, with 4GB space.

NCrunch keeps all old build artifacts around until they are no longer needed. In practice, this means that as I am working, the workspace keeps on filling up, since a change in one place which doesn't impact something else means both versions are kept in the workspace.

As a result of this, the 4GB quickly get gobbled up, forcing me to cleanup by deactivating/activating NCrunch (which means everything gets rebuilt, even though this isn't necessary) or manually trying to delete as much as possible in the filesystem.

More aggressive cleanup (if possible) would be helpful. Besides that, a "cleanup" command would be great. It should purge everything, including any data held by the NUnit runners. At the same time, any tests need not be re-run or anything rebuilt until needed according to the engine mode.

8 votes
Sign in
(thinking…)
Sign in with: facebook google
Signed in as (Sign out)

We’ll send you updates on this idea

Daniel Rose shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

0 comments

Sign in
(thinking…)
Sign in with: facebook google
Signed in as (Sign out)
Submitting...

Feedback and Knowledge Base