The only way I could get this to work was to either create a copy of the .exe file to match the other config or to create a hard link where the name of the link matches the other config, link.
For example, if MyExe.exe has MyExe.exe.config then for my alternate config, named MyExeAlt.exe.config, I could create a hard link to the executable that matches the name of the alternate .config file ln MyExe.exe MyExeAlt.exe and that would work, but it creates a hard link, which you need to remember to remove when you update the source (MyExe.exe) file, so it’s not really preferred. Doing the same with a symlink does not work, unfortunately. In the end, I did neither and just worked around this in my application logic. I will have to dig into the runtime source to see why this option is no longer working. On May 8, 2014, at 7:05 AM, cocowalla <colin.anderson...@gmail.com> wrote: > I realise this is an old post, but I'm trying to do the same thing as you and > was wondering if you came up with a solution? > > I've ended up 'solving' this by creating a new AppDomain and setting the > ConfigurationFile property to the config file I want to use. Feels like > overkill to achieve something so simple though, so I'd be interested in > finding out about simpler solutions! > > > > -- > View this message in context: > http://mono.1490590.n4.nabble.com/MONO-CONFIG-not-working-tp4661189p4662710.html > Sent from the Mono - General mailing list archive at Nabble.com. > _______________________________________________ > Mono-list maillist - Mono-list@lists.ximian.com > http://lists.ximian.com/mailman/listinfo/mono-list _______________________________________________ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
