My presentation on the full trust solution model in SharePoint 2013 for SharePoint Saturday Montreal Feb 2 2013. The premise is you developed full trust solutions in SP 2007 / 2010 and wish to leverage that skillset or legacy solutions in an on premise situation.
[2024]Digital Global Overview Report 2024 Meltwater.pdf
Full Trust Solution Development in SharePoint 2013
1. SP 2013: Full Trust Solution
Development
SharePoint Saturday – MONTRÉAL
2 février 2013 – February 2nd 2013
2. Merci à nos commanditaires!
Thanks to our sponsors!
3. { About.Me() }
• Current SharePoint MVP
• Author for two SP 2010 development books
• SharePoint Architect for Infusion
• Speaker at International Conferences on
SharePoint, at user groups, and at
SharePoint Saturdays
• Certified Trainer for the industry leading
SharePoint training from Critical Path
Training
• Telerik “Insider”
• Holds all MS certifications for SharePoint
2010
• Harley-Davidson ™ Enthusiast!
https://mvp.support.microsoft.com/profile/Ed.Musters
15. Solution Packages
• Solution Packages are sets of Web Parts
functionality deployed to the farm or
site collection (sandbox)
• May contain one or more Features,
assemblies, pages, controls, and other
artifacts Assemblies WSP
• SharePoint framework handles
installation and configuration of
solution items
• Automated packaging and
deployment in Visual Studio 2010 Mapped
Folders
16. Features Solution
• A ‘Feature’ is a defined set of
functionality encapsulated
Feature
within a specific format
• Features may be comprised of
any combination of code, XML Project Item
including web parts, workflows,
and site definitions
• Features may be deployed Receiver
Assembly
Web Part Template Workflow
individually or as a part of the
solution package
18. Sample App – Footer Links
• Illustrates a very common development pattern
1. Define schema: Site Columns and Content Types
2. List Provisioned with attached content types
3. A Web Part that performs a content query against the content type /
SP List
34. Right # of Solutions?
• Partition according to feature scope
• Partition with reusability in mind
• Partition with maintainability in mind
• Partition along activation dependencies
• Put “schema” in its own solution
• Item types have tendency to be grouped together (e.g. web
parts, workflow templates)
35. What’s Your Story?
• Methodically planned deployment
• The “big bang” deployment
• Visual Studio and SharePoint Designer mix
• Manual Deployment – 35 page manual
• Lack of Deployment Automation
• Actually, there is no real deployment
39. Merci à nos commanditaires!
Thanks to our sponsors!
40. Visitez-nous! – Visit Us!
Site principal / Main site – www.sharepointquebec.org
Twitter - @guspquebec
Facebook - http://www.facebook.com/groups/206445679432304/
Meetup- http://www.meetup.com/guspquebec/
LinkedIn - http://www.linkedin.com/groups?gid=149597
Notas do Editor
Suivre Groupe d’usagers SharePoint Québec sur Twitter via @guspquebec
400 full-time employee consultants with offices in Toronto, Waterloo, New York, Boston, Houston, London UK and Dubai (Calgary expansion underway - planned Q4 2010)Specialists in the design, architecture and implementation of enterprise-scale solutions in Public Sector, Travel & Tourism, Financial Services, Oil & Gas, Retail, Education and HealthcareRecognized Experts on strategic Microsoft technologies: .NET, SharePoint, Dynamics CRM SQL Server, Performance Point, Bing Maps, CCF 2008, Silverlight, WPF, WCF, WW, BizTalk, Mobility and Microsoft SurfaceServices: Consulting & Strategy Enterprise Solution Design & Development User Experience Design & Information Architecture On-site technical mentoring & training Application hosting and support Technical writing
La version 2013 a été présentée par Microsoft cet été. Durant cette session, nous en ferons un survol