tag:blogger.com,1999:blog-4126985520350746834.post9135080039996455440..comments2012-01-02T17:34:47.493ZChris O'Brienhttp://www.blogger.com/profile/10022906552670607366noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-4126985520350746834.post-61236623413704985622012-01-02T17:34:47.493Z2012-01-02T17:34:47.493Z@Jasper,<br /><br />Unfortunately I didn&#39;t get very far with the sandbox/versioning discussion with the product team. IIRC we started the e-mail conversation but I stopped getting replies unfortunately, I think because someone moved on.<br /><br />I&#39;m not aware of an automated way to rename the WSP as part of the dev workflow in Visual Studio - I think this needs to be a manual step. I haven&#39;t done much development for SharePoint Online, but I think my approach would be to dev against a local SharePoint instance running the sandbox service initially, then only deploy to SPO when ready. This way most of the iteration is done in an environment where you have more control.<br /><br />Good luck.<br /><br />Chris.Chris O'Brienhttp://www.blogger.com/profile/10022906552670607366noreply@blogger.comtag:blogger.com,1999:blog-4126985520350746834.post-49160790566893573572011-12-28T12:38:53.604Z2011-12-28T12:38:53.604ZHi Chris,<br /><br />I was wondering what you found out about upgrading when talking to the product team. I&#39;m struggling with the same things in SharePoint online, where you&#39;ve got even less options to upgrade (no powershell). <br /><br />What I need is a good way to use upgradable solutions, even in development scenario&#39;s. Is there a way to make Visual Studio take care of renaming the WSP before you deploy it for instance? I was wondering what your list of do&#39;s and dont&#39;s is. Thanks.Jasperhttp://www.blogger.com/profile/00842379683067594806noreply@blogger.com