Your SlideShare is downloading. ×
  • Like
Governance Configure Customise Code
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Now you can save presentations on your phone or tablet

Available for both IPhone and Android

Text the download link to your phone

Standard text messaging rates apply

Governance Configure Customise Code

  • 728 views
Published

Techniques and things to watch out for when configuring, customising and coding on your SharePoint environment

Techniques and things to watch out for when configuring, customising and coding on your SharePoint environment

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
728
On SlideShare
0
From Embeds
0
Number of Embeds
1

Actions

Shares
Downloads
9
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide
  • 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.

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.
    • 3. CustomiseModifying the environment without writing code that requires compilation
    • 4. Code Modifying the environment through compiled code
  • Common Roles
    • System Administration
    • 5. SharePoint Administrators
    • 6. Site Administrators
    • 7. Developers
    • 8. End Users
  • Environments
  • Server Roles
  • Configure
    6.
  • 21. Educate the technical team
    • Get to know your system administrator and DBA
    • 22. Changing settings, can easily break SharePoint
    • 23. Generally not even be SharePoint specific, think database, office, security, internet explorer
  • Configure the right way
    • Always use SharePoint UI’s for changing settings e.g. central administration not IIS
    • 24. Consider the database as off limits until you have read the necessary white papers from Microsoft.
    • 25. IT and the business need to work together on settings changes
  • 9.
    Demo
  • 26. Minimize the risk
    • Ensure test strategy is defined
    • 27. This needs to involve the key stakeholders and key business functions
    • 28. Push changes through the test environment first
  • Repeatable Process
    • Avoid “This problem only happens on production”
    • 29. Document
    • 30. Script
    • 31. Use a tool to synchronise
  • Customise
    12.
  • 32. Common types of customisation
    These are not as harmless as they sound
  • 36. Web parts
    • Content Queries – Large queries
    • 37. XSLT – Incorrect syntax
    • 38. RSS – Malicious feeds, internet access
    • 39. Page Viewer – Malicious content
    • 40. Consider what web parts are appropriate
  • Content types
    • Changes may not propagate as expected
    • 41. Adding fields work well
    • 42. Fields with the same display name
    • 43. Fields with different internal names in locations
  • Branding
    • Rapid development is possible using tools like SharePoint designer
    • 44. Changes may break the entire site
    • 45. Think about different sorts of sites
    • 46. Meeting workspaces
    • 47. Search
    • 48. Back-up and rollback strategy
    • 49. Move between system environments
  • Workflow
    • How will this be tested
    • 50. Loops, annoying test emails, deleting information
    • 51. Deployment strategy
  • 18.
    Demo
  • 52. Solution
    • Control using security and policy but need to preserve the goal
    • 53. Educate the users
    • 54. Provide a training playpen
    • 55. Customisations should go via a test server too
    • 56. Monitor the system
    • 57. Have a backup and rollback strategy
  • Code
    20.
  • 58. Code
  • Develop the right way
    • SharePoint code is just .Net code but has it’s own best practises
    • 65. Traps for new players
    • 66. Memory management
    • 67. Excessive database round tripping
    • 68. Forgetting about scale
    • 69. Forgetting about security
  • Common symptoms of memory leaks
    • Frequent recycles of application pool, especially during peak usage
    • 70. Application crashes that appear as heap corruption in the debugger
    • 71. High memory use for Microsoft Internet Information Services (IIS) worker processes
    • 72. Poor system and application performance
  • 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
  • 73. Testing conditions
    • Does will it work with the following:
    • 74. Large number of sites and lists
    • 75. 2000+ items in a folder
    • 76. Multiple web servers
    • 77. Alternative access mappings
    • 78. Does it work for different users
    • 79. Reader
    • 80. Contributor
  • Package
    • Create features and bundle into solution (WSP) to deploy
    • 81. WSP’s automatically get deployed to all servers in the farm
    • 82. WSP’s can do more than just deploy web parts and files
    • 83. Staple your features if needed on site creation
  • 27.
    Demo
  • 84. Acceptance Checklist
  • Questions ?
    Elaine van Bergen
    @laneyvb on twitter
    http://laneyvb.blogspot.com
    29.