Governance Configure Customise Code

Loading...

Flash Player 9 (or above) is needed to view presentations.
We have detected that you do not have it on your computer. To install it, go here.

0 comments

Post a comment

    Post a comment
    Embed Video
    Edit your comment Cancel

    Notes on slide 1

    Most common cause of SharePoint problems that I fix are due to configuration changes.Examples including changing DB permissions and changing zone of website in IE e.g. SharePoint admin did not know a change had occurred but they got the calls that it was broken.

    Launce site using integrated auth.Show changing Basic auth via IIS direct.Refresh site and show basic auth promptThen open CA, auth provider.Setting is not changed in CA, when you hit ok it will overwrite.Hence CA was out of sync with IIS. Also doing it via IIS would mean you’d have to do it on every WFE instead of CA setting it on all for you.

    Sometimes customisation isn’t pretty.Even customisations via the browser can break things.

    Show customising content types and getting two display names which are the same for usersShow branding demo using SPD and note customisation warning.Talk about wrapping up using tool such as SPSource + WSPBuilder to deploy instead hence create rapid but deploy properly.

    Run SPDisposeCheck on exe.Open up a wsp (rename to cab) , then run on DLL.For dev audience could do more detail on wsp’s + feature stapling.

    Favorites, Groups & Events

    Governance Configure Customise Code - Presentation Transcript

    1. Configure, Customise, Code
      Elaine van Bergen
      OBS
      Architect
    2. Definitions
      • ConfigureChanging settings within the environment at a high level such as SharePoint Farm, Server or DB.
      • CustomiseModifying the environment without writing code that requires compilation
      • Code Modifying the environment through compiled code
    3. Common Roles
      • System Administration
      • SharePoint Administrators
      • Site Administrators
      • Developers
      • End Users
    4. Environments
      • Function
      • Dev (multiple)
      • Test
      • Staging*
      • Production
      • DR
      • Desktop
      • Others
    5. Server Roles
      • Web Front End
      • Serves pages
      • Database
      • Stores Content
      • Index
      • Crawling
    6. Configure
      6.
    7. Educate the technical team
      • Get to know your system administrator and DBA
      • Changing settings, can easily break SharePoint
      • Generally not even be SharePoint specific, think database, office, security, internet explorer
    8. Configure the right way
      • Always use SharePoint UI’s for changing settings e.g. central administration not IIS
      • Consider the database as off limits until you have read the necessary white papers from Microsoft.
      • IT and the business need to work together on settings changes
    9. 9.
      Demo
    10. Minimize the risk
      • Ensure test strategy is defined
      • This needs to involve the key stakeholders and key business functions
      • Push changes through the test environment first
    11. Repeatable Process
      • Avoid “This problem only happens on production”
      • Document
      • Script
      • Use a tool to synchronise
    12. Customise
      12.
    13. Common types of customisation
      • Web parts
      • Content Types
      • Branding
      • Workflow
      These are not as harmless as they sound
    14. Web parts
      • Content Queries – Large queries
      • XSLT – Incorrect syntax
      • RSS – Malicious feeds, internet access
      • Page Viewer – Malicious content
      • Consider what web parts are appropriate
    15. Content types
      • Changes may not propagate as expected
      • Adding fields work well
      • Fields with the same display name
      • Fields with different internal names in locations
    16. Branding
      • Rapid development is possible using tools like SharePoint designer
      • Changes may break the entire site
      • Think about different sorts of sites
      • Meeting workspaces
      • Search
      • Back-up and rollback strategy
      • Move between system environments
    17. Workflow
      • How will this be tested
      • Loops, annoying test emails, deleting information
      • Deployment strategy
    18. 18.
      Demo
    19. Solution
      • Control using security and policy but need to preserve the goal
      • Educate the users
      • Provide a training playpen
      • Customisations should go via a test server too
      • Monitor the system
      • Have a backup and rollback strategy
    20. Code
      20.
    21. Code
      • Why are you writing code ?
      • Negotiate first, code second
      • Code sources:
      • Buy
      • Download
      • Develop
      • Do you have a support strategy ?
    22. Develop the right way
      • SharePoint code is just .Net code but has it’s own best practises
      • Traps for new players
      • Memory management
      • Excessive database round tripping
      • Forgetting about scale
      • Forgetting about security
    23. Common symptoms of memory leaks
      • Frequent recycles of application pool, especially during peak usage
      • Application crashes that appear as heap corruption in the debugger
      • High memory use for Microsoft Internet Information Services (IIS) worker processes
      • Poor system and application performance
    24. Getting memory right is hard
      using(SPSite site = new SPSite("http://server")){
      using(SPWeb web = site.OpenWeb()){...}}
      using( SPWeb web = SPControl.GetContextWeb(HttpContext.Current)) { ... }
      using (SPWeb web = new SPSite(SPContext.Current.Web.Url).OpenWeb()) { ...}
      But SPDispose check helps
    25. Testing conditions
      • Does will it work with the following:
      • Large number of sites and lists
      • 2000+ items in a folder
      • Multiple web servers
      • Alternative access mappings
      • Does it work for different users
      • Reader
      • Contributor
    26. Package
      • Create features and bundle into solution (WSP) to deploy
      • WSP’s automatically get deployed to all servers in the farm
      • WSP’s can do more than just deploy web parts and files
      • Staple your features if needed on site creation
    27. 27.
      Demo
    28. Acceptance Checklist
      • Packaging
      • Coding standards
      • SPDisposeCheck
      • Supported/Upgradable
      • Load + Performance test
      • Security test
      • Accessibility
    29. Questions ?
      Elaine van Bergen
      @laneyvb on twitter
      http://laneyvb.blogspot.com
      29.

    + laneyvblaneyvb, 4 months ago

    custom

    280 views, 0 favs, 0 embeds more stats

    Techniques and things to watch out for when configu more

    More info about this document

    © All Rights Reserved

    Go to text version

    • Total Views 280
      • 280 on SlideShare
      • 0 from embeds
    • Comments 0
    • Favorites 0
    • Downloads 5
    Most viewed embeds

    more

    All embeds

    less

    Flagged as inappropriate Flag as inappropriate
    Flag as inappropriate

    Select your reason for flagging this presentation as inappropriate. If needed, use the feedback form to let us know more details.

    Cancel
    File a copyright complaint
    Having problems? Go to our helpdesk?

    Categories