Not supported. The dll config file is loaded before the test code actually has a change to run. One workaround is to create a copy of the test assembly with a different name and provide a separate dll config file for it.
Jeff. On Thu, Dec 16, 2010 at 6:05 AM, Mark Kharitonov <[email protected]>wrote: > Hi. > > I use [AssemblyInitialize] set up method to check certain stuff. Now > sometimes, I would like to change the application configuration file, > so that all the tests run in a new app domain bound to this new > configuration file. > > In a standalone app this is easy - I create a new config file, bind it > to a new app domain, create and unwrap my program class in a new app > domain and then run the code from the new app domain. > > But how can I make the tests run with a new config file? > > Thanks, > > -- > You received this message because you are subscribed to the Google Groups > "MbUnit.User" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<mbunituser%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/mbunituser?hl=en. > > -- You received this message because you are subscribed to the Google Groups "MbUnit.User" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/mbunituser?hl=en.
