tag:blogger.com,1999:blog-4126985520350746834.post7587028559397223590..comments2024-03-28T07:00:21.554+00:00Comments on Chris O'Brien: Sandbox code no longer available in Office 365 – with immediate effectChris O'Brienhttp://www.blogger.com/profile/10022906552670607366noreply@blogger.comBlogger5125tag:blogger.com,1999:blog-4126985520350746834.post-67756343851139916412016-08-02T22:02:39.704+01:002016-08-02T22:02:39.704+01:00Yep, they did it!Yep, they did it!Anonymoushttps://www.blogger.com/profile/17741659363820166463noreply@blogger.comtag:blogger.com,1999:blog-4126985520350746834.post-55772996008644435082016-08-02T10:57:40.095+01:002016-08-02T10:57:40.095+01:00@Ricardo,
Yes, sites saved as a template should b...@Ricardo,<br /><br />Yes, sites saved as a template should be fine. It seems your testing has backed that up too..<br /><br />Cheers,<br /><br />COB.Chris O'Brienhttps://www.blogger.com/profile/10022906552670607366noreply@blogger.comtag:blogger.com,1999:blog-4126985520350746834.post-9996693353951274302016-08-02T10:47:04.678+01:002016-08-02T10:47:04.678+01:00Hello Chris,
Great article! In my team we are wor...Hello Chris,<br /><br />Great article! In my team we are worried about those packages related with sites saved as template. I guessed this kind of solution is considered a non-code sandbox but I wanted to be sure. So, after reading your article, I did two things:<br />1) search for assemblies in the package.<br />2) upload the file in a new site collection and try to activate it.<br /><br />Fortunately, I couldn't find any assembly in the container and I had no problems during the activation. So I think everything should be OK, shouldn't it?<br /><br />Regards,<br />Ricardo.Ricardohttps://www.blogger.com/profile/18139230279772908796noreply@blogger.comtag:blogger.com,1999:blog-4126985520350746834.post-50991094358102698712016-08-02T10:08:24.272+01:002016-08-02T10:08:24.272+01:00This is a really surprising, and sudden, move. I&#...This is a really surprising, and sudden, move. I'd be interested to find out if some obscure security issue had forced their hand, or if some internal metrics told them that it would impact so few tenants... Luckily, I've been unticking the include assembly option for years now, so hopefully no impact for us.<br /><br />That said - it should act as a lesson about how far MS are willing to go to protect their vision. Sandbox code today - what's next? What else has been soft-deprecated and in danger of such short-notice removal? Custom master pages? Features?Davehttps://www.blogger.com/profile/15245523145860887596noreply@blogger.comtag:blogger.com,1999:blog-4126985520350746834.post-33094352649490736442016-08-02T09:37:44.627+01:002016-08-02T09:37:44.627+01:00In my opinion, Microsoft approach to this argument...In my opinion, Microsoft approach to this argument hasn't been serious. There are many inconsistencies between first messages about SP73009 problem and final 'resolution'?!?!.<br /><br />I have many workflows with declarative custom activities that i can't deploy.<br />Set false to 'Include Assembly In Package' permit me to activate solutions and features but i receive 'System.Xaml.XamlObjectWriterException: Cannot create unknown type' when workflow run..ZioFetecchiahttps://www.blogger.com/profile/15706438738614170777noreply@blogger.com