Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Your sentiment is shared by many, many devs trying to do this for legit purposes. There are some work-arounds out there, all of them either hacky or bizarro. But this is probably the best one I've seen: <a href="http://blogs.microsoft.co.il/blogs/alon/archive/2010/07/06/screen-capture-in-silverlight-4-0.aspx" rel="nofollow noreferrer">Screen Capture in SIlverlight 4.0</a>.</p> <p>Just read again and saw that you're not looking for a crossdomain.xml solution. This page has some other options (again, no solution out there is "great"): <a href="http://betaforums.silverlight.net/forums/t/118030.aspx" rel="nofollow noreferrer">http://betaforums.silverlight.net/forums/t/118030.aspx</a></p> <p>Also, not sure if this is an option, but your app as an OOB app will not be restricted to security checks in ClientAccessPolicy.xml or CrossDomain.xml. Is Out-of-Browser an option for you?</p> <hr> <p><em>EDIT:</em> Upon further review of the post and comments, I believe (Tom, please confirm this) that the need isn't to get a screenshot of the user's instance of the SL app running on their own box (which something like <a href="http://blog.gfader.com/2010/06/customer-support-in-silverlight.html" rel="nofollow noreferrer">Customer Support in Silverlight</a> would take care of pretty well).</p> <p>Rather, it is to take picture of the user's screen (same as <kbd>PrtSc</kbd>-ish). In this case, it is a lot tougher, but not impossible. Rui show's how he does it <a href="http://xamlpt.com/blogs/ruimarinho/archive/2010/02/23/grab-desktop-in-silverlight.aspx" rel="nofollow noreferrer">here</a>, but it relies on a component already being on a user's machine. Jeremy get's even more creative with <a href="http://jmorrill.hjtcentral.com/Home/tabid/428/EntryId/442/Silverlight-4-Hack-Use-Native-Desktop-CLR-Without-COM-Registration.aspx" rel="nofollow noreferrer">Silverlight 4 Hack: Use Native/Desktop CLR Without COM Registration</a>, which would effectively allow access. </p>
    singulars
    1. This table or related slice is empty.
    1. PODoes Silverlight 4's WriteableBitmap *really* cripple legit cross-domain access in the name of DRM?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USTodd Main
    1. USTodd Main
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COBeing OOB doesn't solve this problem; all it does it relax restrictions relating to sockets and permissions.
      singulars
      1. PO
      1. USTom Ritter
    2. CO@Tom Ritter: I guess I'm confused - how doesn't that solve the problem? I guess I should have said "elevated permission OOB".
      singulars
      1. PO
      1. USTodd Main
    3. COEven full Trust OOB doesn't negate WriteableBitmap's DRM Pixel stuff. ClientAccessPolicy/CrossDomain have nothing to do with it - the cross-domain pixel access is independent of them.
      singulars
      1. PO
      1. USTom Ritter
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload