Predictions for SharePoint Portal Server v3

Now here was an interesting post today from Mauro Cardarelli on the next version of SharePoint Portal Server. I’d have to say I am pretty comfortable with his predictions:

(1) There will be no SPS 2005. The timing doesn’t make sense. I think a more reasonable timeframe is (late) 2006.

(2) SPS 2005 will support both SQL Server 2005 and SQL Server 2000. You won’t be required to upgrade your database servers.

(3) The underlying technology will be the next version of the .NET Framework (2.0). The core functionality will be improved (i.e. tighter integration with the next version of Exchange and Office) but not radically different.

I’d also say I would agree with some of his wishlist items for next version.

(1) Late-Bound Security – people hate seeing links that they don’t have privileges for

(2) Better Search Interface – the SPS search engine is great; the interface for entering queries and seeing results is terrible

(3) Better Customization Tools – You shouldn’t have to manually alter CSS and XML files to expose additional functionality

(4) No more DOS – template publishing should be cleaner… the current generation doesn’t know how to use DOS…

Although I would say on number 4 that I can’t personally see the command-line tools going anywhere but who knows.

If you don’t like the command-line for stsadm tasks – you can do a lot through Frontpage already and there is always the little windows app for it that I haven’t tried before.

Thanks for the post Mauro – it’s always nice to think about what’s ahead. I’d post some of my wishlist items but most of them are items my team is developing now for the current version so I must stay hush for now. :)

This entry was posted in Microsoft Stuff. Bookmark the permalink.

One Response to Predictions for SharePoint Portal Server v3

  1. Mike Drips says:

    Customization definitely needs to be addressed in the next version of SharePoint.
    A return to document level security would be nice as well.
    I would rather see (and pay for) an SP 2005 version with these kinds of updates hit the market, than allow the Microsoft SP development team to hide behind the excuses of needing to be compliant with “the next .net, Longhorn, etc. (fill in product name)”.
    It really harms Microsoft’s reputation as company that quickly responds to the market to allow product teams to drag their feet on introducing product upgrades/enhancements.
    A three year gap between versions is too long, especially based on the issues of the current version of SharePoint.