Imp Points SharePoint 2010

1. SharePoint 2010 is based on Asp.Net 3.5 & runs on 64-bit platforms only.

2. The _layouts location is a virtual web folder that points to a file-system folder on SharePoint server. Visual studio 2010 provides support for deploying items to the _layouts folder.

3. Wsp Files simplify deployment across multiple servers in a farm & provide for a standard way for visual studio to open & modify functionality.

4. Site events enable a developer to capture events such as site deletion, site provisioning, and site moving either just before or after these operations have taken place.

5. Visual studio 2010 & SharePoint 2010 combine to provide a full debugging interface for developers.

6. The SpFarm object provides access to all of the services & web applications in SharePoint deployment.

7. Standard webparts inherit from the Asp.Net web part base class.

8. SharePoint Building blocks enable faster development, proven components & more efficient code, & ensure you do not end up building what already exists.

9. Retrieving & manipulating data often makes use of Splistitem & SPQuery classes.

10. Linq offers early binding to list data, fields and the data types of those fields. Linq is also a standard approach to querying data.

11. A Content type can be associated with various types of document & completing the additional Metadata can improve the management of site data.

12. Silverlight .NET & JavaScript can all use the SharePoint client object model.

13. XML & JSON technologies are used to communicate between the client object model & SharePoint server.

14. The client service (client.svc) runs on SharePoint server & services batch requests from applications that use the client object model.

15. When the client object model is instantiated the URL to the SharePoint site can be passed to its constructor as a string.

16. Lambda expressions can be used to filter the items in a list when calling the lists method on the client context load.

17. Silverlight applications should query data using an asynchronous background thread.

18. BCS integrates external content with SharePoint collaboration and workflow.

19. SharePoint Designer can be used to build basic BCS solutions with many of the features managed by standard out of box functionality. More complex requirements can be built in visual studio 2010.

20. External content from BCS can be displayed in the SharePoint web interface and can be taken offline in SharePoint workspace.

21. The workflow engine is based on Asp.Net 3.5 and as well as introducing workflows at the site level, SharePoint 2010 enables workflows to be built in Visio before being imported into SharePoint designer or visual studio.

22. The workflow engine supports Sequential & state machine workflows.

23. The workflow initiation form allows parameters to be provided when a workflow is stated.

24. Silverlight offers a rich user experience and with the code running on the client browser that workload for many operations is removed from the server.

25. Sandboxing provides non-developers & organizations with agility, stability & security.

26. The sandboxed code will run in the context of a specific worker process called spucworkerprocess. The code is then reviewed against a set of allowed objects & methods on the subset of the object model & where allowed calls are made against the full object model.

27. The sandboxed feature also offers advanced resource management that is capable of identifying code that is consuming more resources than acceptable and then reducing the impact of that code by notifying the administrator and if necessary disabling code.

28. There are number of operations that are disallowed in a sandboxed solution. These include using the SpFarm object & performing asynchronous postbacks.

29. The server ribbon uses Ajax, Dynamic Scaling as well as CSS Layouts, styling & hover effects.

30. The dialog interface is a visual interface that helps users maintain context when interacting with content on the SharePoint site. The dialog interface can be accessed by developers using HTML elements & JavaScript.

31. The dialog control is typically implemented in a HTML DIV that is made visible programmatically when required.