I'm just reaching here
Create a file group 'Dev Projects' with a pathname to the folder where the binary lives in, e.g., %DevDrive%\Dev\Projects\*\*.
Then create a Computer Security Policy for the file group and select Installer / Updater as the access rights policy. You might have to toy with the two Defense+ sandbox config options mentioned below in conjunction with this.
If the above don't work, try to configuring the Computer Security Policy for your IDE as an 'Installer / Updater', and en-check 'always trust files from trusted installer' in Defense+ settings, sandbox settings. You may even have to en-check 'automatically detect installers / updaters and run them outside the sandbox'.
Oh, and don't forget there's the 'execution control' settings. Per the rules:
Comodo Internet Security calculates the hash of an executable at the point it attempts to load into memory. It then compares this hash with the list of known/recognized applications that are on the Comodo safe list. If the hash matches the one on record for the executable, then the application is safe. If no matching hash is found on the safe list, then the executable is 'unrecognized' and you will receive an alert.
These settings are independent of the sandbox itself. If sandboxing is enabled, the app image executes according to its access rights defined in 'execution settings'. If no execution settings are enabled, the app image is virtauliized w/out system resource access restrictions If the foregoing don't work suitably, you're going to have to disable one or the other component of Defense+ for the duration of your dev session.