I need to prevent copy/paste options in sandbox. Can you please suggest me how it can be done. Also please clarify whether sandbox is applicable only for web environment or it can also be used in the windows.

Thanks

I post my question here :

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=2057135&SiteID=1

You really help me if you could show me how to solve this problem .

Thank alot.

Guy.

Is Dispatcher.PushFrame not available in partial trust? If so it’s not documented anywhere. I’m getting pretty sick and tired of finding crap that I can’t do and nobody has bothered to make a note of. I’ve invested alot of time into supporting this new platform just to find out that it’s crippled in unexpected ways that are completely undocumented.

Myself and another fellow have been unable to load a custom mouse cursor in an xbap. (see: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1536464&SiteID=1&mode=1)

Is this also a limitation of XBAPS? It doesn’t seem to be mentioned anywhere.

Turns out the only way to do this is to use a hyperlink object. See http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1212612&SiteID=1

Do you know of another way to “navigate” that will work?

Bryan
- The browser download dialogs is the dialog shown when a user navigates to a file whose content-diposition is set to attachment. (This is set in the HTTP header.) This is useful for scenarios where you’re trying to content from the server to the user’s machine.

- Excluding XamlWriter.Save from the sandbox came down to a V1 time constraint. If this is something you feel should be in the sandbox, please add it to the feature wiki (http://channel9.msdn.com/wiki/default.aspx/WPF.FeatureSuggestions) and explain your scenario. We appreciate the feedback!

Thanks both for the comments!

Since it appears the functionality of XamlWriter.Save can be reproduced in a few hundred lines of code, is there really anything gained by having it disabled in the framework?

Available
XAML Serialization (via XamlWriter.Load)

Unavailable
XAML Deserialization (via XamlWriter.Save)

Are these terms used backwards? Shouldn’t Serialization be with XamlWriter.Save and Deserialization be with XamlWriter.Load?

And yes, you’re absolutely right.

http://www.foo.com/my.xbap can render<Image Source="http://www.bar.com/other.jpg">. Ditto with MediaElement.

Thanks,
Karen

Can you confirm how the cross-domain media is supposed to work? Specifically, assume I have an xbap at http://www.foo.com/my.xbap.

It has an Image inside the Page, with Source=http://www.bar.com/other.jpg.

Should the Image render? What if it’s a MediaElement instead of an Image? From your chart above, it implies it ought to render, but I wanted to confirm.

Thanks, Rolf

Thanks
JL

Yes, the controls in both places is a typo (and should most definitely only be in the supported table!).

You also are correct about WF - I’ll also add that to the table for clarity.

Thanks for the comments,
Karen