| We are a small company with big clients. Many of our clients commission multiple projects ranging from small, single person projects taking less than a week to large, team-based projects lasting months. Clients have supoort issues that need to be dealt with fast and they request quotes for enhancements or new projects which also take time. Work is developed using Visual Studio, tested internally and released for client testing and then deployed to production environments hosted by clients. As a company we need to be aware of what our capacity is in order to schedule work. The clients we work with require and deserve a dynamic approach to scheduling: our priorities have to be able to change week to week and day to day whilst we still deliver all of the work that we have committed to. We use elements of Scrum where they are appropriate and a more structured approach to allow us to set client expectations. Our objective is to implement SharePoint 2010, Project Server 2010 and Team Foundation Server 2010 (TFS) in order to manage the work and the development. Our intranet, external website and client extranet will all be hosted on SharePoint 2010. On top of SharePoint 2010 we will have Project Server 2010 to manage the work that needs to be done. The development tasks will be managed using TFS, as will version control, testing and builds. This is the perfect scenario for our business. There are, however, issues that are standing in our way: - How do we integrate Project Server 2010 and TFS 2010 so that management of projects are governed through Project server 2010 and development and testing tasks are managed through TFS 2010?
- How do we associate multiple projects, quote requests and support issues in Project Server 2010 and TFS 2010 with clients?
- How can we expose selected information in both Project Server 2010 and TFS 2010 to clients via an extranet for each client?
These are the initial objectives and issues that we are facing. We have the people with the capable skills and they have the hunger to update their skils and learn about all of these technologies. We also have the thirst, as a company, to deliver this solution for three reasons: - Our lives will be easier
- Our clients will be happier
- We will be able to work more efficiently
We will be pursuing these objectives and will, no doubt, encounter many more challenges. Bring 'em on - we'll get there. 
Alan Eardley - Project Manager, Creative SharePoint
|
| In our office there are 2 types of note-taker. The OneNote user and the MindManager. I am without doubt a MindManager. Why..?
Like a lot of people I've been "brain-storming" on black boards, flip charts and white boards since I was at school. It comes naturally. You start with a central topic and build from there but it's never been simple. Who hasn't been in a meeting with a notepad and started writing something below the first heading when the subject changes and you find you need a new heading and then another and then you're drawing little boxes in corners because the page looks like someone has been sick on it and there are arrows going from one end of the page to the other because that topic is actually related to that other one and frankly you've no hope of understanding it later.. Not just me surely?
Then you launch Mindjet's MindManager there it is - A blank page and one Central Topic. Several clicks later and you have the headings, a few more and you already have a useful "Map". It's easy and not only does it encourage you to be more organised but also concise. No one taught me how to use MindManager. It's as so obvious. I have used OneNote many times and I still don't know half of its features and I don't really want to, I know it's not for me. When I realised I could no longer read my own handwriting, I started writing my notes in Word.
The problem with both Word and OneNote is that you end up doing exactly the same thing as you would do on a notepad. Finding half way through that your headings are wrong, you cut and paste or create a new heading which is actually the same as another already on the page but frankly the other people in the meeting are too fast and you can't keep up anyway so you just keep typing. With MindManager if you find that your topics are under the wrong heading just drag them to a new location. No formatting issues (Word users you know what I'm talking about), no clicking on the page and finding you've created a new "box" randomly which isn't aligned with the others. No figuring out how to organise your Notebook's. No untitled pages which don't seem to even be in a notebook. Just maps. Simple, stylish maps. So what exactly IS a "map"? The only answer is "anything you want it to be".
My day starts when I launch MindManager. The first thing I open is my Dashboard Map to find today's Tasks, Issues and Events as well as the deliverables the team are due to complete for my clients. This information is actually all sitting on our intranet but MindManager for SharePoint pulls the details straight into the map and updates them every time I launch or refresh the page. I can even update the values in SharePoint from MindManager.
Today's Events show I have a workshop with a client in the morning and a meeting to discuss "next steps" in the afternoon. Maps at the ready I set off. The workshop starts off well and people's ideas are coming thick and fast. Because the agenda was agreed beforehand, I have already created a map with headings which correlate directly to the outcomes I need. I can add sub-topics as quick as people can fire them at me and the map is slowly building. We've discussed objectives for their new portal, issues and so on. What next? Time to start building the Site Structure. I know how hard it can be to visualise a portal or functionality that doesn't exist.
They're struggling a bit so I plug my laptop into the projector and as we discuss the best options for their new Site Structure I start mapping it out on the screen. Instantly they can see their thoughts taking shape but it's not quite right yet so we move things around; add more levels and eventually end up with a structure everyone agrees with.

Thankfully there are different formatting options so although I've set up "Site Structure" is a sub-topic I can format it within 2 clicks so everything below it is styled as a proper hierarchy. Previously I have facilitated workshops where an entire afternoon has been devoted to designing the new site structure. There's multiple flip chart pages being scribbled on or stuck together and no one can really see what's been agreed at the end of it. This takes an hour and the best bit is - now I don't have to go away, decipher all the notes, create the structure diagram using Visio or Word Art and then send it over to the sponsor to distribute and get feedback on. It's on the screen and everyone in the room has just approved it. Let's move on...
My next meeting is a smaller group. We're discussing the proposal they've had, deciding when and how to start workshops and agreeing other action points. Again I have pre-defined some topics but it's so easy I didn't really have to. I'm adding issues, their actions, our actions, dates and so on. I've already linked to the Proposal so there is no hunting for the document in Explorer, one click and it opens. We're discussing branding and they're mentioning sites and images they like so I add more hyperlinks and even search results for me to review at a later stage. Suddenly my map is huge but it's okay because I've already defined my own map styles so the different sections are clearly defined. Otherwise I could easily add a box around them for a more visual grouping.

The meeting comes to an end and for once I have not spent the entire time scribbling or tapping frantically panicking about legibility and how much work I'll need to do later to reorganise it all and if I missed anything. Everything I need has been captured with little fuss. My counterpart across the table asks me if it's not too much trouble to send over the minutes when I get back to the office the next day. "No problem" I say. I've already exported the Map as a PDF with an embedded Mindjet player and it is sitting in her inbox. I find workshops are a bit like my life, but with the existence of hair straighteners.....

Emma Thomas - Account Manager Creative SharePoint
|
| When I started working as a developer few years ago I imagined that I would spend all my days designing and coding complex enterprise solutions. As time passed I realized that significant part of any developer’s time is dedicated to deployment, google-ing the issues and bug fixing. No matter how perfectly a solution works on your machine there comes a time when this solution should be migrated to the end user's server and should function just as perfectly on their environment. I found for myself that deploying SharePoint solutions could be quite challenging especially when working alone on a clients’ site. There are some bullet points to be followed in order to avoid the explanation to your project managers - ‘But this worked so fine on my machine...”. In my practice I try to test the piece of work both in isolation from other components and integrated in the whole environment. Each new functionality might easily break a whole site no matter if it is custom code or styling change. It is also highly advisable to make a list of any exotic steps you take in the process of getting something working as you will need to replicate them on the client’s environment. It could be anything - changing access permissions, changing application pool settings, changing a master page – just make a note of it as you do not want to reinvent it when you are deploying to the live box! Another challenge is how to organize all post-deployment processes. A SharePoint solution would generally require some lists or subsites to be created or master page to be changed or web parts to be added onto a page. In case you are the one who is deploying and configuring you would easily set these up. However in some cases you just send a solution installer file and client is responsible to get it running. In that scenario you have the option to provide your client with a long comprehensive user guide what and how to configure and be almost 100% sure that end user will get something wrong. Instead I am trying to encapsulate in the solution as much of these post-deployment steps as possible. Within relatively short time and some efforts you could complete almost any post-deployment task in custom C# code and make deployment process less error-prone. So challenges in deployment process are numerous , it’s up to us to make it as smooth as possible and afterwards keep fingers crossed that our clients will like their new solution as much as we do. | Raya Markova - Consultant Creative SharePoint |
|
| It's about at this time in a product lifecycle that organisations look at the options available when upgrading and migration to new versions of their software applications and platforms. Many IT departments will be looking at upgrading their SharePoint environment from either 2003 or 2007 to SharePoint 2010. The important bit to note is that there’s no upgrade route from SharePoint 2003 to 2010! The only way to upgrade would be to upgrade the farm to 2007, then to 2010. Alternatively a content migration exercise should be assessed, 3rd party tools are available to assist with the migration of content.
To upgrade your environment the following is required:
• SQL 2005 with SP3 supported but not recommended, SQL 2008 is recommended • SharePoint 2007 SP2 with October Cumulative update • 64 bit hardware • Windows Server 2008 with SP2 / R2 • Minimum 8GB RAM, development environment will run on less RAM • SharePoint WCF hotfix required, this isn’t installed by the pre-requisites tool (http://support.microsoft.com/kb/976462)
There are 2 upgrade methods available, and 2 hybrid options: In place upgrade: • Uses existing hardware • The configuration and content databases are upgraded • Server offline during upgrade • Farm wide settings preserved • Customisations should be available after upgrade • Recommended for small or non-production environments
Database attach upgrade: • New hardware (farm) required • Upgrade multiple databases at a time • Server farm settings not kept (Audiences, InfoPath configuration etc...) • Customisations must be transferred / redeployed • Opportunity to consolidate multiple farms into one • Recommended if farm configurations are minimal
Hybrid 1: • Read only databases • Use database attach upgrade to preserve existing farm settings • Existing farm is put in read only mode • Create a new farm and attach all content databases • Recommended for small / medium / with minimal customisations
Hybrid 2: • Detach content databases from the farm • Use in-place upgrade to preserve farm settings • Central Admin and SSP databases upgraded • Once upgrade is complete, reattach DBs and upgrade content databases • Farm level settings are maintained • Content databases could be upgraded in a temporary farm, then ported over • Recommended for medium / large farms
Avoiding Upgrade Issues • Run the pre-upgrade check • Upgraded to SharePoint 2010 won’t fix a broken farm • Coalesce the farm, make sure no users are using the farm while the upgrade takes place • Perform a trial upgrade on a test farm first, important! • Use STSADM / Powershell scripts to attach database • Remember to backup all content, and ensure backups are working!
Technet supporting information: http://technet.microsoft.com/en-us/sharepoint/ee517214.aspx Upgrade Planning: http://www.microsoft.com/downloads/details.aspx?FamilyID=e8b66eb3-27c7-4a39-a2e1-3e7d18b12ee1&displaylang=en | David Hendry - Lead Consultant Creative SharePoint |
|
| The biggest advantages to moving from a third party RIA framework to Silverlight is that it is a fully supported framework. It is a technology Microsoft are pushing at full force to achieve market supremacy and that it has full integration with .NET
Silverlight is based on the .NET framework meaning that integration with .NET applications is a simple matter. With a web service on the backend to feed the Silverlight control, extraordinary feats of usability and functionality can be developed to meet any and all business requirements.
For the people afraid of the user base of Silverlight not being high enough to implement a solution in it, firstly the technology is rapidly growing every week, the number of users adopting the technology is also greatly on the rise. Silverlight offers a very fluid “graceful degredation” to another technology of the developer or companies choice for those who don’t have the Silverlight plugin installed.
Silverlight is aimed at two groups for development, firstly the creative teams add the animation, graphics and effects using “Microsoft Blend” as a creative tool and the backend developers create the functionality and integrations using “Visual Studio”, Microsoft have created blend with the idea that the Silverlight solutions can be loaded in blend or VS independently and can share the same solutions so both developers and creatives can work on the same solutions. SharePoint and Silverlight.
With the release of the new versions of SharePoint 2010 and Silverlight 4, it is now possible in Silverlight to display and manipulate SharePoint information and functionality without relying on external connections to webservices so much. New advances have been made to Silverlight with the inclusion of a “Silverlight Client OM assembly” this effectively allows developers to directly integrate their applications into SharePoint.
SharePoint development in the years to come will be very Silverlight oriented and solutions based on SP2010 will increasingly provide Silverlight interfaces as users want the slickest integration they can get and gold partners are willing to provide it! | Benjamin Dean - Developer - Creative SharePoint |
|
| Since working for CSP, lots of my projects have included branding SharePoint solutions. Branding SharePoint primarily consists of Master Pages, Page Layouts and the web parts. However the purpose of this particular blog article is to look more closely at Page Layouts. So what are page layouts? I would describe a page layout as something that sits within a SharePoint web part page, which makes its appearance slightly different. For example lots of pages have similar layouts. As opposed to creating a new page from scratch, A Master Page coupled with a Page Layout will provide the building blocks required to populate a stylised page with relative ease. Within SharePoint you can build as many layouts as you wish, but best practice would dictate that you promote reusability by making layouts flexible and thus keeping layouts to a minimum. For example as opposed to making one layout to serve one purpose, make a layout to serve two or three purposes. What are the challenges with creating page layouts? I’ve generally found as long as the guidelines are adhered too, for example layouts are published, approved and tested, there are no major issues. My biggest personal challenge was trying to manipulate something displayed within the Master Page depending upon which page you’re on, (this could only be controlled by the Page Layout). However this was at a point when I wasn’t familiar with the good old asp content place holder tags. I soon realised how easy it actually was! Are there any major differences between MOSS and 2010? From personal experience I haven’t found any major differences between page layouts on MOSS and 2010, but I would look out for sporadic issues such as check boxes randomly appearing in IE6! So in summary, page layouts promote reusability, flexibility and generally facilitate the building blocks required to peace pages together. | Adam Dale - Consultant - Creative SharePoint |
|
| It was the start of my epic voyage into what was supposed to be the most exciting thing to happen to collaboration “ever” and “a new way for teams to work together”. It only seems like yesterday when I first took the Team Services and SharePoint Portal Server 2001 CD from the brown jiffy bag and put it into my brand new Windows Server 2000 Drive.
WOW, how things have changed! Not just in the way we use SharePoint as an end user, but also how we, as a SharePoint specialist, take for granted features such as workflow and content management.
As a product, SharePoint has become enormous from where it was nearly 10 years ago. It really became usable in 2003 when suddenly you could build an Intranet and people could search for things and get “some” meaningful results. The day I installed the BETA of MOSS 2007 was when I realised that persevering with this technology had all been worth it.
Suddenly it sold itself on features alone and it started to become a hot topic; even my family members started to use it at their work places. No one could have predetermined the success that this version has bought about. Now with the latest version of SharePoint being released in May (SharePoint 2010) we are in for some exciting times ahead.
So, “Why do we all use SharePoint”? Does it help us all become more organised? Does it stop us from saving files directly on to our Desktops? Will it prevent IT departments from buying more and more storage?
Perhaps, I think the question you ought to ask is “Where next for SharePoint”? | Oli Stickley - MD Creative SharePoint |
|
View in Web Browser /_layouts/VisioWebAccess/VisioWebAccess.aspx?listguid={ListId}&itemid={ItemId}&DefaultItemOpen=1 0x0 0x1 FileType vdw 255 Compliance Details javascript:commonShowModalDialog('{SiteUrl}/_layouts/itemexpiration.aspx?ID={ItemId}&List={ListId}', 'center:1;dialogHeight:500px;dialogWidth:500px;resizable:yes;status:no;location:no;menubar:no;help:no', function GotoPageAfterClose(pageid){if(pageid == 'hold') {STSNavigate(unescape(decodeURI('{SiteUrl}'))+'/_layouts/hold.aspx?ID={ItemId}&List={ListId}'); return false;} if(pageid == 'audit') {STSNavigate(unescape(decodeURI('{SiteUrl}'))+'/_layouts/Reporting.aspx?Category=Auditing&backtype=item&ID={ItemId}&List={ListId}'); return false;} if(pageid == 'config') {STSNavigate(unescape(decodeURI('{SiteUrl}'))+'/_layouts/expirationconfig.aspx?ID={ItemId}&List={ListId}'); return false;}}, null); return false; 0x0 0x1 ContentType 0x01 898 Edit in Browser /_layouts/images/icxddoc.gif /_layouts/formserver.aspx?XsnLocation={ItemUrl}&OpenIn=Browser&Source={Source} 0x0 0x1 FileType xsn 255 Edit in Browser /_layouts/images/icxddoc.gif /_layouts/formserver.aspx?XmlLocation={ItemUrl}&OpenIn=Browser&Source={Source} 0x0 0x1 ProgId InfoPath.Document 255 Edit in Browser /_layouts/images/icxddoc.gif /_layouts/formserver.aspx?XmlLocation={ItemUrl}&OpenIn=Browser&Source={Source} 0x0 0x1 ProgId InfoPath.Document.2 255 Edit in Browser /_layouts/images/icxddoc.gif /_layouts/formserver.aspx?XmlLocation={ItemUrl}&OpenIn=Browser&Source={Source} 0x0 0x1 ProgId InfoPath.Document.3 255 Edit in Browser /_layouts/images/icxddoc.gif /_layouts/formserver.aspx?XmlLocation={ItemUrl}&OpenIn=Browser&Source={Source} 0x0 0x1 ProgId InfoPath.Document.4 255 View in Browser /_layouts/xlviewer.aspx?list={ListId}&id={ItemId}&DefaultItemOpen=1 0x0 0x1 FileType xlsx 255 View in Browser /_layouts/xlviewer.aspx?list={ListId}&id={ItemId}&DefaultItemOpen=1 0x0 0x1 FileType xlsm 255 View in Browser /_layouts/xlviewer.aspx?list={ListId}&id={ItemId}&DefaultItemOpen=1 0x0 0x1 FileType xlsb 255 |
|
|
|
| | Welcome to Creative SharePoint Blogs. Here you will find the ideas, issues, solutions and thoughts of our team. Please feel free to add comment and opinion in response to these posts. |
|
|
View in Web Browser /_layouts/VisioWebAccess/VisioWebAccess.aspx?listguid={ListId}&itemid={ItemId}&DefaultItemOpen=1 0x0 0x1 FileType vdw 255 Compliance Details javascript:commonShowModalDialog('{SiteUrl}/_layouts/itemexpiration.aspx?ID={ItemId}&List={ListId}', 'center:1;dialogHeight:500px;dialogWidth:500px;resizable:yes;status:no;location:no;menubar:no;help:no', function GotoPageAfterClose(pageid){if(pageid == 'hold') {STSNavigate(unescape(decodeURI('{SiteUrl}'))+'/_layouts/hold.aspx?ID={ItemId}&List={ListId}'); return false;} if(pageid == 'audit') {STSNavigate(unescape(decodeURI('{SiteUrl}'))+'/_layouts/Reporting.aspx?Category=Auditing&backtype=item&ID={ItemId}&List={ListId}'); return false;} if(pageid == 'config') {STSNavigate(unescape(decodeURI('{SiteUrl}'))+'/_layouts/expirationconfig.aspx?ID={ItemId}&List={ListId}'); return false;}}, null); return false; 0x0 0x1 ContentType 0x01 898 Edit in Browser /_layouts/images/icxddoc.gif /_layouts/formserver.aspx?XsnLocation={ItemUrl}&OpenIn=Browser&Source={Source} 0x0 0x1 FileType xsn 255 Edit in Browser /_layouts/images/icxddoc.gif /_layouts/formserver.aspx?XmlLocation={ItemUrl}&OpenIn=Browser&Source={Source} 0x0 0x1 ProgId InfoPath.Document 255 Edit in Browser /_layouts/images/icxddoc.gif /_layouts/formserver.aspx?XmlLocation={ItemUrl}&OpenIn=Browser&Source={Source} 0x0 0x1 ProgId InfoPath.Document.2 255 Edit in Browser /_layouts/images/icxddoc.gif /_layouts/formserver.aspx?XmlLocation={ItemUrl}&OpenIn=Browser&Source={Source} 0x0 0x1 ProgId InfoPath.Document.3 255 Edit in Browser /_layouts/images/icxddoc.gif /_layouts/formserver.aspx?XmlLocation={ItemUrl}&OpenIn=Browser&Source={Source} 0x0 0x1 ProgId InfoPath.Document.4 255 View in Browser /_layouts/xlviewer.aspx?list={ListId}&id={ItemId}&DefaultItemOpen=1 0x0 0x1 FileType xlsx 255 View in Browser /_layouts/xlviewer.aspx?list={ListId}&id={ItemId}&DefaultItemOpen=1 0x0 0x1 FileType xlsm 255 View in Browser /_layouts/xlviewer.aspx?list={ListId}&id={ItemId}&DefaultItemOpen=1 0x0 0x1 FileType xlsb 255 |
|
Thu, 29 Jul 2010 09:52:20
Thu, 29 Jul 2010 09:44:38
Thu, 29 Jul 2010 08:49:14
Thu, 29 Jul 2010 08:20:39
Thu, 29 Jul 2010 08:16:51
Thu, 29 Jul 2010 08:16:51
Thu, 29 Jul 2010 08:11:29
Thu, 29 Jul 2010 08:08:13
Wed, 28 Jul 2010 15:57:34
Wed, 28 Jul 2010 15:35:12
Wed, 28 Jul 2010 15:34:03
Wed, 28 Jul 2010 11:46:56
Wed, 28 Jul 2010 11:41:12
Wed, 28 Jul 2010 11:31:00
Wed, 28 Jul 2010 11:29:18
Wed, 28 Jul 2010 09:19:20
Tue, 27 Jul 2010 13:16:28
Tue, 27 Jul 2010 11:27:37
Tue, 27 Jul 2010 11:24:04
Tue, 27 Jul 2010 11:21:11
|
|
|