Personalization VS Customization

Just refreshing the idea of Personalization and Customization

Personalization is a process where a user create a new view for any web part on his personal View.

Customization is a process where a user change a Shared view of the page by using the appropriate permissions.

The default page is Shared view which can be changed by editing the page property DefultViewPersonal on the aspx page code.


Types of Web Parts

Just wanting to refer here that there are two types of web parts

  1. Static web parts

Static web parts are placed outside the Web part zone on the web part zone and the user can be change it behaviors and properties on the browser. Static web part properties are stored within the aspx page and will not saved to content Database.

  1. Dynamic web parts

Dynamic web parts are placed in web part zone and all its properties are stored within the content Database. A user can change its behavior and properties and the changes will be saved to Content Database. Dynamic web parts can also be connected to other web parts on the site or page.

Resource Files for SharePoint Web Parts

If we have a web parts that stores Resources like language files or images in its RESX files we can save these files to the virtual server where we need to install the Web part in two ways;

  • If the DLL is placed in \inetput\wwwroot\Bin then and place the Resource files in Virtual Server \inetput\wwwroot\wpresources directory.
  • If the DLL is placed in the GAC. Then the Resource files must be places in <local drive>C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\wpresources directory.

Leaving INTECH & Joining Xavor from September 1st 2006

Believe me or not I am going to join XAVOR as a Mixture of SharePoint Consultant and SharePoint Developer. I remember my Final project days at UMT in 2002 when I went to Xavor to talk to one of the Sr. PM there about the project. I don’t know why I never thought about joining the company at that time. This was because of my intentions to finish the project which I finally did in January 2003 and got Job at ISA soon after that. The other important thing about this job for me is that I never applied for this job. One of my eWorx colleagues Wajhi who is SSE there forwarded the CV. I got a mixture of technical and non technical interview with three guys few days back. They offer me the position which I accepted finally and sign the papers. I would like to thank those people who helped me to find a career in Collaboration technologies e.g. EPM and SharePoint. I worked as EPM guy for an year now but things are starting to change. I am going to back to my favorite topic which I never stopped working even working on EPM stuff.

This job is also the result of my MOM’s prayers and efforts. She always worked hard on me and guided me to be on the right track. And I will always love and respect her. Thanks to my wife who inspired me and never felt bored talking to me about SharePoint Stuff which she never understand (She is not IT only know Email and MSN).

This is not the end. I think I have destiny to grow and will grow as day progresses. I will need more hard work and vision to go through the next phase which is moving towards working as Sr. Consultancy on SharePoint and EPM technologies.

Last but not least I thank myself to never stop dreaming about the SharePoint Job and always look for things and material to read about SharePoint.

The company I am leaving is

The company I am joining is



VSTO and SharePoint – A winning and Possible Profitable Combination

by Bill Sheldon,

During my RND on VSTO I Found this article about VSTO and SharePoint.

VSTO and SharePoint–A Winning and Possibly Profitable Combination

In my previous column "Ripple Has Become a Wave" (, I invited readers to email me reasons why people might still be using COM in the business logic behind their Web sites. I received only one email. In it, the reader said that one reason might be that, "MS never updated the Office COM interface to .NET, requiring you to completely re-engineer your methods for providing Excel based reports to users or just use Interop." The reader went on to mention that "you have plenty of options to get around this limitation." I got the impression that the reader might not have a solid understanding of what Microsoft had and hadn’t done regarding Office and its interaction with .NET.

I last mentioned the Visual Studio Tools for the Microsoft Office System (VSTO) in my August 2005 column "The Shifting Sands of Technology" ( In case you’re unfamiliar with VSTO, it’s the replacement for COM interop. With VSTO 2005, you do anything that you can do with interop. And with a custom task pane, VSTO’s capabilities go a long way beyond interop’s capabilities. I was recently involved in a project for a small company in which we added custom research capability to Microsoft Word. Because we followed the Microsoft standards for publishing the actual search interfaces, the custom search was available not only from our own pane in Word but also from the research pane in any Microsoft Office product and in Microsoft Internet Explorer (IE) once you installed the search interfaces.

Microsoft Office 2007 (previously code-named Office 12), which Microsoft plans to ship by the end of this year, will bring enhancements to VSTO. In addition, developers will be better able to use the Windows .NET Framework to manipulate Office 2007 products. Some of the changes coming to products such as Microsoft Outlook are just amazing. You can read about Outlook’s design changes and changes in programming capabilities in Sue Mosher’s "A New Look for Outlook 12" ( In addition, you can view slides that specifically address the new programmatic features in Outlook at

VSTO currently has two disadvantages, which Microsoft will hopefully eliminate or at least minimize in Office 2007. The first disadvantage is that VSTO capabilities in Outlook 2003 are limited compared with its capabilities in Word 2003 and Microsoft Excel 2003. The second limitation is that clients need to have Office Professional Edition 2003 installed for VSTO to operate. VSTO isn’t available to clients using Office Standard Edition 2003.

In "The Shifting Sands of Technology," I discussed how VSTO impacts the development of Windows Forms applications, but I didn’t discuss the impact that Office 2003 is having on Web applications. Although I briefly touched on this topic in my April 2004 column "SharePoint Portal Server 2003 and InfoPath–A Dynamic Duo" (, that column mainly focused on Microsoft Office InfoPath 2003. Thus, I want to spend more time discussing SharePoint.

SharePoint lets you upload, version, and manage Office documents and other project documents straight out of the box. SharePoint, which is the focus this month’s issue of Windows IT Pro magazine (, can be confusing in that there are actually two SharePoint products: Microsoft Windows SharePoint Services and Microsoft Office SharePoint Portal Server 2003. The differences between the products lie in which Microsoft product team owns the product and what each product costs and does.

In short, SharePoint Portal Server is a product from the Microsoft Office team and requires separate licensing associated with Office. Many companies that use SharePoint Portal Server get their licensing through their enterprise Office licensing. Not surprisingly, the SharePoint Portal Server home page is on the Office site at

SharePoint Portal Server builds on Windows SharePoint Services, which most people consider the core SharePoint product. Essentially, Windows SharePoint Services creates independent project sites and SharePoint Portal Server ties these sites together under a common portal. SharePoint Portal Server also provides other features, which you can read about at;EN-US;830320.

Windows SharePoint Services is a component that’s part of and included with all editions of Windows Server 2003. Thus, you’ll find the Windows SharePoint Services home page on the Windows Server site at Windows SharePoint Services lets you create project-based Web sites and is used in other Microsoft products. A good developer-focused example is Team Foundation Server (TFS). The TFS integration with Windows SharePoint Services is what sets up your project site so that you can combine your source code repository with a repository for project-related documentation.

Windows SharePoint Services’ versatility at providing a standard Web interface for project teams has made it synonymous with collaboration. The Microsoft Small Business Server ships with Windows SharePoint Services already enabled so that small businesses can easily share internal documentation. Windows SharePoint Services is an "intranet in a box" for companies that are looking for a low-cost internal tool to manage their shared documents.

Microsoft recognizes that Windows SharePoint Services is an important tool in its collaboration platform and a direct competitor to existing collaboration tools, such as Lotus Notes/Lotus Domino. Perhaps that’s why Microsoft recently purchased Groove Networks, a leading provider of workgroup collaboration software. Microsoft will be working to better integrate Windows SharePoint Services with tools such as Microsoft FrontPage and InfoPath. These improvements will make Windows SharePoint Services a more powerful platform by the end of this year. Working with VSTO, Windows SharePoint Services, and other Office system tools to develop collaboration, messaging, and other information-management solutions might even help your company net part of a $148 billion market, according to Microsoft Partner Capacity Research ( For more information about Windows SharePoint Services as a part of a collaborative environment, check out TechNet’s collaboration page at