1st October, 2020
Ans: Microsoft SharePoint Products and Technologies (including SharePoint Portal Server and Windows SharePoint Services) deliver highly scalable collaboration solutions with flexible deployment and management tools. Windows SharePoint Services provides sites for team collaboration, while Share Point Portal Server connects these sites, people, and business processes-facilitating knowledge sharing and smart organizations. SharePoint Portal Server also extends the capabilities of Windows SharePoint Services by providing organizational and management tools for SharePoint sites, and by enabling teams to publish information to the entire organization.
Ans: A SharePoint Feature is a functional component that can be activated and deactivate at various scopes throughout SharePoint instances, the scope of which are defined as1.Farm-level 2.Web Application level 3.Site-level 4. Web level Features have their own receiver architecture, which allows you to trap events such as when a feature is Installing, Uninstalling, Activated, or Deactivated. The element types that can be defined by a feature include menu commands, link commands, page templates, page instances, list definitions, list instances, event handlers, and workflows. The two files that are used to define a feature are the feature.xml and manifest file(elements.xml). 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.
Ans: Workflow associations are often created directly on lists and libraries, a workflow association can also be created on a content type that exists within the Content-Type Gallery for the current site or content types defined within a list. In short, it can be applied ...At the level of a list/library At the level of a content type defined at site scope At the level of a content type defined at list scope
Ans: You can create four different types of input forms including1. An association form 2. An initiation form 3. A modification form 4. A task edit form. Note that these forms are optional when you create a workflow template.
Ans: Two1. You can create your forms by using custom application pages, which are standard .aspx pages deployed to run out of the _layouts directory. ( disadv: lot of code required when compared to Infopath approach) 2. Using Microsoft Office InfoPath 2007 (disadv: picks up a dependence on MOSS, i.e. it cannot run in a standalone WSS environment)
Ans: A method activity is one that performs an action, such as creating or updating a task. An event activity is one that runs in response to an action occurring.
Ans: A content type is a flexible and reusable WSS type definition (or we can a template) that defines the columns and behavior for an item in a list or a document in a document library. For example, you can create a content type for a leave approval document with a unique set of columns, an event handler, and its own document template and attach it with document library/libraries.
Ans: Yes, a content type can have an event receiver associated with it, either inheriting from the SPListEventReciever base class for list level events or inheriting from the SPItemEventReciever base class. Whenever the content type is instantiated, it will be subject to the event receivers that are associated with it.
Ans: 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.
Ans: An ancestral type is the base type that the content type is deriving from, such as Document (0x0101). The ancestral type will define the metadata fields that are included with the custom content type.
Ans: 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.
Ans: You can create a new instance of a list by creating an instance.XML file
Ans: 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.
Ans: This varies. Generally, custom field controls inherit from Microsoft.SharePoint.WebControls.BaseFieldControl namespace, but you can inherit from the default field controls.
Ans: Multiple SharePoint installs can use the same database server. Not literally the same database on that server. That server must be SQL Server 2000 or SQL Server 2005. It cannot be Oracle or another vendor.
Ans: Creating links to mapped drives in WSS v3 or MOSS 2007 can be done via the new content type for .lnk files.
Ans: Override the CreateChildControls method to include your new controls. You can control the exact rendering of your controls by calling the. Render method in the web parts Render method.
Ans: There are two base classes that a WebPart which is going to be consumed by SharePoint can inherit from, either the SharePoint WebPart Base class or the ASP.NET 2.0 WebPart base class.When inheriting from the SharePoint WebPart Base class your derived WebPart class will inherit from Microsoft.SharePoint.WebPartPages.WebPart. When inheriting from the ASP.NET 2.0 WebPart base class your derived WebPart class will inherit from System.Web.UI.WebControls.WebParts.WebPart. It is considered good practice to use the ASP.NET WebPart base class since the old base class is meant for backward compatibility with the previous version of SharePoint, however, there are four exceptions when it is better to leverage functionality from the SharePoint WebPart base class: 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
Ans: The difference is 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 infrastructureASP.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 using ClassResources for the deployment of said types.
Ans: The WebPartManager sealed class is responsible for managing everything occurring on a WebPart page, such as the WebParts (controls), events, and misc. functionality that will occur in WebPartZones. For example, the WebPartManager is responsible for the functionality that is provided when you are working with moving a WebPart from WebPartZone to WebPartZone. It is known as “the central class of the Web Part Control Set.”
Ans: If your code modifies Windows SharePoint Services data in some way, you may need to allow unsafe updates on the Web site, without requiring a security validation. You can do by setting the AllowUnsafeUpdates property.
Ans: There is a certain object model calls model that requires site-administration privileges. To bypass the access-denied error, we use RunWithElevatedPrivileges property when a request is initiated by a nonprivileged user. We can successfully make calls into the object model by calling the RunWithElevatedPrivileges method provided by the SPSecurity class.
Ans: Checks whether the specified login name belongs to a valid user of the Web site, and if the login name does not already exist, adds it to the Web site. e.g SPUser usr = myWeb.EnsureUser("hitenders");
Ans: The SPSite object represents a collection of sites (site collection [a top-level site and all its subsites]). The SPWeb object represents an instance SharePoint Web, and the SPWeb object contains things like the actual content. An SPSite object contains the various subsites and the information regarding them.
Ans: 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.
Ans: 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.
Ans: In order to retrieve list items from a SharePoint list through Web Services, you should use the lists.asmx web service by establishing a web reference in Visual Studio. The lists.asmx exposes the GetListItems method, which will allow the return of the full content of the list in an XML node. It will take parameters like the GUID of the name of the list you are querying against, the GUID of the view you are going to query, etc. Side Question: I got asked how I built queries with the lists.asmx web service. In order to build queries with this service, one of the parameters that the GetListItems method exposes is the option to build a CAML query. There are other ways to do this as well, but that was how I answered it.
Ans: 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.
Ans: CAML stands for Collaborative Application Markup Language. CAML is an XML-based language that 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.
Ans: Impersonation can basically provide the functionality of executing something in the context of a different identity, for example assigning an account to users with anonymous access. You would use impersonation in order to access resources on behalf of the user with a different account, that normally, that wouldn’t be able to access or execute something.
Ans: 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.
Ans: 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 write 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.
Ans: A SharePoint solution file is essentially a .cabinet file with all a developer's custom components 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 farm is highly manageable from the interface allowing deployment, retraction, and versioning Can package all types of assets like site definitions, feature definitions (and associated components), WebParts, etc. Can provide Code Access Security provisioning to avoid GAC deployments And much more..
Ans: 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 the construction of the SharePoint solution file.
Ans: The solution Manifest.XML file.
Ans: 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.
Ans: Event receivers are classes that inherit from the SpItemEventReciever or SPListEventReciever base class (both of which derive out of the abstract base class SPEventRecieverBase), and provide the option of responding to events as they occur within SharePoint, such as adding an item or deleting an item.
Ans: 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 the retention of stored data.
Ans: Event receivers either inherit from the SPListEventReciever base class or the SPItemEventReciever base class, both of which derive from the abstract base class SPEventReceiverBase.
Ans: You would on the ItemDeleting event set: properties.Cancel= true.
Ans: An asynchronous event occurs after an action has taken place, and an asynchronous event occurs before an action has taken place. For example, an asynchronous event is ItemAdded, and its sister synchronous event is ItemAdding
Ans: Windows SharePoint Services is the solution that enables you to create Web sites for information sharing and document collaboration. Windows SharePoint Services -- a key piece of the information worker infrastructure delivered in Microsoft Windows Server 2003 -- provides additional functionality to the Microsoft Office system and other desktop applications, and it serves as a platform for application development. Office SharePoint Server 2007 builds on top of Windows SharePoint Services 3.0 to provide additional capabilities including collaboration, portal, search, enterprise content management, business process and forms, and business intelligence.
Ans: SharePoint Portal Server is a portal server that connects people, teams, and knowledge across business processes. SharePoint Portal Server integrates information from various systems into one secure solution through single sign-on and enterprise application integration capabilities. It provides flexible deployment and management tools, and facilitates end-to-end collaboration through data aggregation, organization, and searching. SharePoint Portal Server also enables users to quickly find relevant information through customization and personalization of portal content and layout as well as through audience targeting.
Ans: Microsoft Windows Services is the engine that allows administrators to create Web sites for information sharing and document collaboration. Windows SharePoint Services provides additional functionality to the Microsoft Office System and other desktop applications, as well as serving as a platform for application development. SharePoint sites provide communities for team collaboration, enabling users to work together on documents, tasks, and projects. The environment for easy and flexible deployment, administration, and application development.
Ans: Microsoft SharePoint Products and Technologies (including SharePoint Portal Server and Windows SharePoint Services) deliver highly scalable collaboration solutions with flexible deployment and management tools. Windows SharePoint Services provides sites for team collaboration, while Share Point Portal Server connects these sites, people, and business processes—facilitating knowledge sharing and smart organizations. SharePoint Portal Server also extends the capabilities of Windows SharePoint Services by providing organizational and management tools for SharePoint sites, and by enabling teams to publish information to the entire organization.
Ans: Office SharePoint Server 2007 can be used by information workers, IT administrators, and application developers. is designed
Ans: Microsoft Office SharePoint Server 2007 for Internet sites and Microsoft Office SharePoint Server 2007 have identical feature functionality. While the feature functionality is similar, the usage rights are different. If you are creating an Internet, or Extranet, facing website, it is recommended that you use Microsoft Office SharePoint Server 2007 for Internet sites that do not require the purchase of client access licenses. Websites hosted using an “Internet sites” edition can only be used for Internet-facing websites and all content, information, and applications must be accessible to non-employees. Websites hosted using an “Internet sites” edition cannot be accessed by employees creating, sharing, or collaborating on content which is solely for internal use only, such as an Intranet Portal scenario. See the previous section on licensing for more information on the usage scenarios.
Ans: Office Outlook 2007 provides bidirectional offline synchronization with SharePoint document libraries, discussion groups, contacts, calendars, and tasks. Microsoft Office Groove 2007, included as part of Microsoft Office Enterprise 2007, will enable bidirectional offline synchronization with SharePoint document libraries. Features such as the document panel and the ability to publish to Excel Services will only be enabled when using Microsoft Office Professional Plus 2007or Office Enterprise 2007. Excel Services will only work with documents saved in the new Office Excel 2007 file format (XLSX).
Ans: SharePoint-based Web sites can be password-protected to restrict access to registered users, who are invited to join via e-mail. In addition, the site administrator can restrict certain members' roles by assigning different permission levels to view post and edit.
Ans: You can post documents in many formats, including .pdf, .htm and .doc. In addition, if you are using Microsoft Office XP, you can save documents directly to your Windows SharePoint Services site.
Ans: No you cannot. However, you can exchange contact information lists with Microsoft Outlook.
Ans: It only takes a few minutes to create a complete Web site. Preformatted forms let you and your team members contribute to the site by filling out lists. Standard forms include announcements, events, contacts, tasks, surveys, discussions, and links.
Ans: Yes, you can. You can have templates for business plans, doctor's office, lawyer's office, etc.
Ans: By default, all sites are created private. If you want your site to be a public Web site, enable anonymous access for the entire site. Then you can give out your URL to anybody in your business card, e-mail, or any other marketing material. The URL for your Web site will be Http:// yoursitename.wss.bcentral.com Hence, please take special care to name your site. These Web sites are ideal for information and knowledge-intensive sites and/or sites where you need to have shared Web workspace. Remember: Under each parent Web site, you can create up to 10 sub-sites each with unique permissions, settings, and security rights.
Ans: You can create a subsite for various categories. For example:
Departments - finance, marketing, IT
Products - electrical, mechanical, hydraulics
Projects - Trey Research, Department of Transportation, FDA
Team - Retention team, BPR team
Clients - new clients, old clients
Suppliers - Supplier 1, Supplier 2, Supplier 3
Customers - Customer A, Customer B, Customer C
Real estate - property A, property B The URLs for each will be, for example:
You can keep track of permissions for each team separately so that access is restricted while maintaining global access to the parent site.
Ans: If you want your site to have anonymous access enabled (i.e., you want to treat it like any site on the Internet that does not ask you to provide a username and password to see the content of the site), follow these simple steps:
Log in as an administrator
Click on site settings
Click on Go to Site Administration
Click on Manage anonymous access
Choose one of the three conditions on what Anonymous users can access:
Entire Web site
Lists and libraries
The default condition is nothing; your site has restricted access. The default conditions allow you to create a secure site for your Web site.
Ans: Unfortunately, no. At this point, we don't offer domain names for SharePoint sites. But very soon we will be making this available for all our SharePoint site customers. Please keep checking this page for further updates on this. Meanwhile, we suggest you go ahead and set up your site and create content for it.
Ans: Picture libraries allow you to access a photo album and view it as a slide show or thumbnails or a film strip. You can have a separate folder for each event, category, etc
Ans: Hardware requirements: Processor 64-bit, four-core, 2.5 GHz minimum per core. RAM 4 GB for developer or evaluation use, 8 GB for single server and multiple server farm installation for production use. Hard disk 80 GB for installation: For production use, the users need additional free disk space for day-to-day operations. Add twice as much free space as the users have RAM for production environments. Software requirements: The 64-bit edition of Windows Server 2008 Standard with SP2. If the users are running Windows Server 2008 without SP2, the Microsoft SharePoint Products and Technologies 2010 Preparation Tool installs Windows Server 2008 SP2 automatically.
Ans: The key limitation of the SSP architecture was that it was configured by using a set of services, and all Web applications associated with the SSP bore the overhead of all the services even if they weren’t being used. To change the service configuration for a particular Web application, a new SSP would have to be created. The service application architecture, on the other hand, allows a set of services to be associated with a given Web application and a different set of services to be associated with another Web application. Also, the same service application can be configured differently in different Web applications; therefore, Web sites can be configured to use only the services that are needed, rather than the entire bank of services.
TekSlate is the best online training provider in delivering world-class IT skills to individuals and corporates from all parts of the globe. We are proven experts in accumulating every need of an IT skills upgrade aspirant and have delivered excellent services. We aim to bring you all the essentials to learn and master new technologies in the market with our articles, blogs, and videos. Build your career success with us, enhancing most in-demand skills .
Write For Us