Wednesday, May 12, 2010

SharePoint 2010 - What I hate

SharePoint 2010 is BLAH BLAH BLAH , i know that but there are few things I really didn't like or hated.

Hardware requirements for SP2010 Development:
I am sure you know it that you need 64bit machines + 6-8GB RAM to be able to develop for sharepoint 2010 but thats not all. What ever way you tune it you will see Virtual machines slowing down often / hung / crashes and much more..

Top Nav and Quick launch Navigation links:
You can click the links to navigate to the page/document but you cant right click the navigation links in Top Nav and Quick Launch and say open in another Tab. As during the demo's we need to have multiple pages open to save time, you will feel the pain.

Core Search Web Part configuration change:
Have you tried changing the Metadata properties or XSLT for the Core Search web part , once you save it, Core Search web part will display a message "Refresh the web part... ", Its such a pain in case you want to play around different look and feel with extra metadata columns and xslt. One workaround I used was I designed my XSLT in 2007 and then used it in SP2010.

Content Query Web Part configuration:
In case you want to filter out items from the site collection based on its Content Type, Content Type Column is missing from filter list. You do have an option to filter items based on SINGLE content type.

i.e You can filter all the items of content type 'Business Page' but in case you want to see all the items which have content type as 'Business Page' or 'Finance Page' , you can't.

Alert Templates customizations:
Alert templates are stored in AlertTemplate.xml and if you want to have custom templates there is no other option then modifying OOTB file which is not recommended. In SP2010 , still the option is missing to add a new AlertTemplate_XYZ.xml file and let SharePoint merge the two files automatically.

Alerts and Delivery Options:
Try setting an alert for a task list , delivery options are Email OR SMS , there is no way to specify that I want both ???

Processing dialog missing while create Web Application:
Confusing .. as you don't know whats going on behind the scene.
I will add more with time in the meanwhile leave your comments from your experience.

Learn more languages:
As a MOSS developer , you were suppose to have experience of ASP.Net 2.0, HTML, Javascript, XSLT, CSS , CAML , WebServices , Infopath

As a SP2010 developer , you were suppose to have experience of ASP.Net 2.0, Framework 3.5 , HTML, Java-script, ECMA Script , XSLT, XHTML, CSS , CAML , LINQ , Silverlight, WCF ,InfoPath , PPS Designer , Power-shell and much more...

Client Object Model:
You are reading it right, even though this is a great feature added to SP2010 but also a pain to learn 3 different kind of Client OM , one for .Net Applications, Silver light has it own and JavaScript client has it own.

Also if not used very well , client object model can easily be used to delete items from site collections.

Sandbox Solutions:
Again I know this is a great ++ thing for hosting environments but as Microsoft has given options to control resource usage for all the sandbox solutions as a whole. One bad sandbox solution can eat up all the resources and block other solutions.

SharePoint Service Application:
:) - I know its a great improvement in terms of scalability but how many more databases and IIS Web Applications to manage ??
dbs

Visual Studio 2010 Tools for SharePoint
GREAT , far much better experience than 2007 BUT still few missing pieces.

You need to pre-plan a lot about what's the assembly name you need, feature naming etc in advance to be able to use it in real sense.

a) Any updation to output assembly name / feature name / namespaces etc will not be synced by Package Designer

b) Edit XML options is great but there is an issue. Once you start doing Edit XML, you are out of sync for any new changes. Now if you add any new feature / remove a feature , your manifest will not be synced with the changes any more. I am sure all of us is going to experience the ERA of 2006 where people use to hand create manifest files. lolz..

c) In case you want to deploy a Infopath as content type, you can't design a feature for it using VS 2010 sharepoint project as it doesn't allow you to include files in root folder of Feature. Elements Manifest/Files will always be in sub-folders, and that makes it difficult for deploying infopath as content type.

InfoPath 2010
Metadata control is not available
No easy way to publish browser enabled forms packaging as Content Type feature

Content Type Hub
Syncs content type across site collections but if you have an external template file, it will not be synced.

Also in case of infopath based content types, if template also got synced it will become non-browser enabled and will open in Infopath only and not in browser.

Silverlight new UI for creating new assets
Looks awesome until you get an error. Bad part is that it will give you error with correlation id and you cant select the HTML because its silverlight :)

Import WSP option in VS 2010
Try this , you will be amazed to see that Microsoft is dumping complete SharePoint content types in your solution. Too good but too much to clean.

Breadcrumb:
This is another crappy piece SP2010 has now. It works well mostly for sites but in case you go to Central Administration and navigate to series of screens. Check the breadcrumb now and only thing it shows is link to home page. You will need to go through all the those click again to reach the screen again.

2 comments:

Chaitu May 12, 2010 at 8:38 AM  

"Core Search Web Part configuration change:
Have you tried changing the Metadata properties or XSLT for the Core Search web part "
This is certainly a drawback, but it also has the feature to point to an XSL/T file anywhere which is quite a good feature.

"Content Query Web Part configuration:
In case you want to filter out items from the site collection based on its Content Type, Content Type Column is missing from filter list. You do have an option to filter items based on SINGLE content type."
Have you tried adding the Content Type to the AdditionalFilterFields property?

In 2010, we can no more save publoshing sites as templates. There are some back routes to accomplish this in 2007. Also configuration on ForeFront Manager is a real pain. You may need that for search property mapping configuration.

Third party vendors like Bamboo solutions etc are not supporting their solutions with SharePoint 2010 yet.

More later..

Anonymous,  August 24, 2011 at 11:19 AM  

for "Alert Templates customizations".

you can add your own template through object model or stsadm. what you have to do is based on the oob template, but you don't have to change oob template.