SharePoint & it's Competitors

Shawn from CMS watch has a very interesting point in the latest trend for competing with (by alternate CMS systems) SharePoint head on. Though at these times, the best bet for them is to move along.

"As any product gains in popularity, especially if it's seen as dominant, you tend to see more and more news about alternatives that inevitably get dubbed "killers." The news media and the product's competitors are continually trying to best the dominant solution and predict a product's demise. We can see this clearly with the iPhone and, as Seth Gottlieb pointed out, "who isn't working on a SharePoint killer?" But in many cases, these "killers" are only hopefuls with virtually no evidence they could harm a fly."

Read more here

How to get Raw HTML from a Page : System.Net.WebResponse

Retrieving a page's HTML can sometimes be necessary in applications. You could be filling columns for actual meta data of sites or may retrieving remote web sites for specific content. It's require very simple code to do all the stuff

// pass the site URL
string strHTML = Strip(Request(strWebURL + "/" + file.Url, "GET"));

//The Request Function
String Request(String uri, String verb)       {

            WebRequest request = WebRequest.Create(uri);
            request.ContentType = "application/x-www-form-urlencoded";
            request.Method = verb;
            request.ContentLength = 0;
            WebResponse response = request.GetResponse();
            if (response == null) return null;
            StreamReader reader = new StreamReader(response.GetResponseStream());
            return reader.ReadToEnd().Trim();
        }

// The Strip function, to remove style, scripts & Html tags from the text

 public string Strip(string text)
        {
            text = Regex.Replace(text, "", "", RegexOptions.Singleline | RegexOptions.IgnoreCase);
            text = Regex.Replace(text, "", "", RegexOptions.Singleline | RegexOptions.IgnoreCase);
            text = Regex.Replace(text, @"<(.|\n)*?>", string.Empty);
            text = text.Replace("\r\n\t", " ").Replace("\n", " ").Replace("\r", " ").Replace("\t", " ");
            return text;
        }

// That's All

Making Sense of the SharePoint 2010 Pie



With so many blogs now on SharePoint, it has become more like a box of choclates, You never know what you're gonna get.

Mark bower in his article has explained the Sharepoint 2010 pie, here is a repost

"A new version of SharePoint gives us an updated SharePoint Pie. Like the SharePoint 2007 pie, SharePoint 2010 has six slices, most subtly renamed."

Collaboration becomes Communites
  • Renamed, perhaps to emphasize the intent to make SharePoint 2010 a more social experience.
  • Aim to empower people to work together in new ways through ad-hoc collaboration in communities of interest or in work-group communities
Content Management becomes simply Content
  • Does this imply a de-emphasis of SharePoint as a serious content management platform? I think not. I suspect this is a desire to move people away from traditional equation of content management to web content management, towards a broader view of content management…covering document management, records management as well as web content management.
Search stays as Search
  • What’s publicly known right now is inclusion of FAST technologies and improvements to people and line of business application search. At the top end of the market Microsoft is loosing out to the likes of Autonomy, and they’ll want to put the brakes on that.
Business Intelligence becomes Insights
  • The new name emphasises the business impact, rather than the technology function, which is powerful. Perhaps again, Microsoft is taking a broader view of this capability, thinking about getting insights in a more human way, through crowdsourcing or collaborative approaches, as well as simply through data crunching. Just speculating.
Business Process and Forms becomes Composities
  • Composite Applications being a more corporate-friendly word than mashups.
  • The idea once again I think is to broaden the category to include other user and developer tasks of creating custom business solutions through mashing together web parts, forms and processes.
Portal becomes Sites
  • This moves away from positioning SharePoint as an Intranet Portal product to being a product capable of serving as a intranet, extranet or Internet site

SharePoint Object Hierarchy: How it all fits together

A very useful article by Martin Kearn about How objects in SharePoint relate to each other? It gives you a bird eye view of the country called SharePoint.

From the article:
"I often get asked to clarify how all of the objects in SharePoint relate to each. For example, people do not always understanding the differnence between a site collection and a site or how a web application and content database relate to each other.

To help out, I have produced this diagram which I think explains all of the main SharePoint objects and how they relate to each other. I did consider writing some kind of description to go with this, however I think it is better that I just do my best to answer any questions via the comments. If there are any re-occuring themes, I'll add to this article and try to explain them."