SecurityExceptions and compile warnings in xbap projects

Update:

I have removed the following attributes from my AssemblyInfos (which makes sense i suppose), and i seem to have gotten a bit further.

[assembly:AllowPartiallyTrustedCallers]
[assembly: SecurityRules(SecurityRuleSet.Level1)]

I'm now able to load my assembly and get a 'proper' MethodAccessException on an actual line of code

Attempt by security transparent method '*..ctor(...)' to access security critical method 'ActiproSoftware.Windows.Themes.ThemeManager.BeginUpdate()' failed.

Hi Munish,

Yes in .NET 4.0 Microsoft changed completely how security works.  We had to remove the AllowPartiallyTrustedCallersAttribute on the assemblies since it caused .NET 4.0 security issues for some of our features.

I'm not seeing any issues running our XBAP demo on the site though.  Do you get that error on startup or on a specific sample?

We don't ship an XBAP demo project but on its project properties' Security tab, we have "Enabled ClickOnce security settings" checked, the partial trust radio button checked, and Internet zone selected.

Regarding your demo:

I first get a "Application Run - Security Warning" dialog, where it asks me to "Run" or "Don't Run" the sample browser. I choose run, obviously, and after downloading the XBAP i immediately get the above error, i never actually see the sample browser.

Since it works on your machine, i thought maybe it's a local problem, but i tried to run other 4.0 XBAPs online and they seem to work fine.

On our XBAP project security tab we also have "Enabled ClickOnce security settings" checked, and the partial trust radio button checked. We have Zone set to Custom however, because we need some additional permissions (which we define in app.manifest), to run/debug our application locally. Perhaps something in there is causing it, though that wouldn't explain why i can't run your XBAP demo.

I will try some things out in a clean project and keep you guys updated.

Update:

When i uninstall 12.1, the online sample browser runs fine. Installed 12.1 again, and i get the exception again.

Only thing i can think of at the moment is that the online demo tries to use the assemblies from the GAC when i have 12.1 installed and that they are somehow different from the assemblies the online demo uses normally.

With a clean project i get the same result as in our 'real' project, it fails when i try to call ThemeManager.BeginUpdate.

Hi Munish,

We've been researching this and see the same thing you do.  If WPF Studio is installed on the machine, the XBAP demo on our site fails.  If we uninstall WPF Studio, the XBAP demo works fine.  The assemblies should be the same in the GAC as they are from the XBAP.  But for some reason the security is treating them differently.  We've been looking on the web for answers but aren't finding anything so far.

As for new clean projects, we tried one here and it worked ok.  If you want to e-mail our support address with your new simple sample, we can try it.  Please rename the .zip file extension file so it's not spam blocked.