Explore topic-wise InterviewSolutions in .

Field CONTROLS are simple ASP.NET 2.0 server controls that PROVIDE the BASIC field functionality of SharePoint. They provide basic general functionality such as displaying or editing list data as it APPEARS on SharePoint list pages.

Field controls are simple ASP.NET 2.0 server controls that provide the basic field functionality of SharePoint. They provide basic general functionality such as displaying or editing list data as it appears on SharePoint list pages.

You can create a NEW INSTANCE of a list by CREATING an instance.XML file.

You can create a new instance of a list by creating an instance.XML file.

YES, a list definition can DERIVE from a content type which can be seen in the schema.XML of the list definition in the ELEMENT.

Yes, a list definition can derive from a content type which can be seen in the schema.XML of the list definition in the element.

An ancestral TYPE is the base type that the content type is deriving from, such as Document (0×0101). The ancestral type will define the metadata FIELDS that are included with the CUSTOM content type.

An ancestral type is the base type that the content type is deriving from, such as Document (0×0101). The ancestral type will define the metadata fields that are included with the custom content type.

There is generally the main CONTENT type file that HOLDS things like the content type ID, NAME, group, description, and version. There is also the ContentType.FIELDS file which contains the fields to include in the content type that has the ID, Type, Name, DisplayName, StaticName, Hidden, Required, and Sealed elements. They are related by the FieldRefs element in the main content type file.

There is generally the main content type file that holds things like the content type ID, name, group, description, and version. There is also the ContentType.Fields file which contains the fields to include in the content type that has the ID, Type, Name, DisplayName, StaticName, Hidden, Required, and Sealed elements. They are related by the FieldRefs element in the main content type file.

Yes, a content type can have an event receiver associated with it, EITHER inheriting from the SPListEventReceiver BASE CLASS for list level events, or inheriting from the SPItemEventReceiver base class. WHENEVER the content type is instantiated, it will be subject to the event receivers that are associated with it.

Yes, a content type can have an event receiver associated with it, either inheriting from the SPListEventReceiver base class for list level events, or inheriting from the SPItemEventReceiver base class. Whenever the content type is instantiated, it will be subject to the event receivers that are associated with it.

A content type is an information blueprint basically that can be re-used throughout a SharePoint environment for defining things like metadata and ASSOCIATED behaviors. It is basically an extension of a SharePoint list, HOWEVER makes it portable for use throughout an instance regardless of where the INSTANTIATION occurs, ergo has location independence.

Multiple content types can exist in ONE document library assuming that the appropriate document library settings are enabled. The content type will contain things like the metadata, listform pages, workflows, templates (if a document content type), and associated CUSTOM written functionality.

A content type is an information blueprint basically that can be re-used throughout a SharePoint environment for defining things like metadata and associated behaviors. It is basically an extension of a SharePoint list, however makes it portable for use throughout an instance regardless of where the instantiation occurs, ergo has location independence.

Multiple content types can exist in one document library assuming that the appropriate document library settings are enabled. The content type will contain things like the metadata, listform pages, workflows, templates (if a document content type), and associated custom written functionality.

Yes.

Yes.

In the OnActivated EVENT:

C#

< view plain TEXT >

SPWeb site = siteCollection.RootWeb;

site.Title+=”INTERVIEW”;

site.Update();

In the OnActivated event:

C#

< view plain text >

SPWeb site = siteCollection.RootWeb;

site.Title+=”interview”;

site.Update();

An asynchronous event OCCURS after an action has TAKEN place, and a SYNCHRONOUS event occurs before an action has TAKE place. For EXAMPLE, an asynchronous event is ItemAdded, and its sister synchronous event is ItemAdding.

An asynchronous event occurs after an action has taken place, and a synchronous event occurs before an action has take place. For example, an asynchronous event is ItemAdded, and its sister synchronous event is ItemAdding.

EVENT RECEIVERS EITHER INHERIT from the SPListEventReceiver base class or the SPItemEventReceiver base class, both which derive from the ABSTRACT base class SPEventReceiverBase.

Event receivers either inherit from the SPListEventReceiver base class or the SPItemEventReceiver base class, both which derive from the abstract base class SPEventReceiverBase.

Since event receivers respond to events, you could use a RECEIVER for something as simple as canceling an action, such as deleting a DOCUMENT library by USING the Cancel property. This would essentially prevent USERS from deleting any documents if you WANTED to maintain retention of stored data.

Since event receivers respond to events, you could use a receiver for something as simple as canceling an action, such as deleting a document library by using the Cancel property. This would essentially prevent users from deleting any documents if you wanted to maintain retention of stored data.

Event receivers are classes that inherit from the SpItemEventReceiver or SPListEventReceiver base class (both of which derive out of the abstract base class SpEventReceiver Base), and PROVIDE the OPTION of RESPONDING to events as they occur WITHIN SharePoint, such as adding an ITEM or deleting an item.

Event receivers are classes that inherit from the SpItemEventReceiver or SPListEventReceiver base class (both of which derive out of the abstract base class SpEventReceiver Base), and provide the option of responding to events as they occur within SharePoint, such as adding an item or deleting an item.

FEATURES can do a lot. For example, you could deploy

• Simple site CUSTOMIZATIONS
• Custom site navigation
• WEBPARTS
• pages
• LIST types
• list instances
• event handlers
• WORKFLOWS
• custom actions
• just to name a few

Features can do a lot. For example, you could deploy

A SharePoint Feature is a FUNCTIONAL component that can be activated and DEACTIVATE at various scopes THROUGHOUT a SharePoint instances, such as at the farm, site collection, web, etc.

Features have their own receiver architecture, which allow you to trap events such as when a feature is installing, uninstalling, activated, or deactivated. They are helpful because they allow ease of upgrades and VERSIONING.

The two files that are used to DEFINE a feature are the feature.xml and manifest file. The feature XML file defines the actual feature and will make SharePoint aware of the installed feature. The manifest file contains details about the feature such as functionality.

A SharePoint Feature is a functional component that can be activated and deactivate at various scopes throughout a SharePoint instances, such as at the farm, site collection, web, etc.

Features have their own receiver architecture, which allow you to trap events such as when a feature is installing, uninstalling, activated, or deactivated. They are helpful because they allow ease of upgrades and versioning.

The two files that are used to define a feature are the feature.xml and manifest file. The feature XML file defines the actual feature and will make SharePoint aware of the installed feature. The manifest file contains details about the feature such as functionality.

SharePoint solution files can add in order to handle code access SECURITY DEPLOYMENT issues. This is done in the element in the SharePoint solution manifest.XML, which MAKES it EASIER to get assemblies the appropriate PERMISSIONS in order to operate in the bin directory of the web application.

SharePoint solution files can add in order to handle code access security deployment issues. This is done in the element in the SharePoint solution manifest.XML, which makes it easier to get assemblies the appropriate permissions in order to operate in the bin directory of the web application.

The SOLUTION Manifest.XML FILE.

The solution Manifest.XML file.

A .ddf file is a data directive file and is used when building the SharePoint solution bundle specifying the source FILES and their destination locations. The IMPORTANT thing for someone to understand is that the .ddf file will be passed as a PARAMETER to the MAKECAB utility to orchestrate construction of the SharePoint solution fiel.

A .ddf file is a data directive file and is used when building the SharePoint solution bundle specifying the source files and their destination locations. The important thing for someone to understand is that the .ddf file will be passed as a parameter to the MAKECAB utility to orchestrate construction of the SharePoint solution fiel.

A SHAREPOINT solution file is essentially a .cabinet file with all a developers ustom componets suffixed with a .wsp EXTENSION that aids in deployment. The BIG difference with SharePoint solution files is is that a solution:allows deployment to all WFE’s in a farmis highly manageable from the interface allowing deployment, retraction, and versioningCan package all types of assets like SITE definitions, feature definitions (and associated components), Webparts, ETC.

A SharePoint solution file is essentially a .cabinet file with all a developers ustom componets suffixed with a .wsp extension that aids in deployment. The big difference with SharePoint solution files is is that a solution:allows deployment to all WFE’s in a farmis highly manageable from the interface allowing deployment, retraction, and versioningCan package all types of assets like site definitions, feature definitions (and associated components), Webparts, etc.

ClassResources are used when inheriting from the SHAREPOINT.WebPart.WebPartPages.WebPart base class, and are defined in the SharePoint solution file as things that should be stored in the wpresources directory on the server. It is a helpful directory to use in order to deploy CUSTOM IMAGES. In ASP.NET 2.0, typically things such as images are referenced by embedding them as resources within an ASSEMBLY. The good part about ClassResources is they can help to eliminate recompiles to change SMALL interface adjustments or alterations to external JavaScript files.

ClassResources are used when inheriting from the SharePoint.WebPart.WebPartPages.WebPart base class, and are defined in the SharePoint solution file as things that should be stored in the wpresources directory on the server. It is a helpful directory to use in order to deploy custom images. In ASP.NET 2.0, typically things such as images are referenced by embedding them as resources within an assembly. The good part about ClassResources is they can help to eliminate recompiles to change small interface adjustments or alterations to external JavaScript files.

Properties are important because WebParts allow levels of personalization for each user. WebPart properties make it possible for a user to INTERACT, adjust, and increase overall experience value with the programmatic assets that you develop without having the need to USE an external editor or right any code.

A very simple example of exploiting a property WOULD be SOMETHING like allowing the user to change the text on the WebPart design interface so that they can display whatever string of text they desire.

Each custom property that you have must have the appropriate get and set accessor methods.

Properties are important because WebParts allow levels of personalization for each user. WebPart properties make it possible for a user to interact, adjust, and increase overall experience value with the programmatic assets that you develop without having the need to use an external editor or right any code.

A very simple example of exploiting a property would be something like allowing the user to change the text on the WebPart design interface so that they can display whatever string of text they desire.

Each custom property that you have must have the appropriate get and set accessor methods.

WebPart properties are just LIKE ASP.NET control properties, they are used to INTERACT with and specify attributes that should be APPLIED to a WebPart by a user. Some of the attributes you SEE with ASP.NET 2.0 properties are WebDescription, WebDisplayName, CATEGORY, Personalizable, and WebBrowsable. Although most of these properties come from the System.Web.UI.WebControls.WebParts class, ones like Category come out of System.ComponentModel namespace.

WebPart properties are just like ASP.NET control properties, they are used to interact with and specify attributes that should be applied to a WebPart by a user. Some of the attributes you see with ASP.NET 2.0 properties are WebDescription, WebDisplayName, Category, Personalizable, and WebBrowsable. Although most of these properties come from the System.Web.UI.WebControls.WebParts class, ones like Category come out of System.ComponentModel namespace.

The IDesign Times HTML Provider interface uses the function GetDesignTimeHtml() which can CONTAIN your relevant render methods. It was helpful to use in 2003 SINCE it allowed your WEBPART to have a preview while a PAGE was edited in FrontPage with the Webpart on it, because the GetDesignTimeHtml() method contains the HTML for the designer to render.

The IDesign Times Html Provider interface uses the function GetDesignTimeHtml() which can contain your relevant render methods. It was helpful to use in 2003 since it allowed your WebPart to have a preview while a page was edited in FrontPage with the Webpart on it, because the GetDesignTimeHtml() method contains the HTML for the designer to render.

CAML stands for Collaborative Application Markup Language. CAML is an XML based language which PROVIDES data constructs that build up the SHAREPOINT fields, VIEW, and is used for table definition during site PROVISIONING.

CAML is RESPONSIBLE for rending data and the resulting HTML that is output to the user in SharePoint. CAML can be used for a variety of circumstances, overall is used to query, build and customize SharePoint based sites.

A general use would be building a CAML query in a SharePoint WebPart in order to retrieve values from a SharePoint list.

CAML stands for Collaborative Application Markup Language. CAML is an XML based language which provides data constructs that build up the SharePoint fields, view, and is used for table definition during site provisioning.

CAML is responsible for rending data and the resulting HTML that is output to the user in SharePoint. CAML can be used for a variety of circumstances, overall is used to query, build and customize SharePoint based sites.

A general use would be building a CAML query in a SharePoint WebPart in order to retrieve values from a SharePoint list.

In ORDER to specify explicit credentials with a Web Service, you generally instantiate the web service, and then using the credentials properties of the Web Service object you USE the System.Net.NetworkCredential class to specify the username, PASSWORD, and domain that you wish to PASS when making the web service call and OPERATIONS.

In order to specify explicit credentials with a Web Service, you generally instantiate the web service, and then using the credentials properties of the Web Service object you use the System.Net.NetworkCredential class to specify the username, password, and domain that you wish to pass when making the web service call and operations.

C#

&LT; view plain TEXT >

SPList interviewList = myWeb.Lists[“listtoiterate”];

foreach (SPListItem INTERVIEW in interviewList)

{

// Do Something

}

C#

< view plain text >

SPList interviewList = myWeb.Lists[“listtoiterate”];

foreach (SPListItem interview in interviewList)

{

// Do Something

}

C#

< view PLAIN TEXT &GT;

USING(SPSite mySite = new SPSite(“yourserver”))

{

using(SPWeb myWeb = mySite.OpenWeb())

{

SPList interview LIST = myWeb.Lists[“list insert”];

SPListItem newItem = interview List.Items.Add();

newItem[“interview”] = “interview”;

newItem.Update();

}

}

C#

< view plain text >

using(SPSite mySite = new SPSite(“yourserver”))

{

using(SPWeb myWeb = mySite.OpenWeb())

{

SPList interview List = myWeb.Lists[“list insert”];

SPListItem newItem = interview List.Items.Add();

newItem[“interview”] = “interview”;

newItem.Update();

}

}

Yes, since this is a Web Application level setting. You would iterate through each SPWebApplication in the SPWebApplication collection, and then use the appropriate PROPERTY calls (OutboundMailServiceInstance) in ORDER to RETURN settings REGARDING the mail service such as the SMTP address.

Yes, since this is a Web Application level setting. You would iterate through each SPWebApplication in the SPWebApplication collection, and then use the appropriate property calls (OutboundMailServiceInstance) in order to return settings regarding the mail service such as the SMTP address.

The SPWEBAPPLICATION objects represents a SharePoint Web Application, which ESSENTIALLY is an IIS VIRTUAL server. Using the class you can instigate high level operations, such as getting all the FEATURES of an entire Web Application instance, or doing high level creation operations like creating NEW Web Applications through code.

The SPWebApplication objects represents a SharePoint Web Application, which essentially is an IIS virtual server. Using the class you can instigate high level operations, such as getting all the features of an entire Web Application instance, or doing high level creation operations like creating new Web Applications through code.

C#

< VIEW plain TEXT >

SPSITE = new SPSite(“http:/SERVER”);

SPWeb = SPSite.OpenWeb();

C#

< view plain text >

SPSite = new SPSite(“http:/server”);

SPWeb = SPSite.OpenWeb();

The SPSite object represents a collection of SITES (SITE collection [a TOP level sites and all its subsites]). The SPWeb object represents an instance SHAREPOINT Web, and SPWeb object CONTAINS things like the actual content. A SPSite object contains the various subsites and the information regarding them.

The SPSite object represents a collection of sites (site collection [a top level sites and all its subsites]). The SPWeb object represents an instance SharePoint Web, and SPWeb object contains things like the actual content. A SPSite object contains the various subsites and the information regarding them.

The RENDER CONTENTS method will render the WebPart content to the writer, usually an HtmlTextWriter since WebParts will output to an HTML STREAM. RenderContents is used to tell how the controls that are going to be displayed in the WebPart should be rendered on the page.

The render contents method will render the WebPart content to the writer, usually an HtmlTextWriter since WebParts will output to an HTML stream. RenderContents is used to tell how the controls that are going to be displayed in the WebPart should be rendered on the page.

The CreateChildControls method in WebParts is used to NOTIFY the WebPart that there are children CONTROLS that should be output for rendering. Basically, it will add any child ASP.NET controls that are called instantiating each control with its relevant properties set, wire any relevant event handlers to the control, etc.

Then the add method of the control class will add the control to the controls collection. In the relevant WebPart render method, the EnsureChildControls method can be called (or set to false if no child controls should be called) to ensure that the CreateChildControls method is run. When using CreateChildControls it implies that your WebPart CONTAINS a COMPOSITION of child controls.

In order to create something like a label control in Create, you would create a new label control using the new keyword, set the various properties of the control like Visible=True and ForeColor = Color.Red, and then USE Controls.Add(myLabelControl) to add the control to the controls collection. Then you can declare EnsureChildControls in the Render method of the WebPart.

The CreateChildControls method in WebParts is used to notify the WebPart that there are children controls that should be output for rendering. Basically, it will add any child ASP.NET controls that are called instantiating each control with its relevant properties set, wire any relevant event handlers to the control, etc.

Then the add method of the control class will add the control to the controls collection. In the relevant WebPart render method, the EnsureChildControls method can be called (or set to false if no child controls should be called) to ensure that the CreateChildControls method is run. When using CreateChildControls it implies that your WebPart contains a composition of child controls.

In order to create something like a label control in Create, you would create a new label control using the new keyword, set the various properties of the control like Visible=True and ForeColor = Color.Red, and then use Controls.Add(myLabelControl) to add the control to the controls collection. Then you can declare EnsureChildControls in the Render method of the WebPart.

When you deploy a WebPart to SHAREPOINT, you must first make it as a safe control to use within SharePoint in the web.config file. Entries made in the safe controls element of SharePoint are encountered by the SharePointHandler object and will be loaded in the SharePoint environment PROPERLY, those not will not be loaded and will throw an error.

In the generic safe control entry (this is GENERAL, there could be more), there is generally the Assembly name, the namespace, the public key token NUMERIC, the typename, and the safe declaration (whether it is safe or not). There are other OPTIONAL elements.

When you deploy a WebPart to SharePoint, you must first make it as a safe control to use within SharePoint in the web.config file. Entries made in the safe controls element of SharePoint are encountered by the SharePointHandler object and will be loaded in the SharePoint environment properly, those not will not be loaded and will throw an error.

In the generic safe control entry (this is general, there could be more), there is generally the Assembly name, the namespace, the public key token numeric, the typename, and the safe declaration (whether it is safe or not). There are other optional elements.

Signing an assembly with a strong name (a.k.a strong naming) uses a cryptographic key pair that gives a unique identity to a component that is being built. This identity can then be REFERRED throughout the rest of the ENVIRONMENT. In order to install assemblies into the GAC, they must be STRONGLY NAMED. After signing, the binary will have a public key token identifier which can be USE to register the component in various other places on the server.

Signing an assembly with a strong name (a.k.a strong naming) uses a cryptographic key pair that gives a unique identity to a component that is being built. This identity can then be referred throughout the rest of the environment. In order to install assemblies into the GAC, they must be strongly named. After signing, the binary will have a public key token identifier which can be use to register the component in various other places on the server.

The difference is the Microsoft.SharePoint.WebPartPages.WebPart base class is MEANT for backward compatibility with previous versions of SharePoint. The benefit of USING the SharePoint WebPart base class is it supported:

• Cross page connections
• Connections between Web Parts that are outside of a Web Part zone
• Client-side connections (Web Part Page Services Component)
• Data caching infrastructure
• NET 2.0 WebParts are generally considered better to USE because SharePoint is BUILT upon the ASP.NET 2.0 web architecture. Inheriting from the ASP.NET 2.0 base class offers you features that inherit to ASP.NET 2.0, such as embedding RESOURCES as opposed to use ClassResources for deployment of said types.

The difference is the Microsoft.SharePoint.WebPartPages.WebPart base class is meant for backward compatibility with previous versions of SharePoint. The benefit of using the SharePoint WebPart base class is it supported:

SharePoint 2013 Introduces a Cloud App Model that enables you to Create apps.Apps for SharePoint are self-contained pieces of functionality that extend the CAPABILITIES of a SharePoint website. An app may include SharePoint components such as lists, WORKFLOWS, and site PAGES, but it can also surface a remote web application and remote data in SharePoint.

SharePoint 2013 Introduces a Cloud App Model that enables you to Create apps.Apps for SharePoint are self-contained pieces of functionality that extend the capabilities of a SharePoint website. An app may include SharePoint components such as lists, workflows, and site pages, but it can also surface a remote web application and remote data in SharePoint.

Microsoft has improved both Client Side Object Model (CSOM) and Representational State Transfer (REST) based APIs by adding a MUCH NEEDED support for the Search, User Profiles, TAXONOMIES, and Publishing Object Model.Client.svc service is extended with REST capabilities and ACCEPTS HTTP GET, PUT, POST requests.

Microsoft has improved both Client Side Object Model (CSOM) and Representational State Transfer (REST) based APIs by adding a much needed support for the Search, User Profiles, Taxonomies, and Publishing Object Model.Client.svc service is extended with REST capabilities and accepts HTTP GET, PUT, POST requests.

In SharePoint 2013, three New Delegate Controls have been Introduced for the PURPOSE of displaying the new Top Suite bar (with links SkyDrive, NewsFeed,Sync,FOLLOW).

These Controls are :

• SuiteBarBrandingDelegate delegate CONTROL
• SuiteLinksDelegate delegate Control
• PromotedActions Delegate Control

In SharePoint 2013, three New Delegate Controls have been Introduced for the purpose of displaying the new Top Suite bar (with links SkyDrive, NewsFeed,Sync,follow).

These Controls are :