Pages

Tuesday, 28 June 2011

SharePoint Questions and Answers

1. What is the SharePoint..?
a. Easily create a Collaborative Site.
b. Efficiently manage Information. (Documents, Information storage, version control, schedule.)
c. Automate Business Processes.(Common project workflow, SharePoint workflow)
d. SharePoint is .Net based Technology. That is used to create dynamic and secure websites without writing any code and design, any user interface, using predefined site templates
e. SharePoint site allow information may be stored, shared and searched in secure manner.
f. SharePoint team members to connect and exchange information in a collaborative manner.
g. SharePoint helps to centralize enterprise information for efficient


2. What is the concept of ghosting and unghosting in SharePoint?
a. Pages which are loaded from the file system are termed as ghosted pages.
b. If the page data is loaded from the content database it’s termed as unghosted pages.

3. What is the web Application..?
A web application is an application that is accessed over a network such
as the Internet or an intranet. To provide the some services to end users.

4. What is a Portal..?
a. A portal is a central place for making all types of information accessible to an audience of varying range.
b. Portal refers to a web site or service that offers a broad array of services, such as e-mail, forums, search engines and online shopping malls etc….

5. What is the web Application in SharePoint..?
A SharePoint Web Application is an IIS website that has been configured to run a SharePoint site. When you create a new Web Application with SharePoint, it creates a new database named a Content Database.

6. What is the Site and Site Collection..?
A SharePoint Site is a container for content. Every site must be provisioned (created) within an existing Web Application. It must be created inside the scope of a Site Collection. A SharePoint Site Collection is a container of SharePoint Sites, and requires a Top-Level Site.

7. What is the master page..?a. Master pages provide the look and feel and standard behavior that you want for all of the pages in your site. Together with content pages, they produce output that combines the layout of the master page with content from the content page.
b. Do not edit the default.master file directly in the <%System Drive%>Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\TEMPLATE\GLOBAL\ folder.
c. In SharePoint designer set to "/_catalogs/masterpage/default.master"

8. What is the Content Typea. SharePoint Content Type is a flexible and reusable type definition in SharePoint that defines the item template in SharePoint Lists and Libraries. We can define columns of items or document types or document templates, then associate them to a list or library simultaneously
b. Content types
c. Business Intelligence (Dashboard Page)
d. Document Content Type (Basic Page, Document, Form, Master Page, Picture)
e.Folder Content Types (Folder, Discussion)
f.List Content Type (Announcement, Contact, Issue, Item, Link, Message, Task)
g.Special

9. What is the Site column..?
A Site Column is a reusable column definition that can be used across multiple lists. Once you have created a site column, you can use it to create Lists or Libraries. You can update a Site Column in a single place, and it affects all the lists where the Site Column has been used.

10. What is the different between List and library..?a. List Provide a basic structure to organize data and Libraries Provide a basic structure to store documents or other files.
b. List will allow you to store a number of items such as, staff details ext…
c. Libraries are really for holding documents, files and images ext…

11. What is the difference between Site Page and Application Page..?a. Site pages support page customization. Examples of site pages include the home page (default.aspx) for a site as well as the pages associated with lists and document libraries, such as AllItems.aspx, NewForm.aspx, and EditForm.aspx.
b. Site pages are pages which live in the SharePoint database.
c. Site pages are customized pages and are saved in to content database. So when you use the SharePoint designer to make custom changes it saves the changes in to content database.
d. Application pages do not support customization, which gives them two distinct advantages over site pages. First, each application page is always compiled into a single DLL so that it performs and scales better than a site page. Second, application pages are allowed to have in-line code.
e. Application pages are pages which live on the server's file system. Application pages usually also execute code, but not always.
f. If you want to make generic pages in a site collection which will be used by everyone, like for instance the 'Settings.aspx' page then you need to use application pages.
g. Application pages are stored typically in the file system of the front-end Web server within a directory "c:\program files\common files\Microsoft shared\web server extensions\12\TEMPLATE\LAYOUTS". settings.aspx, viewlsts.aspx, etc.
h. Application page never run in safe mode and they can contain inline code.

12. What is the difference between site template and site definition..?a. Site template (STP) is just a snapshot of the current state of a site.
b. Which another site is creating from so it will have the same customizations.
c. Site template in their most basic form is easy to create.
d. No server touch:Site template doesn’t require access to the server.
e. Easy to create:
f. Single file deployment: Because everything you need is in the single STP file, you don’t have to worry about putting the file.
g. Site Definitions are the foundations on which all sites and user templates are built.
h. Site Definition is collection ox XML and .aspx file.
i. Site Definitions are predefined components needs to be included when a site was created in SharePoint server.
j. Site Definition contains information of Web Part , Lists, Features and navigation bars to be included in the site.
k. The configuration of this site definitions are defined in XML file which is available in

C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\1033\XML folder.

13. what is difference between GAC directory and BIN Directory.?
Assemblies deployed to the GAC have full trust, while the assemblies deployed to the bin folder runs with the trust level specified for the web application (standard or custom CAS policy).
Assemblies deployed to the GAC available to all of the web applications, while the assemblies deployed to the bin folder are local to the given web application.
a.) Deploying a DLL to the bin directory means that whatever features your solution included will only be available for the particular web application you deployed it to, since by definition you only deployed it to a particular web application. If you deploy a dll to the GAC, it's available for all your web applications to use.
2.) The bigger difference is in regards to security. Any dll deployed to the GAC operates with full rights to do anything, essentially. DLLs in the bin directory operate with minimal permissions. Putting a dll in the bin directory is more secure, but there are times when you might have to explicitly grant your code permission to do various things. We refer to this concept as "Code Access Security" or CAS. Take a look at this article on MSDN: http://msdn.microsoft.com/en-us/library/dd583158(office.11).aspx. It was written for SharePoint 2003 but applies to 2007 as well.

Assemblies deployed to the GAC have full trust, while the assemblies deployed to the bin folder runs with the trust level specified for the web application (standard or custom CAS policy).
Assemblies deployed to the GAC available to all of the web applications, while while the assemblies deployed to the bin folder are local to the given web application.

14. What is the Event Receiver or Event Handling in SharePoint…?a. The ability to catch certain user actions in code and respond programmatically. These are the classes which we can inherit and write event handlers or receivers against them.
b. Asynchronous vs Synchronous Events: The "ing" and the "ed"

Synchronous events:
a. Occur before the event.
b. Block the flow of code execution until your event handler completes.
c. Provide you with the ability to cancel the events resulting in no after event (“...ed") being fired.

Asynchronous events:
a. Occur after the event.
b. Do not block the flow of code execution in SharePoint.

15. What is the web part..?a. Web part is a reusable code component creates a document to display some information (content) or provide some functionality in SharePoint site.
b. Web part can present any type of web based information.
c. Web Parts are the main user interface elements in SharePoint, and they are similar to ASP.NET controls.
d. Web Part Life Cycle starts with
OnInit – Configuration values set using WebBrowsable properties and those in web part task pane are loaded into the web part.
LoadViewState – The view state of the web part is populated over here.
CreateChildControls – All the controls specified are created and added to controls collection. When the page is being rendered for the first time the method generally occurs after the OnLoad() event. In case of postback, it is called before the OnLoad() event. We can make use of EnsureChildControls() - It checks to see if the CreateChildControls method has yet been called, and if it has not, calls it.OnLoad
User Generated Event – for e.g. button click on the web part.
OnPreRender – Here we can change any of the web part properties before the control output is
drawn.
RenderContents – Html Output is generated.
SaveViewState - View state of the web part is serialized and saved.
Dispose
UnLoad.
e. Following WebParts are available with WSS:-
Data View Web Part: - Displays data with rich design support through Microsoft SharePoint Designer.
List View Web Part: - Helps us to display list content for any list in the SharePoint site.
Image Web Part: - Helps us to display image files.
Content Editor Web Part: - Use this to display static HTML content using a WYSIWYG editor or to link to a text file.
Members Web Part: - Helps us to display members of the site.
Page Viewer Web Part: - Displays web page in an Iframe.

Wednesday, 1 June 2011

Microsoft Office SharePoint Server 2007 and Windows SharePoint Services v3 Branding Articles and Resources

Microsoft Office SharePoint Server 2007 and Windows SharePoint Services v3 Branding Articles and Resources


Articles:

Please go through the below links

Introduction to Customization


Cascading Style Sheets (CSS)

·         » CSS Reference Chart

Design Tips


Interface Customization How-To Articles


Master Pages

·         » DOCTYPES and SharePoint

Navigation


Other

SharePoint Workflow

Standard out-of-the-box workflows in WSS 3.0 and Office SharePoint Server 2007

Out-of-the-box SharePoint workflows

Learn which standard out-of-the-box workflows are available for document management in Windows SharePoint Services (WSS) 3.0 and Microsoft Office SharePoint Server 2007.

Workflows in Windows SharePoint Services (WSS) 3.0

Windows SharePoint Services (WSS) 3.0 comes with only one workflow template out-of-the-box (OOTB):
  • Three-state workflow

Three-state workflow

The Three-state workflow is a simple issue tracking workflow that shows the status of active and resolved issues. You can use this workflow to move a document along one or 3 states, for example a PendingApproved, and Rejected state.
The Three-state workflow works with an Issue Tracking list or any other list that has a Choice column with 3 values.

Workflows in Microsoft Office SharePoint Server 2007

Microsoft Office SharePoint Server 2007 comes with the following workflow templates out-of-the-box (OOTB):
  • Approval workflow
  • Collect Feedback workflow
  • Collect Signatures workflow
  • Disposition Approval workflow
  • Group Approval workflow (available only in some languages)
  • Translation Management workflow

Approval workflow

The Approval workflow routes a document for approval. You can set up this workflow to be serial or parallel, and preset the approvers.
The Approval workflow is typically used to send out a document to people who need to approve the document, often as a prerequisites to publishing the document.
The document can be sent to:
  1. People one by one after each other ( = serial), or 
  2. Everyone at the same time ( = parallel)

Collect Feedback workflow

The Collect Feedback workflow routes a document for feedback. When the workflow completes all the feedback is aggregated and sent to the originator of the workflow.

Collect Signatures workflow

Rather than just sending a document for approval, the Collect Signatures workflow requires digital signatures on the document. This workflow requires Office 2007 and can only be initiated from an Office 2007 client application.

Disposition Approval workflow

The Disposition Approval workflow works with the records management capabilities and Records Center in SharePoint. It allows you to manage document expiration and retention.
You can use the Disposition Approval workflow to make decisions as to what you want to do with documents after they expire; not just delete the documents, but for example, archive documents, send out notifications, etc.

Group Approval workflow (East Asian Document Approval)

The Group Approval workflow routes a document for approval using stamp signatures and a group-oriented consensus process. It is only available for East Asian cultures.
To support hierarchical approvals, this workflow uses a hierarchical control to select the approvers and stamping rather than signatures for approval.

Translation Management workflow

The Translation Management workflow is used with the Web content management features of SharePoint to support a translation workflow for content to multiple languages.


SharePoint Designer 2007 workflows

Introduction to SharePoint Designer workflows
If you want to know whether you should be using SharePoint Designer to design your workflows
Before you can create custom workflows in SharePoint Designer you must:
  1. Have access to the SharePoint site on which the list or library to which you want to add a workflow resides.
  2. Have access to the list or library to which you want to add a workflow.
To create a workflow in SharePoint Designer 2007, you must:
  1. Open a SharePoint site.
  2. Create a new workflow.
  3. Design the workflow. This includes attaching the new workflow to a list or library on the SharePoint site, and adding steps, conditions, and actions to the workflow.
  4. Publish the workflow to the SharePoint site.
Open a SharePoint site
To open a SharePoint site in SharePoint Designer 2007:
  1. On the File menu, click Open Site.
 SharePoint Designer 2007 Open Site menu item on the File menu.
  1. On the Open Site dialog box, select the SharePoint site you want to open, or type the URL to the SharePoint site in the Site name field, and click Open.
SharePoint Designer 2007 Open Site dialog box.
Create a new workflow
To create a new workflow in SharePoint Designer 2007:
  1. On the File menu, select New, and then click Workflow.
SharePoint Designer 2007 menu items to create a new workflow.
  1. You are now ready to attach the workflow to a list or library and create its steps.
Design the workflow
For an example and instructions on attaching a workflow to a SharePoint list or library and adding steps, conditions, and actions to the workflow
Publish the workflow
Once you’ve designed your workflow, you can click the Finish button on the Workflow Designer to save your workflow to the Workflows document library in the Folder List, and also publish your workflow to the SharePoint site.

MyWorkflow workflow selected under the Workflows document library.

If at any time after saving and publishing the workflow you want to modify the design of your workflow, you must:
  1. Expand the Folder List of the SharePoint site and locate the Workflows document library.
  2. Under the Workflows document library, locate the workflow you created.
  3. Double-click the <YourWorkflowName>.xoml file to open the Workflow Designer.
You can now modify your workflow and re-publish it.