Earlier this year Microsoft announced the next wave of Office products that will "redefine how people work", which included Exchange 2010, Office 2010, Visio 2010, Project 2010, and SharePoint 2010. All will enter public beta later this year and is targeted for general availability in the first half of 2010. Over the last few weeks we've seen a ton of information leak regarding the Office 2010 suite, and this week Microsoft has released a sneak-peak of SharePoint 2010.
So what exactly is SharePoint again? SharePoint is an enterprise portal that can be configured to run Intranet, Extranet, and Internet sites. SharePoint A SharePoint enterprise portal is composed of both SharePoint Portal and Windows SharePoint Services, with SharePoint being built upon WSS. WSS is typically used by small teams, projects, and companies. SharePoint Server is designed for individuals, teams, and projects within a medium to large company wide enterprise portal.
Feature Highlights:
- New UI including Ribbon
- Web Edit
- Silverlight Web Part
- Rich Theming
- Multiple Browser Support
- Visio Services
- SharePoint Designer
- Business Connectivity Services
The SharePoint 2010 team launched a sneak-peak website earlier this week, which you can find here. The site is loaded with videos, information on new features, and a complete overview of what is coming to SharePoint 2010.
There will be more announcements later this year in regards to new and improved features, which will be at the SharePoint Conference 2009 in Las Vegas on October 19th-22nd with CEO Steve Ballmer expected to be the keynote speaker.
















...
MS does some great software, but this ain't it. I would rather use Lotus (and note, yes they say multi-browser support, but support in anything other than IE is way behind, and means there are loads of stuff you can't do).
The test site they provided works perfectly well in multiple browsers.
EDIT: Also, the reason large organisations can't migrate away from IE6 is because (in my organisation at least) the people that developed the "Web applications" developed for IE6 instead of Web standards, and are still regretting it.
EDIT: Also, the reason large organisations can't migrate away from IE6 is because (in my organisation at least) the people that developed the "Web applications" developed for IE6 instead of Web standards, and are still regretting it.
because at that time IE6 Is the standard
No, HTML 4.01 and CSS2 were the standards.
Firefox doesn't help the cause though by not offering MSI packages for wide scale enterprise deployment or the lack of active directory integration. Many people I know in decision making areas want to leave IE but can't due to the alternative lack in a particular area.
MS does some great software, but this ain't it. I would rather use Lotus (and note, yes they say multi-browser support, but support in anything other than IE is way behind, and means there are loads of stuff you can't do).
there speaks the uninformed. The latest sp for MOSS2007 upgrades non-ie browsers to a higher compatibility rating, however they still lack some of the functionality required to properly edit page layouts. I'm using ie 7 & 8 across the organisation with NO problems whatsoever. There is another issue which prevents the rich text editor working in anything but ie, this is easily rectified after 2 mins googling.
We are implementing MOSS to get away from the horrendous pot of **** that is Lotus Notes.
MS does some great software, but this ain't it. I would rather use Lotus (and note, yes they say multi-browser support, but support in anything other than IE is way behind, and means there are loads of stuff you can't do).
IE7 and 8 work fine with SharePoint 2007, and everything works in FireFox except the rich text editor, which is easily replaced by a cross-browser one. MOSS 2007 is an awesome product, and 2010 looks like it will be even better.
Sharepoint can drastically improve communication in an organisation. Quite how you can compare that to a toolbar/menu enhancement i'm not sure
I find the ribbon to be cumbersome. I waste more time looking for the command I need or just using keyboard shortcuts. The ribbon to me is a step backward.
One thing I'm very interested to learn is if our SharePoint license will give us access to the Office web apps. Not everyone in our company needs Office, but it would be nice if they could do basic edits directly from SharePoint (we have more SharePoint CALs than Office licenses).
Last edited by JonathanMarston on 20 Jul 2009 - 16:42
You are stuck with sharepoint, there is no easy way to get the content out of there, unlike most other systems which are very open, or built on open standards. Look for a system that uses SVN or git as a backend. Microsoft don't even use sharepoint, that should give you a hint to stay away from it.
I'd like 'lists' to become more like tables in databases that can be cross-referenced. At the moment, they're very much like Excel Spreadsheets (without the functionality). This is the thing I wish most they'd address.
I also think that documents should be able to be 'published' to different areas of a site collection without having to create multiple instances. For instance, you might want a policy to exist in a central policy repository and also have it within the area of the site to which it's most applicable - for example, an IT policy. Sure, you can hyperlink but you then lose the ability to check out/edit/version history from the secondary location.
Seems like Microsoft just treated Sharepoint like the rest of the Office 14 suite and stuck on a ribbon. I hope there's more to come after this 'sneak peek.'
+1
I completely agree, this is a MASSIVE problem. Come on ms
No Folder tree is used.
Insert/Index anything into SharePoint without having to run SharePoint
No Folder tree is used.
Insert/Index anything into SharePoint without having to run SharePoint
thanks for the tip. I'll be checking out Knowledgelake
Commenting has either been disabled on this article or you are not logged in. Click here to login or register, its free!
Note: Anonymous commenting is disabled in order to keep the quality of responses to a high standard.