I was making some alterations to Statlight to better support extensions, in area of what they are capable of (which has no impact on AgUnit) and in how they are located/loaded (which does). https://github.com/staxmanade/StatLight/pull/11
The scenario I wanted to talk about is this: I want to have solution (or project) specific plugins for Statlight, that live somewhere in the project and therefore whoever uses the project doesn't need to make the additional step of making sure they get the
extension into their Extensions folder (and update if needed) in order to be running the tests.
This is handed in StatLight.exe by specifying extension assemblies from the command line. Now my question to you is, what would be the best way to support that in AgUnit?
The solution I've implemented on my team at the moment is that we're looking in the folder where we load .xap file from for .NET assemblies named *.StatLightExtension.dll and loading them from there, and we have an MsBuild task to copy the extension to the
output folder of our Silverlight project.
While it does work for us, I do realise this is not really a low-friction solution. What do you think would be a better option to support this in AgUnit?