Razvoj za SharePoint Predavatelj: Uroš Žunič Podjetje: Kompas Xnet

Transcription

1 Razvoj za SharePoint 2010 Predavatelj: Uroš Žunič Podjetje: Kompas Xnet

2 Vaš IT outsourcing partner Z vami že 15 let Storitve: Pomoč uporabnikom HelpDesk Razvoj poslovnih aplikacij Namestitve in prilagoditve SharePoint-a Administracija strežnikov Izobraževanje

3 Agenda Visual Studio SandBox

4 INTRODUCTION TO VS2010 SHAREPOINT TOOLS Improved VS2010 development expirience

5 SharePoint 2007 Development Visual Studio Experience Is Limited Visual Studio Extensions for WSS Visual Studio Tools for Office with VS2008 SharePoint developers reliant on community tools Developers have to deal with tedious details Manually editing CAML files Understanding RootFiles directory of WSS Manual edits to manifest.xml file

6 SharePoint 2010 Project Templates All Projects built using standard structure Common Project Properties Project File Project Folder Assembly Deployment Target Sandboxed Solution Site URL Startup Item

7 SharePoint 2010 Project Structure Standard Project Nodes Properties (standard with Visual Studio) References (standard with Visual Studio) Features (always added by SharePoint 2010 Developer Tools) Package (always added by SharePoint 2010 Developer Tools) SharePoint Project Items (optionally added by dev using SharePoint 2010 Developer Tools)

8 Mapped Folders Mapped Folders used to deploy to RootFiles Layouts folder maps to virtual path /_layouts Images folder maps to virtual path /_layouts You can map other folders inside RootFiles directory Layouts folder key to creating application pages Best practice to create solution-specific folder inside Layouts

9 Project Packaging Project packaging based on Package.wspdef Modify package properties with designer or XML text Modify package properties using property grid Designer allows you to add/remove features and SPIs

10 SPT Deployment Options Two Deployment configuration by default Default No Activation

11 The F5 Debugging Experience What does F5 do? 1. Builds new version of.wsp file 2. Deactivates/uninstalls feature 3. Retracts/deletes old.wsp file 4. Adds/deploys new.wsp file 5. Activates feature in target site (via Site Url) 6. Attaches debugger to W3WP.EXE worker process (via Site URL)

12 Visual Studio 2010

13 SANDBOXED SOLUTIONS

14 SharePoint 3.0 s Challenge Developers build custom solutions Administrators can only secure solutions with CAS Hard to control what is being done in custom code Biggest cause of SharePoint support cases: custom code Developer Design, build and test customizations Administrator Install and monitor customizations Site Collection Owner Activate and use customizations

15 SharePoint 2010 Approach Developers build custom solutions Site collection owners deploy, activate and implement the customizations Administrators leverage resource monitors to check site collection usage Automatic triggers turn off custom solutions in a site collection that are too expensive and taxing on the server Developer Design, build and test customizations Administrator Monitor customizations Site Collection Owner Activate and use customizations Install customizations

16 INTRODUCING SANDBOXED SOLUTIONS

17 Sandboxed Solutions Allow a subset of full solution features Code executes in sandbox Are deployed by a Site Collection administrator Stored in the Solution Gallery

18 Introducing Sandboxed Solutions Sandboxed solution: site collection owners can upload to SharePoint Empowers site collection owners to deploy new functionality w/o involvement of IT Local/remote development options Self-regulating and monitored by IT Limited set of permissions & functionality Resource quotas established & monitored by IT Secure: site collection owner is in control

19 Sandboxed Solutions Help Enterprises Sandboxed solutions are important because Solve SharePoint hosting issues in corporate environments Hosted environments much easier to manage Reduces time to deploying custom solutions Removing process of getting code approved and deployed by IT Improves stability of SharePoint servers Now badly performing code isolated to site collection rather than potentially bringing down an entire server

20 Overview of the Sandbox Allows a subset of the full capabilities in the SharePoint API Secure enforcing the sandbox Execute in a partially trusted environment Code executes in a special service process Subject to CAS Validation framework Provides way to do custom farm wide validation for the deployed packages Each solution is isolated to its site collection

21 Sandboxed Solution Lifecycle Installation Upload into Solution Gallery Solution is validated upon installation Activation Auto-activates features Deactivation Inert operation, extended by developer Web Parts no longer execute Deletion

22 Sandboxed Solution Elements Web Parts Lists List Templates Custom Actions Workflows Event Receivers Content Types Site Columns

23 Installing and running a sandboxed solution

24 EXECUTING CODE IN THE SANDBOX

25 Sandboxed Solutions Process Root SPWeb of SPSite Per-WFE AssemblyCache WebParts.wsp 1 Solution gallery Web Part gallery 2 5 <siteguid>\company. intranet.webpart.wsp\ company.intranet.dll Sandboxed Code Service

26 Sandboxing Architecture Front end Execution Manager Back end Host Service Worker Process Untrusted Code Subset Object Model Full Object Model

27 The Subset Object Model In general SPSite and below SPSite SPWeb No SPSecurity No SPSite construction SPList SPListItem

28 Compiling vs. Executing Sandboxed Solutions Visual Studio 2010 uses IntelliSense to hide full-trust types MyWebPart.dll Runtime All code is compiled against the full API Thus, no sandbox check at compile time only at runtime Workaround Full Object Model Subset Object Model Proxy

29 Creating a Sandboxed Solution with VS 2010

30 SANDBOX RESOURCE MONITORING

31 Sandbox Solution Monitoring Site collection quotas specify the warning and hard limits for number of resources that can be used per day Sum of resource measures are taken across solutions deployed to site collection i.e.: add up CPU Points for all solutions Max of resource utilization measures checked against site collection quota to determine if it should be throttled/blocked

32 Resource Monitoring Processing

33 Monitored Resources Metric Name Description Units Resources Per Point AbnormalProcessTerminationCount Process gets abnormally terminated Count 1 1 CPUExecutionTime CPU exception time Seconds 3, CriticalExceptionCount Critical exception fired Number 10 3 InvocationCount Number of times solution has been invoked Count N/A N/A PercentProcessorTime Note: # of cores not factored in Percentage Units of Overall Processor Consumed ProcessCPUCycles CPU Cycles 1E+11 1E+11 ProcessHandleCount Windows Handles 10,000 1,000 ProcessIOBytes (Hard Limit Only) Bytes written to IO Bytes 0 1E+08 ProcessThreadCount Number of Threads in Overall Process Threads 10, ProcessVirtualBytes (Hard Limit Only) Memory consumed Bytes 0 1E+09 SharePointDatabaseQueryCount SharePoint DB Queries Invoked Number SharePointDatabaseQueryTime Amount of time spent waiting for a query to be performed Seconds UnhandledExceptionCount Unhanded Exceptions 50 3 UnresponsiveprocessCount We have to kill the process because it has become unresponsive Number 2 1 Hard Limit

34 Managing Sandbox Solutions Configure site collection quotas from Central Administration Site collection owners can manage and view resource usage from Site Settings» Solution Gallery PowerShell administration Get-SPSite foreach-object {$_.Quota.UserCodeMaximumLevel = 300} Get-SPSite foreach-object {$_.Quota.UserCodeWarningLevel = 100} You can also block completely certain solutions in farm level Can be managed from Central Admin level

35 Load Balancing Sandboxed solutions can be run in two modes: Local Mode: Execute code on WFE Low administration overhead Lower scalability Remote Mode: Execute on dedicated SharePoint servers Load balanced distribution of code execution requests Create custom Load balancers

36 Exploring Central Administration & Solution Gallery

37 Summary Application Hosting and Customization Introducing Sandboxed Solutions Executing Code in the Sandbox Sandbox Resource Monitoring

38 Vprašanja? Po predavanju boste na vaš elektronski naslov prejeli vprašalnik o predavanju, ki ste ga ravnokar poslušali. Vprašalniki bodo dostopni tudi preko profila na spletnem portalu konference. Z izpolnjevanjem le tega pripomorete k izboljšanju konference. Hvala!

39