What is SharePoint?

Answer: 

Share point helps team members to connect and exchange information in a collaborative manner. It helps to centralize enterprise information for efficient functioning. 

More details: http://www.go4sharepoint.com/Code/sharepoint-186.aspx

What is MOSS ?

Answer: 

Microsoft Office SharePoint Server (MOSS) is the full version of a portal-based platform for collaboratively creating, managing and sharing documents and Web services. 

In MOSS additional feature add that can not in WSS 3.0.

How does WSS actually work?

Answer: 

WSS does not work in an isolated fashion. It needs help of two more products IIS (Internet Information Server) and SQL Server.

What is WSS and MOSS?

Answer: 

Microsoft has divided share point products in two parts. 

1) One is called as WSS (Windows SharePoint services) and 

2) the other is MOSS (Microsoft Office SharePoint server). 

WSS is the platform on which MOSS is built. The WSS part is licensed through Windows 2003 server and it does not cost. MOSS is separate product by itself and it needs licensing and it has a good amount of cost J . WSS is good for small team and small projects. MOSS has extra functionalities in other words value added services. So the choice between WSS and MOSS will depend on budget of the project and the VAS provided by MOSS.   

In summary WSS + Additional Functionalities = MOSS

What is site and site collection?

Answer: 

Share point is all about enterprise data. When we talk about enterprise data it looks some as shown in the figure below. In other words grouping and sub groupings of data.

SharePoint extends the IIS web application structure to accommodate the above defined data structure using site and site collections. We will see in the later section how to create site collections.

More details: http://www.go4sharepoint.com/Code/site-site-collection-187.aspx

What is the concept of Site pages and Application pages?

Answer: 

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. If you want to make generic pages in a site collection which will be used by every one, like for instance the ‘Settings.aspx’ page then you need to use application pages.

     In other words Site pages are nothing but customized pages stored in content, while application pages are generic pages which will be used by all the sites in a site collection.

What is the main advantage of using site collections?

Answer: 

As said previously SharePoint is all about data and data should properly authenticated / authorized to proper users. By defining the structure in site and site collection we can now define roles and responsibilities according to data. For instance in the above figure we will assign all HR user to payroll, recruitment and assessment site. These users will not be assigned to account site collection. Same holds true for accounts user.

So when you design your hierarchy of site and site collection you need to keep in mind the enterprise hierarchy structure and design the same accordingly.

What is a web part?

Answer: 

Web parts consist of xml queries to full SharePoint lists or document libraries. You can also develop your own web parts and web part pages.

What is web part and provide type?

Answer: 

Web Parts are the fundamental building blocks for Share Point user interface, and with them we can build and integrate many different types of applications.In share point also be create custom web part using .oscx control 

steps create custom web part 

• create web part project copied .oscx control and build application.place .dll file in GAC .reset IIS. 
• go 12 hive _layout folder create folder past your .oscx control 
• go inetpub ->wwwroot->wss->open Your site ->web con fig->create safe control write assembly information of web part application 
• open sharepoint site ->site action-site editing->Galleries ->web part->new Add your web part. 

follow few web part in WSS 3.0 

• Content Editor Web Part 
• Data View Web Part 
• List View Web Part 
• Image Web Part 
• Members Web Part . 
• Page Viewer Web Part

How to disable scroll bar in Page Viewer Web parts iframe

Answer:

I am building a site using sharepoint services 3.0. I want to display a Particular Page from my sharepoint site into a different page that is also in that sharepoint site. For example, the page that I want to show is "Sample.aspx" and the page where I want "Sample.aspx" to be placed as an <iframe> is "Master.aspx." Now I have created the "Sample.aspx" and it doesnt have a height more than 100px. In order to create a <iframe> I used the Page Viewer web part and located http://server/Sample.aspx and set the height to 800px so that its enough for the <iframe> to show the Sample.aspx without have to show a scroll bar. Now this works fine in internet explorer but when you browse using FireFox, you can see a huge 800px scroll bar which is not supposed to be there because the sample.aspx page has a smaller height that is not bigger than 100px.

Now, how can I remove the scroll bar from displaying in Firefox?

I have never used SharePoint services, but if you can edit the HTML, go to the IFRAME tag:

<iframe src="Sample.aspx" ... ...>...</iframe>

and add the attribute SCROLLING="no".

<iframe scrolling="no" src="Sample.aspx" ... ...>...</iframe> 

How can we display a simple custom page in SharePoint?

Answer: 

Ok first thing there is no concept of simple page in SharePoint. There are two types of pages in SharePoint as we discussed in the previous article one is an Application page and the other is the site page. 

Application page is a generic page while site pages are custom to a website. To just cool you off lets display a simple Application page first.

Some points to be noted about Application pages:-

• They are pages which are shared across sites like ‘settings.aspx’ , which will helps us set generic properties across sites in a site collection.
• The second important part is that we need to save application pages in ‘C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\LAYOUTS’ folder. If you browse to the folder you will find SharePoint’s own application pages.

Ok, what we will do is that to build confidence let’s make a simple page called as ‘SimplePage.aspx’. We are not doing anything great in this we will just write this simple sentence inside the page. 

 

<b> Ohhhh I never Knew SharePoint is so easy </b>

 

Once you have saved the page just browse to the IIS application and browse to the _layouts folder as shown in the figure below. If you open the page in browser you should see your display message.

 

Note: - For the next question you need to understand the concept of master pages. If you have not please read it once. Consistent look and feel is one of the most important factor in enterprise portal and SharePoint achieves the same using Master pages.

Which are the various ready made list types in SharePoint?

Answer: 

There are approximately thirteen different ready made list types, below mentioned are some of the most used ones.

1. Document library
2. Form library
3. Wiki page library
4. Picture library
5. Announcements
6. Contacts
7. Discussions
8. Links
9. Calendar
10. Tasks
11. Project tasks
12. Issue tracking
13. Custom list

Explain Document list library

Used for collaborating on documents with support for versioning, check-in and check-out, and workflow. Includes support for deep integration with Microsoft Office.

Explain Form list library

Used to store XML documents and forms for use with Microsoft Office InfoPath.

Explain Wiki page list library

Used for collaborative Web pages based on wiki pages, which are dynamically generated and collaboratively edited Web pages.

Explain Picture library

A specialized document library enhanced for use with pictures. Includes support for slide shows, thumbnails, and simple editing through Microsoft Office Picture Manager.

Explain Announcements list library

Used for simple sharing of timely news with support for expiration.

Explain Contacts list library

A list for tracking people and contact information, with support for integration into Microsoft Office Outlook and other WSS-compatible contacts applications.

Explain Discussions list library

A simple list for threaded discussions with support for approval and managing discussion threads.

Explain Links list library

A list for managing hyperlinks.

Explain Calendar list library

A list for tracking upcoming events and deadlines. Includes support for integration and synchronization with Office Outlook.

Explain Tasks list library

A list of activity-based items that can integrate with workflow.

Explain Project tasks list library

An enhanced tasks list with support for Gannt chart rendering and integration with Microsoft Office Project.

Explain Issue tracking list library

A list for tracking issues and resolution, with support for prioritization.

Explain Custom list library

An empty list definition for extending with custom columns, or created using Microsoft Office Excel spreadsheets

What is the concept of safemodeparser in ASP.NET?

Answer: 

As said the previous section there are two tables one is the document and the other content. If the page is stored in the content database it’s loaded by the SafeModeParser which is page parser provided by SharePoint. If there is no data found in the content it’s loaded from the file directory by simple ASP.NET runtime. 

What are ways to create input forms for workflow ?

Answer: 

Two 

1. You can create your forms by using custom application pages, which are standard .aspx pages deployed to run out of the _layouts directory. 

2. Using Microsoft Office InfoPath 2007

What are the types of input forms that can be created for a workflow ?

Answer: 

You can create four different types of input forms including 

1. An association form 

2. An initiation form 

3. A modification form 

4. A task edit form.

What are the advantages of SharePoint Portal Services (SPS) over SharePoint Team Services (STS)?

Answer: 

harePoint Portal Services (SPS) has MUCH better document management. It has check-in, check-out, versioning, approval, publishing, subscriptions, categories, etc. STS does not have these features, or they are very scaled back. SharePoint Portal Services (SPS) has a better search engine, and can crawl multiple content sources. STS cannot. STS is easier to manage and much better for a team environment where there is not much Document Management going on. SPS is better for an organization, or where Document Management is crucial.

How can debugging share point application and timer jobs ? with steps?

Answer: 

Steps 1:build application place .dll into gac and reset iis 

steps 2:On the Debug menu, select Attach to Process 

steps 3:select the Show processes from all users check box. 

steps 4:select W3W.exe and OSWTIMER.exe can attach 

steps 5:refresh sharepoint site point break point