I have subclassed DomainManager and HostSecurityManager to allow for (pre) runtime edits to the application configuration. I am doing this so that I can store all of our configuration bits in a database and still leverage the standard .Net configuration processing. My apps will stream the updated configuration to the user-profile (on-demand) based on checksum comparisons with the local and server versions. I have this working for XBAPs when I set the HostInBrowser flag to false, but my custom DomainManager appears to be completely ignored when HostInBrowser is set to true.
Note: these are Full-Trust LOB applications and the custom DomainManager is configured via the <runtime> configuration section.
Question 1: Any idea why the custom DomainManager is not loaded when running in the browser?
Question 2: When running out of the browser the appdomain load process does not respect my changes to the AppDomainSetup.ConfigurationFile property - it overrides my changes. I have worked around this problem by subclassing HostSecurityManager to rewrite AppDomainSetup.ConfigurationFile after the security-policy processing has completed. This seems like a pretty dirty hack that may not work in the future. I would think that I can get respect for my changes to the config-path by working the the evidence/trust APIs but I am not sure how. Can anyone help?
Thanks much!
-Brian