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. |
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. |
CALM tands for Collaborative Application Markup Language and is an XML-based language that is used in Microsoft Windows SharePoint Services to define sites and lists, including, for example, fields, views, or forms, but CAML is also used to define tables in the Windows SharePoint Services database during site provisioning. |
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. |
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 |
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. |
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
1.create web part project copied .oscx control and build application.place .dll file in GAC .reset IIS.
2.go 12 hive _layout folder create folder past your .oscx control
3.go inetpub ->wwwroot->wss->open Your site ->web con fig->create safe control write assembly information of web part application
4.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 |
|
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 |
When user writing custom code then it is not trusted, its failure causses on entire site. So the sandbox solution concept is used. In that case program is only written for particular site & solution is uploaded in the same site. The solution size limit is decided at the time of site creation & if size increases or code showing bad performance then it is easy to administrator to stop the working of solution. |
We can create sandbox solution for particular site but not for the entire site collection or farm. It is not applicable for farm solution. There are some restriction while creating the sandbox solution. |
When we deploy project from Visual studio then we can use the SPContext.Current.web but when we use the powershell to activate or deactive the feature then we have to use properties.current.web beacuse there is no access of browser here. |
1. v4.master - This is default master page.
2. default.master - this is used to support the 2007 user interface
3. minimal.master
4. simple.master- it is used for accessdenied.aspx, confirmation.aspx, error.aspx, login.aspx, reqacc.aspx, signout.aspx & webdeleted.aspx pages. |
MasterUrl is used to change the layout of all use end pages but CustomMasterUrl is for changing the layout of admin side pages. |
a. With the help of delegate control, we can take any OOB control of SharePoint and replace with our custom control without any modification in the SharePoint page. So that new custom control overrides the existing one.
b. So the delegate control provide one of the option to add control (either server control or user control) on a SharePoint page.
c. This is one of the important features of SharePoint, introduced in WSS v3 and so in MOSS 2007.
d. For example : In master page SearchBox control is included as
<SharePoint:DelegateControl runat="server" ControlId="SmallSearchInputBox" />
e. The above lines instantiate the delegate control object.
f. This delegate control object uses features to locate the control which is specified in ControlId. So there must be the features (it includes feature at any scope) which creates and deploys the SmallSearchInputBox control.
Thanks and Regards
Prasham |
1. Zones provides the separate logical paths of authentication for the same web application.
2. We can create 5 zones for each web application as follows :
a. Default
b. Intranet
c. Extranet
d. Internet and
e. Custom
3. Each zone represented by different web sites in IIS. |