tag:blogger.com,1999:blog-4126985520350746834.post128962281279999305..comments2024-03-28T07:00:21.554+00:00Comments on Chris O'Brien: Feature upgrade (part 3) – introducing SPFeatureUpgrade kitChris O'Brienhttp://www.blogger.com/profile/10022906552670607366noreply@blogger.comBlogger10125tag:blogger.com,1999:blog-4126985520350746834.post-31873101768226540972014-09-16T21:54:46.078+01:002014-09-16T21:54:46.078+01:00@Dennis,
I haven't tested on SharePoint 2013,...@Dennis,<br /><br />I haven't tested on SharePoint 2013, but it wouldn't be too much work to get the tool to work there if it doesn't already (assuming you have dev skills). <br /><br />The changes in the Feature framework between SP2010/SP2013 are fairly minor - so I don't believe there's anything that would get in the way of this.<br /><br />All the best,<br /><br />Chris.Chris O'Brienhttps://www.blogger.com/profile/10022906552670607366noreply@blogger.comtag:blogger.com,1999:blog-4126985520350746834.post-6784773366240975152014-09-16T08:49:22.981+01:002014-09-16T08:49:22.981+01:00Chris great work and nice article. It was very hel...Chris great work and nice article. It was very helpful to me. <br />Does the SPFeatureUpgrade kit works on SharePoint 2013?Dennishttps://www.blogger.com/profile/11320454387887189915noreply@blogger.comtag:blogger.com,1999:blog-4126985520350746834.post-78055202685944364212014-05-28T15:50:31.731+01:002014-05-28T15:50:31.731+01:00@Antonsen,
This was published in the 5th article ...@Antonsen,<br /><br />This was published in the 5th article in this series - <a href="http://www.sharepointnutsandbolts.com/2010/08/feature-upgrade-part-5-using-powershell.html" rel="nofollow">http://www.sharepointnutsandbolts.com/2010/08/feature-upgrade-part-5-using-powershell.html</a><br /><br />Cheers!<br /><br />Chris.Chris O'Brienhttps://www.blogger.com/profile/10022906552670607366noreply@blogger.comtag:blogger.com,1999:blog-4126985520350746834.post-24046728774003960832014-05-28T11:36:57.511+01:002014-05-28T11:36:57.511+01:00"[Coming soon] - a PowerShell cmdlet which al..."<b>[Coming soon]</b> - a PowerShell cmdlet which allows Feature upgrade to be run from script. (This is the final piece and will be ready shortly, since I’ve got the core logic implemented already.)"<br /><br />... comming soon? ;-)Antonsenhttps://www.blogger.com/profile/03101552107640663718noreply@blogger.comtag:blogger.com,1999:blog-4126985520350746834.post-83449038311325207112013-08-09T11:23:02.119+01:002013-08-09T11:23:02.119+01:00Does anyone has an idea why this happens on the We...Does anyone has an idea why this happens on the Web scope?<br /><br />Farm/WebApp/SiteCollection Scope is working well, but the WebScope gives this error for all Site Collections I've tried.<br /><br />Unable to access web scoped feature (Id: 00bfea71-d1ce-42de-9c63-a44004ce0104) because it references a non-existent or broken web (Id: 581e2333-fc2d-43e3-8cb0-96a3db718145) on site 'http://lenzeweb-test.lenze.com/app/akb'. Exception: System.Threading.ThreadAbortException: Thread was being aborted. <br /> at System.Threading.Thread.AbortInternal() <br /> at System.Threading.Thread.Abort(Object stateInfo) <br /> at System.Web.HttpResponse.End() <br /> at Microsoft.SharePoint.Utilities.SPUtility.Redirect(String url, SPRedirectFlags flags, HttpContext context, String queryString) <br /> at Microsoft.SharePoint.Utilities.SPUtility.RedirectToAccessDeniedPage(HttpContext context) <br /> at Microsoft.SharePoint.Utilities.SPUtility.HandleAccessDenied(HttpContext context) <br /> at Microsoft.SharePoint.Utilities.SPUtility.HandleAccessDenied(Exception ex) <br /> at Microsoft.SharePoint.Library.SPRequest.GetAllWebsOfSite(String bstrUrl, Object& pvarWebs, Object& pvarWebIds, Object& pvarParentWebs, Object& pvarLangs, Object& pvarTitles, Object& pvarUIVersions, Object& pvarFlags, Object& pvarWebTemplates, Object& pvarConfigurations, Object& pvarMasterUrls, Object& pvarCustomMasterUrls) <br /> at Microsoft.SharePoint.SPSite.SPWebCollectionProvider.GetWebsData(String[]& strNames, String[]& strServiceRelUrls, Guid[]& guidWebIds, Int32[]& nLanguages, String[]& strTitles, String[]& strDescriptions, String[]& strCreationTimes, String[]& strModifiedTimes, Boolean[]& bUserIsWebAdmins, Int32[]& nWebTemplates, Int16[]& nProvisionConfigs, Int16[]& nMeetingCounts, Int32[]& nUIVersions, Int32[]& nFlags, String[]& strMasterUrls, String[]& strCustomMasterUrls) <br /> at Microsoft.SharePoint.SPWebCollection.EnsureWebsData() <br /> at Microsoft.SharePoint.SPWebCollection.get_Item(Guid id) <br /> at Microsoft.SharePoint.SPFeatureEnumeratorBase.GetCachedWeb(SPSite site, Guid webId, Guid featureId)Anonymoushttps://www.blogger.com/profile/17634396717757239560noreply@blogger.comtag:blogger.com,1999:blog-4126985520350746834.post-5888428806853716072011-02-02T10:08:37.548+00:002011-02-02T10:08:37.548+00:00Thanks Sam :)Thanks Sam :)Chris O'Brienhttps://www.blogger.com/profile/10022906552670607366noreply@blogger.comtag:blogger.com,1999:blog-4126985520350746834.post-45520432784376259412011-02-02T03:53:38.945+00:002011-02-02T03:53:38.945+00:00Top work, Chris. Such a useful tool - clean UI, ea...Top work, Chris. Such a useful tool - clean UI, easy to use, and so critical for those of us using SP as a development platform that I can't believe Microsoft didn't bother writing something like this for Central Admin themselves!Sam Venableshttp://spnovocaine.wordpress.comnoreply@blogger.comtag:blogger.com,1999:blog-4126985520350746834.post-20933435561253456402010-09-08T16:05:51.363+01:002010-09-08T16:05:51.363+01:00yes, that make sense.
Thanks a lot,
Lucayes, that make sense.<br /><br />Thanks a lot,<br />LucaLucahttp://blogs.ugidotnet.org/lmaurinoreply@blogger.comtag:blogger.com,1999:blog-4126985520350746834.post-75361284717065847812010-09-07T21:57:13.539+01:002010-09-07T21:57:13.539+01:00@Luca,
Thanks, glad you like the tool.
That'...@Luca,<br /><br />Thanks, glad you like the tool.<br /><br />That's a great question - you do indeed need to test *multiple* Feature upgrade iterations as you develop your Feature upgrade XML/code. You cannot specifically "rollback" an upgrade as such, but by reverting back the version number to the real one you want to use (e.g. 1.0.0.1) and *reinstalling* the Feature (i.e. by retracting/redeploying the WSP rather than upgrading), the end result is that the Feature is installed at that version with the current Feature contents. You can then use this as the version of your Feature to take forward to other environments. In other words, SharePoint does not maintain historic versions of a Feature's state.<br /><br />Does that make sense?<br /><br />Thanks,<br /><br />Chris.Chris O'Brienhttps://www.blogger.com/profile/10022906552670607366noreply@blogger.comtag:blogger.com,1999:blog-4126985520350746834.post-44408747768526272712010-09-07T16:41:07.563+01:002010-09-07T16:41:07.563+01:00That's a great feature! I've just used it ...That's a great feature! I've just used it and works like a charm.<br /><br />But how could I manage frequently and partially upgrading during my development ? I mean, I need to upgrade from 1.0.0.0 to 1.0.0.1 but during the development I will need to do partial upgrading that will lead to the final 1.0.0.1 set of deployable features.<br /><br />Could I rollback an upgrade ?Lucahttp://blogs.ugidotnet.org/lmaurinoreply@blogger.com