Skip Ribbon Commands
Skip to main content

Robin | zevenseas | SharePoint Blog

:

The zevenseas Community > Blogs > Robin | zevenseas | SharePoint Blog > Posts > IGNITE recap
November 06
IGNITE recap

After a pretty exhausting but very interesting week I can say that SharePoint 2010 will be very.. awesome..  (that was pretty much THE word of the week by a particular trainer and a few attendees (amongst them were SharePoint heroes like Tobias Zimmergren, Waldek Mastykarz, Joris Poelmans (AKA JOPX)))

After seeing a lot of sessions in Vegas at the SPC09, I thought that I had seen all the cool new things that are coming but this week showed a couple more.

One of the biggest new things for me was the removal of .stp files and instead of those, now we have .wsp’s that are called “WebTemplates”. Because they are .wsp’s, we can make use of the upgrade functionality. Meaning that in 2010 we have UPGRADEABLE webtemplates!!

Once more..

in 2010 we have UPGRADEABLE webtemplates!!!

To give you the bigger picture ..

  1. User can click together the layout..
  2. User can save the site as template
  3. Developer can import the WSP into VS
  4. Developer can upload the WSP as a farm solution
  5. Sites can be created based on that custom webtemplate
    1. Developer modifies the webtemplate according to new business needs
    2. Developer updated WSP
    3. WSP get’s upgraded
    4. Existing sites get updated using the Feature Update framework

(at least.. that’s the story ;))

Can’t believe they didn’t shout this one out as big as the ‘F5 experience’ for example. I mean.. businesses were (and are) waiting for many years to have this functionality available..

For now I just wanted to say.. thanks Microsoft for making this possible, thanks Wouter van Vugt, Vesa Juvonen and Todd Carter for giving an awesome developer training and thanks Dan for giving me his seat ;)

Comments

Sahil Malik

The kicker of course is "Existing sites get updated using the feature update framework" - which is not as trivial as .. just bullet 5.4 if you know what I mean :)

And then if you think about it, the bulk of your work is still in authoring those updates.

So practically speaking, it is still a lot of work, but the one big advantage here is a standard supported upgrade mechanism, that is in code, and not in documents - which is the feature upgrade framework.

Sahil
System Account on 10/11/2009 13:48

Robin

Hi Sahil,

yes you are totally right.. and even with the feature upgrade framework as it is now you'll need to build your own tool that updates an individual feature or a set of features instead of doing a PSConfig -cmd upgrade that upgrades the entire farm..

But.. at least it is supported right now and that's something we are wanting for quite some time eh? :)
System Account on 11/11/2009 02:19
 

 Statistics

 
Views: 1679
Comments: 2
Tags:
Published:1320 Days Ago