To Backup or Not to Backup ... The Question is How

1. Run > cmd (depending on your configuration you might have to run the cmd prompt as a local admin)
2. cd "C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\BIN"
3. stsadm -o backup -url http://mysite.com -filename C:\temp\mysitefile -overwrite
4. You are DONE!

...And Your Data Will Be Held in a Secure Location on a Remote Island - Oops..  I Mean Server

To restore a site backup on another server:

1. Login to Central Admin
2. Create a new web application under the "Application Management" tab
   • Once the site has been successfully created, there is no need to create a site collection because we are going to load it from the backup file
3. Run > cmd > cd "C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\BIN"
4. stsadm -o restore -url http://mynewsite.com -filename E:\temp\mysitefile -overwrite
5. Once the restore has complete head back into the Central Admin > Application Management tab and choose "Policy for Web Application" and add a user account to login to the new restored website.

Forrester Research Inc. Gains Insight On SharePoint from Steve Ballmer

I had the pleasure to sit down with Steve Ballmer for an interview at the Microsoft SharePoint conference in Las Vegas this week. My research team at Forrester spends a lot of time thinking, researching, and writing about the future of information work. So getting Steve’s view on SharePoint’s decade-long evolution from a basic document sharing application to a broad platform for rapid application development, intranet and internet sites, content management, search, social computing, and composite applications, was something I couldn’t pass up.

Unfortunately, pre-taped interviews are like a ball of pizza dough. They start life with different ingredients, get molded into interesting shapes through the discussion, until they’re eventually pounded and rolled out by communications professionals into something utterly flat and lifeless. This is not a ding on Microsoft, Forrester has its share of communications pros with flour on their hands too. For the video version, click here. But let’s consider several highlights that did and didn’t make the video. Consider that Steve:

• Compares SharePoint to the PC… “In my own mind I compare [SharePoint] to the PC, the PC started off life as a spreadsheet machine, then became a programming machine, a word processing machine, [SharePoint is] a general purpose infrastructure that connects people to people and people to information,” says Steve. Is it just me, or does this analogy say a lot about the scale and scope of Microsoft’s ambition for SharePoint? Of course the millions of people licensed on SharePoint today pales in comparison to the billions of people using PCs. But the recipe for SharePoint does resemble the recipe for the modern-day PC to some extent: mix programmability, broadly available developer tools, common user experience conventions (aka, the “ribbon” interface), and useful applications for communicating, reading, writing, and storing information.
• Doubles down on Windows Phone for mobile access to SharePoint… I asked Steve about mobility, specifically whether the SharePoint team is targeting competing smart phones, like RIM’s Blackberry, or Apple iPhone, with dedicated client applications. The answer was “no,” paired with a big Steve Ballmer style smile.  I thought this a fair question as my colleague Ted Schadler’s Workforce Technographics report recently showed that while only 11% of information workers in companies use a smart phone for work, the number of collaborative applications people use on these devices, and the number of locations workers use these apps from are both very high and growing. Combined with decreasing prices for smart phones, it feels like we’re on the brink of a tipping point where smart phones become a ubiquitous platform for enterprise computing. For now, Steve seems willing to let others build iPhone apps for SharePoint. Is this a mistake? Time will tell, but after a week in Vegas of dropped calls and late delivery of SMS messages on my own iPhone, it’d be a big mistake to call the smart phone race prematurely.
• Positions SharePoint as a serious rapid application development platform. A big focus of the conference, and the interview, was on developers. Steve disagreed with my argument that SharePoint is not a “serious” development platform in the eyes of IT architects and developers. He countered, “I disagree … I think SharePoint is considered a very serious development platform for rapid application development.” What struck me was his take on the opportunity presented by “the many applications companies build with one man year or less of development.” Having worked in or consulted with IT departments for the majority of my career, I can’t tell you how many that is, but I’m confident saying it’s a whole lot. Many of these apps are built on technologies like Microsoft Access, Visual Basic, Lotus Notes, Java server pages, Active Server Pages, and more. So while high-end middleware companies duke it out for the comparatively few large, transactional, and process-heavy apps of the world, Steve appears completely content for now capturing even a portion of the smaller apps market. To get there, Microsoft must convince enterprise architects that tools like InfoPath Forms and SharePoint Designer can be used without taking down entire SharePoint server farms, something Microsoft has ostensibly failed to do thus far. Is SharePoint 2010 the answer? Won’t know til the Beta is underway in November. But given Steve’s talk of creating a SharePoint “sandbox in the cloud,” my bet is we’ll see lots of liberal arts programmers forged into “SharePoint Developers” over the next decade (whether enterprise architects like it or not).

Is the SharePoint/PC analogy a stretch? Is a dedicated SharePoint mobile client for competing devices a missed opportunity for Microsoft? Will SharePoint 2010 finally lead to the next generation of liberal arts “developers” building small, but useful apps? I’ve got my ideas, what about you?

Deciding to Get Started

So you have decided to entertain the concept of developing a published CMS (Content Management Systems) website built on the SharePoint technology, and perhaps you are unsure of any pros and cons with the technology or need a good solid place to begin research. If you are just starting with the SharePoint development you do have a long road to travel and the road can very rough at based on a direction that has been chosen. I have been primarily developing in SharePoint for 2 years now and have fought hard for the toolbox library of custom web parts that I have today, but with every step forward more opportunity and understanding of the true power of SharePoint framework, especially using the framework for customized or template CMS websites.

Hearing Mike Fitzmaurice

I was at the 2009 SharePoint Summit in Montreal and had the amazing opportunity to listing to Mike Fitzmaurice – Nintex, present a talk on "The Evolving Market around SharePoint Products and Technologies". Within first slide, he had made a statement that completely summed up the SharePoint framework for me and really started to make me think about using the product differently and to that effect, appropriately. The statement was very simple and stated that "SharePoint is an Ecosystem". This statement turned me around because instead of thinking "what is SharePoint going to do for me?" I started thinking "How can I start developing my own ecosystem on top of the SharePoint engine?" And that leaves me where I am today. I have now been building various websites within SharePoint and have a collection of valuable customized web parts that I can deploy and reuse and SharePoint site. Throughout the course of this development blog I will be releasing concepts that represent different tools in our web part library to help make any readers understand the approach and begin using these tools within their development.

Planning and Understanding

Beginning a SharePoint site of any size takes a large amount of understand of the SharePoint hierarchy of sites, sub-sites, content types, folders and list items. Understanding the appropriate approach with this hierarchy and assigning the appropriate relations and metadata, your development cycle will completely benefit from. Take the time to plan and understand the requirements in relation to the SharePoint core functionality.

Other Links for Blogs

There are a lot of really good articles and blog postings out and from time to time I intend to share links to related topics that helped improve our understanding when developing parts for SharePoint. Being as this is the initial blog post, I will quickly share our recent links to help any up and coming SharePoint developers get started. ENJOY!!

• http://www.telerik.com/help/aspnet-ajax/moss-overview.html
• http://stevepietrek.com/2007/07/28/turn-off-sharepoint-custom-error-messages/
• http://sharepoint.microsoft.com/blogs/mike/Lists/Posts/Post.aspx?ID=3
• http://www.sharepointnutsandbolts.com/2008/06/spdatasource-every-sharepoint-developer.html
• http://blogs.msdn.com/sharepointdesigner/archive/2007/04/24/spdatasource-and-rollups-with-the-data-view.aspx
• http://sharepointdata.blogspot.com/2009/04/bind-list-items-using-spdatasource.html
• http://www.supershareware.com/software/sharepoint-themes.html
• http://www.u2u.info/Blogs/Patrick/Lists/Posts/Post.aspx?ID=1765
• http://sharepointmagazine.net/technical/development/writing-caml-queries-for-retrieving-list-items-from-a-sharepoint-list
• http://www.codeproject.com/KB/aspnet/SPCustomSearchResults.aspx
• http://theengineroom.provoke.co.nz/archive/2007/05/11/creating-a-custom-search-results-page-for-a-searchresults-aspx-windows-sharepoint-services-wss-site.aspx
• http://blogs.msdn.com/kaevans/archive/2007/04/26/code-blocks-are-not-allowed-in-this-file-using-server-side-code-with-sharepoint.aspx
• http://msdn.microsoft.com/en-us/library/aa543347.aspx

Kyle Pearn,
akira systems