Sharepoint 2013

[redgiant]

yeah we were going to start going down the Sharepoint route where I am - it was touted as the next best thing and could do anything you wanted.

problem is no body could actually decide what to do with it.

It works as a good document management system and is go for collaboration etc but it just seemed to be expensive for any bespoke developments and so in the end it seemed to dissapear up it's own jacksie.

Would be interesting to hear from anyone who does use Sharepoint and what they use it for...

The project I mentioned before is a document management system for around 3,500 users across EMEA. In a nutshell it manages document configuration (i.e. versioning, gives each doc unique DocIDs, enforces naming convention and does several other doc config tasks), stores doc templates, has basic team sites which provide a way for users to see related documents in one place (to work on them collaboratively), allows users to search for documents using FAST search and lastly it has limited MySites (personal sites but these are not fully implemented i.e. it provides the user with a list of documents they have worked on - none of the more advanced features). Pretty standard approach but where support becomes difficult are the numerous UI changes that the clientco wants to the OOTB product.

[easyrider]

TBH I am not enjoying SP 2013 development much at all. The product requires 16GB RAM just to get a development box to run it for chrissakes! Then default functionality is that when the user clicks 'logoff' they are not properly logged out, instead MS presents a message to screen 'please close your browser to log out properly'. WTF. Unbelievable.
Requirement is to integrate the product with federated claims authentication (eg all users can use their facebook login). and this is also a undocumented complete PTA.
There is no documentation available for SP2013 administration (which is where we are struggling as we are .NET developers...) as the books have not been published.
Clientco want an extranet, intranet and internet all on SP2013, deadline is looming and we cannot get a SP 2013 admin in at all, so guess who has to push the site toward live ? Me.
A team of 3/4 developers for that lot. Thinking of bailing out!!!
Anyhow had an interview for a finance role which sounds promising. All custom .NET insurance SOA services, claims matrix and all that. Only downside seems to be that I have to relearn VB.Net from C#.