I think you’ve answered my question in your new post. I see now that pointing at a complete config file is no problem for NSandbox! Great stuff.

It would be cool if there was a IConfigurationWriter in the library that you can point at a complete custom config file. The project I’m working on adds a section to the config file.

Yes, NSandbox will allow you to write a new App.config file for each new AppDomain (sandbox). Right now I have a “parameterized file” configuration writer that takes a template file and then lets you globally replace “variables” in the format “$variableName$” with different strings before writing the App.config file to disk. Of course, this is just one implementation of IConfigurationWriter and you can make your own.

As for the permissions, right now it’s hard-coded as “full trust” but it won’t be difficult to change this in future versions

This test outlines all of those features:
http://nsandbox.svn.sourceforge.net/viewvc/nsandbox/trunk/NSandbox.Tests/SandboxTest1.cs?revision=12&view=markup

I’ll post some examples soon

-Matt

When you run your sandbox, can you supply an alternative config file? I’m working on a project (no, this time it’s not conditions ) where I’d like to test different app.config settings, without having to create many test projects. Is that possible?