asp.net - Specify Shadow Copy location in configuration -

on development machine, have slow system disk (ssd) , fast (ram disk) development disk. once visual studio , running, develop/build/test cycle extremely fast, application start slower [i believe] because of shadow copying of assemblies system disk clr download cache lives.

i have specified visual studio debugging assembly cache location on ram disk, after initial load ssd of referenced assemblies on ram disk.

i know can add custom code application affect change. however, because configuration specific development environment, don't want make code changes modify shadow copy behavior. seems leave me 3 choices:

• disable shadow copying in web.debug.config
• somehow specify cachepath , applicationname settings appdomainsetup requires in web.debug.config only
• somehow specify clr's download cache path point ram disk

i'm not familiar enough details of how clr uses shadow copy know if disabling adversely affect development , test cycle in either subtle or overt ways. (i'm using iis express on dev box, not iis, in case matters.) think i'm left 3 questions:

what effects of disabling shadow copying on code/build/run locally development cycle?

is there configuration setting specify shadow copy location assembly?

is there way change global clr download cache location or temporary asp.net files directory location?

(and of course 4: did miss else? :)