Microsoft.SharePoint and Microsoft.SharePointt.WebPartPages
2) What are the differences between the two base classes and what are the inherit benefits of using one over another?
Microsoft.SharePoint is used to access sharepoint object model and WebPart Pages is used to access webpart class.
3) What is GAC?
4) Why is strong naming (signing) a WebPart assembly file mean?
Strong names guarantee name uniqueness by relying on unique key pairs. No one can generate the same assembly name that you can, because an assembly generated with one private key has a different name than an assembly generated with another private key.
5) What are safe controls, and what type of information, is placed in that element in a SharePoint web.config file?
6) What is the CreateChildControls() method? How can you use it to do something simplelike displaying a simple Label control?
7) What does the RenderContents method do in an ASP.NET 2.0 WebPart?
8) What is the WebPartManager sealed class? What is its purpose?
9) What is a SPSite and SPWeb object, and what is the difference between each of the objects?
10) How would you go about getting a reference to a site?
11) What does a SPWebApplication object represent?
12) Would you use SPWebApplication to get information like the SMTP address of the SharePoint site?
13) How do you connect (reference) to a SharePoint list, and how do you insert a new List Item?
14) How would you loop using SPList through all SharePont List items, assuming you know the name (in a string value) of the list you want to iterate through?
15) How do you return SharePoint List items using SharePoint web services?
16) When retrieving List items using SharePoint Web Services, how do you specify explicit credentials to be passed to access the list items?
17) What is CAML, and why would you use it?
18) What is impersonation, and when would you use impersonation?
19) What is the IDesignTimeHtmlProvider interface, and when can you use it in WebParts?
20) What are WebPart properties, and what are some of the attributes you see when declaring WebPart properties?
21) Why are properties important in WebPart development, and how have you exploited them in past development projects?
22) What are ClassResources? How do you reference and deploy resources with an ASP.NET 2.0 WebPart?
23) What is a SharePoint Solution File? How does it differ from WebPart .cab files in legacy development? What does it contain?
24) What is a .ddf file and what does it have to do with SharePoint Solution creation?
25) What file does a SharePoint solution pacakage use to orchestrate (describe) its packaged contents?
26) What deployment mechanism can you use to instigate Code Access Security attributes for your WebParts?
27) What is a SharePoint Feature?
28) What types of SharePoint assets can be deployed with a SharePoint feature?
29) What are event receivers?
30) When would you use an event receiver?
31) What base class do event receivers inherit from?
32) If I wanted to not allow people to delete documents from a document library, how would I go about it?
33) What is the difference between an asynchronous and synchronous event receivers?
34) How could you assign append string to the title of a site when it is provisioned?
35) Can an event receiver be deployed through a SharePoint feature?
36) What is a content type?
37) Can a content type have receivers associated with it?
38) What two files are typically included when developing a content type, and what is the purpose of each?
39) What is an ancestral type and what does it have to do with content types?
40) Can a list definition be derived from a custom content type?
41) When creating a list definition, how can you create an instance of the list?
42) What is a Field Control?
43) What base class do custom Field Controls inherit from?
44) What is a SharePoint site definition?
45) How does one deploy new SharePoint site definitions so that they are made aware to the SharePoint system?
Some More Questons
1. Describe Authentication Model in SharePoint?
1. Window
In Windows Based Authentication ASP.NET Relies on IIS to authenticate Incoming request using one of its available Authenticate Methods.
a) Basic Authentication:-Basic Authentication is Compatible with most browsers. But Password is sent in Clear Text. These are Protected with SSL Encryption.
b) Digest Authentication:- Digest Authentication is introduced with HTTP 1.1,So it may not support all browsers. It sends hashed value instead of Clear-Text Password, its more secure than Basic Authentication. But it requires a Windows 2000 Domain Controller.
c) Integrated windows (NTLM)[NT LAN Manager] Authentication:-Integrated Windows Authentication is Available only with Internet Explorer. Its most secure method because it never sends a username /Password over the network., but it will not work over HTTP Proxy Connection.
Form-Based Authentication allows developers to easily implement “roll-your-own” security in their Applications. All you need to do is create the login page, tell ASP.NET where to find (via web.config) and set the desired Authorisation restrictions. In your login page, you can verify username and password credentials entered by user against a database, windows 2000 autrhenticate directory.
Once Credentials are verified you can use methods exposed by Forms Authentication class to set or remove an authentication cookie redirect the user to original page they requested or renew the authentication Cookie.
3. Passport
Password Authentication used the Centralized Password service provided by Microsoft. Passport authentication gives users a single login to use with any passport-enabled site.
In order to use Passport Authentication with ASP.NET , you must download and install SDK, which is available with www.passport.com/business
2. What is the difference between a Site Definition and a Site Template?
Site Definitions are stored on the hard drive of the SharePoint front end servers. They are used by the SharePoint application to generate the sites users can create. Site Templates are created by users as a copy of a site they have configured and modified so that they do not have to recreate lists, libraries, views and columns every time they need a new instance of a site.
No comments:
Post a Comment