Yesterday I talked about the changes in security policy for managed applications , namely that managed applications will run with full trust – the same as native applications – when you execute them directly. That change doesn’t mean that managed code can no longer be sandboxed however – far from it.  Hosts such as ASP.NET and ClickOnce continue to use the CLR to sandbox untrusted code.  Additionally, any application can continue to create AppDomains to sandbox code in. As part of our overhaul of security policy in v4, we made some interesting changes to how that sandboxing should be accomplished as well.  In previous releases, the CLR provided a variety of ways to sandbox code – but many of theme were problematic to use correctly.  In the v4 framework, we made it a goal to simplify and standardize how sandboxing should be done in managed code.

See the original post:
Sandboxing in .NET 4.0

Filed under: 2008, 2009, 3.0, acr, action, ads, adventure, api, app, application, archive, art, atom, Blog, boxing, build, business, cd, change, cli, cloud, code, coding, community, control, Cookie, css, data, developer, developers, ea, eff, elements, email, event, events, fun, gdc, goo, hd, heat, host, icon, im, Interesting, internet, ion, IT, java, javascript, King, language, languages, library, location, long, ls, mail, march, media, Meta, microsoft, Microsoft Rules, mmo, new, news, NIN, notification, opera, order, OS, pc, policy, post, pre, pro, problem, problems, Q1, rant, Rants, release, Releases, required, rights, rip, rss, screen, script, search, security, server, simplify, syndication, tag, tags, talk, tasks, theme, themes, time, tip, tor, track, trends, ui, uk, unity, update, used, value, wind, windows, word


Hurricane Sandy and My Windows Phone