Philadelphia SharePoint Community<br /><ul><li>SharePoint (2010 & 2007)
Administrators
Developers
Architect Council after every meeting
Free Training before every meeting
www.TriStateSharePoint.com [coming in December]
Hosted blogs for members
Community Forums
Exclusive content / pre-release content
Meeting recordings
Free training
www.officegeeks.org/philly [until December]</li></ul>CONTACT: tss@mannsoftware.com<br />TWITTER: @tristateSP<br /><ul><li>...
Todd Bleeker
Rob Bogue
Eric Shupps
John Holliday
Ben Curry
Asif Rehmani
Paul Schaeflein
Brett Lonsdale
Nick Swan
(and more)
Topics
Upgrade to 2010
SharePoint 2010 Development
No-Code Workflows
Client object model
Records Management
Business Connectivity Services
Sandbox Solutions
SharePoint Tools in Visual Studio 2010
Social Media
List Enhancements
Workflows
Database and Infrastructure</li></li></ul><li>Case Study: Upgrading SLFE from 2007 to 2010<br />Shai Petel (shai@kwizcom.c...
Content<br />Building a new solution<br />Upgrading an existing solution<br />Version management<br />
Goals<br />In this session you will learn about the new VS2010 extensions for WSS<br />You will learn how to migrate your ...
Content<br />Building a new solution<br />Creating a new solution<br />Choose a project template<br />Setup trust level<br...
Building a New Solution Before you begin…<br />Is your team ready for 2010?<br />Silverlight, Ajax, JSON<br />Visual web p...
Building a New Solution Before you begin…<br /><ul><li>SharePoint web parts are still supported for backwards compatibility
Do not change base for existing web parts!!!</li></ul>Creating a new web part?<br />Inherit from ASP.NET!<br />
Building a New SolutionBefore you begin…<br />
Building a New Solution Before you begin…<br />Install all components on developer machine<br />
Building a New Solution Before you begin…<br />Install developer components on development client and use remote debugger ...
Building a New Solution Before you begin…<br />Virtualize! (Recommended)<br />
Content<br />Building a new solution<br />Creating a new solution<br />Choose a project template<br />Setup trust level<br...
Building a New SolutionCreating a new solution<br />Open VS2010<br />
Building a New SolutionCreating a new solution<br />Click on new project. Go to:<br />C# -&gt; SharePoint -&gt; 2010 templ...
Content<br />Building a new solution<br />Creating a new solution<br />Choose a project template<br />Setup trust level<br...
Building a New SolutionChoose a project template<br />There are a lot of new project templates to choose from!<br />But fe...
Introducing<br />Visual Web Part<br />
Building a New SolutionChoose template: visual web part<br />This project template cannot be sandboxed<br />
Building a New SolutionChoose template: visual web part<br />Project created with all web part files for you<br />
Building a New SolutionChoose template: visual web part<br />A feature will be created for you automatically<br />
Building a New SolutionChoose template: visual web part<br />A package will be created for you automatically<br />
Building a New SolutionChoose template: event receiver<br />This project template can be sandboxed<br />
Building a New SolutionChoose template: event receiver<br />“Create project” Wizard<br />New types of receivers<br />New e...
Building a New SolutionChoose template: event receiver<br />Adds all needed files for you<br />
Introducing<br />Business Data Catalogue Tools<br />
Building a New SolutionChoose template: BCS model<br />This project template can be sandboxed<br />
Building a New SolutionChoose template: BCS model<br />BCS editing tools<br />
Building a New SolutionChoose template: BCS model<br />Packaged and deployed as a farm level feature<br />
Building a New SolutionChoose template: content type<br />This project template can be sandboxed<br />
Building a New SolutionChoose template: content type<br />“Create content type” Wizard<br />More work needed on the wizard...
Building a New SolutionChoose template: list definition<br />This project template cannot be sandboxed<br />
Building a New SolutionChoose template: list definition<br />“Create List Def.” Wizard<br />
Building a New SolutionChoose template: content type<br />Schema File<br />Create Elements file for feature<br />Optional:...
Building a New SolutionChoose template: content type<br />Packaged and deployed as a web feature<br />
Building a New SolutionChoose template: workflow<br />This project template cannot be sandboxed<br />
Building a New SolutionChoose template: workflow<br />Sequential workflow is designed to execute a series of predefined st...
Building a New SolutionChoose template: workflow<br />“State machine” wizard<br />Choose history and tasks lists.* Also ch...
Building a New SolutionChoose template: workflow<br />Designer has different options for site and list workflows<br />
Building a New SolutionChoose template: workflow<br />Add sequential workflow, with its own designer<br />
Building a New SolutionChoose template: workflow<br />Creates separate elements file for each workflow<br />
Content<br />Building a new solution<br />Creating a new solution<br />Choose a project template<br />Setup trust level<br...
Introducing<br />Your very own sandbox!<br />
Building a New SolutionSetup trust level<br />Choose your destiny<br />
Building a New SolutionSetup trust level<br />To trust, or not to trust?<br />Sandbox solutions is a way for you to deploy...
Building a New SolutionSetup trust level<br />What does this setting change?<br />This setting does not get written to WSP...
Building a New SolutionSetup trust level<br />What is supported within a sandbox solution?<br />List Definitions, List Ins...
Building a New SolutionSetup trust level<br />What is not supported within a sandbox solution?<br />Mapped folders (14 hiv...
Building a New SolutionSetup trust level<br />How do I deploy a sandbox solution?<br />Upload to Solutions gallery<br />Ac...
Building a New SolutionSetup trust level<br />Cannot activate solution?<br />Go to central administration and make sure wi...
Building a New SolutionSetup trust level<br />Keep in mind:<br />Deploying a sandbox solution automatically activates feat...
Content<br />Building a new solution<br />Creating a new solution<br />Choose a project template<br />Setup trust level<br...
Building a New SolutionAdding new components<br />It is extremely easy to add any component to any project you like<br />T...
Building a New SolutionAdding new components<br />Add mapped folder<br />
Building a New SolutionAdding new components<br />Add other components<br />
Content<br />Building a new solution<br />Creating a new solution<br />Choose a project template<br />Setup trust level<br...
Building a New SolutionOne-click deploy or package<br />Feature and Package editors available<br />
Building a New SolutionOne-click deploy or package<br />Project menu allows you to build, deploy to development server, an...
Upcoming SlideShare
Loading in...5
×

Upgrading SLFE from 2007 to 2010

1,040

Published on

Shai Petel's session at SPS Philly was all about upgrading to SharePoint 2010 using KWIzCom's SharePoint List Forms Extension Feature as an example.

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
1,040
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
11
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • Upgrading Philly Office Geeks in DecemberWorld-class speakersFocus on SharePoint 2010 and 2007Jump start Philly SharePoint communityRegional focus – looking into different meeting locations/optionsInvestigating various virtual meeting options
  • This is my personal experience upgrading SLFE from 2007 to 2010.(what will be different in my presentation is that it is based on actual migration I did and the lessons I learned, hope it can save you some time and allow to you take the right decisions on your projects today that will prepare you for the future)
  • These are the topics…1st quick overview on VSeWSS2010, allow us to prepare for the next topic, which is the main one…Last – versioning, my personal goal to make all my customer work like an ISV
  • * Sandbox See below
  • 2 clicks
  • Farm level resources:SQL, file system, 14 hive, schema filesEasy to mess up:Developer has full control and can make his environment. Unusable and cannot revert it back to original form.Hard to backup:Server, not code. For code we use VSS.New: Supported under windows 764bit for developers!!!
  • No worries environment:(can restore to original state with no problems so feel free to mess up the server!
  • 1 click
  • You will need to decide what type of project you wish to create.(Visual web part, list/site definition, event handler, workflow, BCS and much more)If you are not sure you can start with an empty one.For advanced solutions that has many different customizations (web parts, list definitions and more…) just pick any project and add other components to it after you create the project.
  • Files:CS file for web partASCX and ASCX.CS file for user control*.webpart XML fileElements XML file for use in featuresNote: All web part related files are created within the same folder to help you keep resources organized.4 clicks
  • Note:New feature designer!The elements file from within the web part is recognized and added into your feature.
  • Note:New package designer!All features and elements in this projectare recognized and added into your package.1 click
  • When creating this type of project there is a wizard to guide you through the creation of the solution.Note: new types of event receivers.Note: New events to handle in existing event receivers!2 clicks
  • Elements file within the receiver’s folder to be used in features.Receiver’s handler code file.1 Click
  • BCS – Business connectivity Services (former BDC)1 click
  • 1 Click
  • Just intelli-sense… no real wizard.2 Clicks
  • no real wizard. But creates all files for you (list def, feature elements, and list instance)
  • 2 clicks
  • no real wizard. But creates all files for you (list def, feature elements, and list instance)
  • 1 click
  • 1 Click
  • 1 Click
  • Deploying a sandbox solution that has any of the forbidden content will succeed but that content will not be deployed.Application pages: no pages into layouts since no mapped folders.Pages with embedded code are not supported from data base – security.
  • 1 click
  • 1 click
  • 1 click
  • 1 click
  • Updating existing ones done using file system priority trick still working in 2010.We used MSI installer due to some limitations in WSP
  • 1 Click
  • All in XML,Added images, CSS and ASCXShow live, visual studio
  • Show the upgraded componentsShow the new components
  • Show live
  • Show the new Ribbon UI, and shot settings pagesShow it working in the new item popupShow next / prev item based on view in tasksShow groupingShow disabled field
  • 2 Clicks
  • 1 Click
  • 1 Click
  • Note: code does not get imported.3 clicks
  • After import is done – still need to import code manually and set namespace / assembly evidence
  • Import SLFE WSP package,Show what is created (skeleton),Manually add code files and set namespace, assembly evidence.
  • Pages, web parts, event handlers – do not support assembly version changes.Version in features for upgrade operations if needed. Change only when needed.Version in code, to show in about to identify current running version easily. Change every time.
  • 2 clicks
  • 1 click after auto
  • Overall, my personal experience was very positive,The beta is in great shape and migrating customizations looks simple.
  • Upgrading SLFE from 2007 to 2010

    1. 1. Philadelphia SharePoint Community<br /><ul><li>SharePoint (2010 & 2007)
    2. 2. Administrators
    3. 3. Developers
    4. 4. Architect Council after every meeting
    5. 5. Free Training before every meeting
    6. 6. www.TriStateSharePoint.com [coming in December]
    7. 7. Hosted blogs for members
    8. 8. Community Forums
    9. 9. Exclusive content / pre-release content
    10. 10. Meeting recordings
    11. 11. Free training
    12. 12. www.officegeeks.org/philly [until December]</li></ul>CONTACT: tss@mannsoftware.com<br />TWITTER: @tristateSP<br /><ul><li>Scheduled Speakers
    13. 13. Todd Bleeker
    14. 14. Rob Bogue
    15. 15. Eric Shupps
    16. 16. John Holliday
    17. 17. Ben Curry
    18. 18. Asif Rehmani
    19. 19. Paul Schaeflein
    20. 20. Brett Lonsdale
    21. 21. Nick Swan
    22. 22. (and more)
    23. 23. Topics
    24. 24. Upgrade to 2010
    25. 25. SharePoint 2010 Development
    26. 26. No-Code Workflows
    27. 27. Client object model
    28. 28. Records Management
    29. 29. Business Connectivity Services
    30. 30. Sandbox Solutions
    31. 31. SharePoint Tools in Visual Studio 2010
    32. 32. Social Media
    33. 33. List Enhancements
    34. 34. Workflows
    35. 35. Database and Infrastructure</li></li></ul><li>Case Study: Upgrading SLFE from 2007 to 2010<br />Shai Petel (shai@kwizcom.com)<br />VP R&D, Microsoft Certified Trainer<br />KWizCom Corporation<br />
    36. 36. Content<br />Building a new solution<br />Upgrading an existing solution<br />Version management<br />
    37. 37. Goals<br />In this session you will learn about the new VS2010 extensions for WSS<br />You will learn how to migrate your existing solutions into the new environment reducing the migration process time to minimum.<br />This session will allow you to make better decisions on your current solutions for 2007 today that will make the transition to 2010 easy and simple.<br />
    38. 38. Content<br />Building a new solution<br />Creating a new solution<br />Choose a project template<br />Setup trust level<br />Adding new components<br />One-click deploy or package<br />Upgrading an existing solution<br />Version management<br />
    39. 39. Building a New Solution Before you begin…<br />Is your team ready for 2010?<br />Silverlight, Ajax, JSON<br />Visual web parts! (or is it?)<br />Prepare to be hosted!<br />Limit customization to site collection level<br />Prefer to support sandboxed solutions*<br />
    40. 40. Building a New Solution Before you begin…<br /><ul><li>SharePoint web parts are still supported for backwards compatibility
    41. 41. Do not change base for existing web parts!!!</li></ul>Creating a new web part?<br />Inherit from ASP.NET!<br />
    42. 42. Building a New SolutionBefore you begin…<br />
    43. 43. Building a New Solution Before you begin…<br />Install all components on developer machine<br />
    44. 44. Building a New Solution Before you begin…<br />Install developer components on development client and use remote debugger to connect to development server (not so bad, but still…)<br />
    45. 45. Building a New Solution Before you begin…<br />Virtualize! (Recommended)<br />
    46. 46. Content<br />Building a new solution<br />Creating a new solution<br />Choose a project template<br />Setup trust level<br />Adding new components<br />One-click deploy or package<br />Upgrading an existing solution<br />Version management<br />
    47. 47. Building a New SolutionCreating a new solution<br />Open VS2010<br />
    48. 48. Building a New SolutionCreating a new solution<br />Click on new project. Go to:<br />C# -&gt; SharePoint -&gt; 2010 templates<br />
    49. 49. Content<br />Building a new solution<br />Creating a new solution<br />Choose a project template<br />Setup trust level<br />Adding new components<br />One-click deploy or package<br />Upgrading an existing solution<br />Version management<br />
    50. 50. Building a New SolutionChoose a project template<br />There are a lot of new project templates to choose from!<br />But fear not – You can easily add any component to any project later<br />
    51. 51. Introducing<br />Visual Web Part<br />
    52. 52. Building a New SolutionChoose template: visual web part<br />This project template cannot be sandboxed<br />
    53. 53. Building a New SolutionChoose template: visual web part<br />Project created with all web part files for you<br />
    54. 54. Building a New SolutionChoose template: visual web part<br />A feature will be created for you automatically<br />
    55. 55. Building a New SolutionChoose template: visual web part<br />A package will be created for you automatically<br />
    56. 56. Building a New SolutionChoose template: event receiver<br />This project template can be sandboxed<br />
    57. 57. Building a New SolutionChoose template: event receiver<br />“Create project” Wizard<br />New types of receivers<br />New events to handle!<br />
    58. 58. Building a New SolutionChoose template: event receiver<br />Adds all needed files for you<br />
    59. 59. Introducing<br />Business Data Catalogue Tools<br />
    60. 60. Building a New SolutionChoose template: BCS model<br />This project template can be sandboxed<br />
    61. 61. Building a New SolutionChoose template: BCS model<br />BCS editing tools<br />
    62. 62. Building a New SolutionChoose template: BCS model<br />Packaged and deployed as a farm level feature<br />
    63. 63. Building a New SolutionChoose template: content type<br />This project template can be sandboxed<br />
    64. 64. Building a New SolutionChoose template: content type<br />“Create content type” Wizard<br />More work needed on the wizard though… <br />
    65. 65. Building a New SolutionChoose template: list definition<br />This project template cannot be sandboxed<br />
    66. 66. Building a New SolutionChoose template: list definition<br />“Create List Def.” Wizard<br />
    67. 67. Building a New SolutionChoose template: content type<br />Schema File<br />Create Elements file for feature<br />Optional: Create list instance XML<br />
    68. 68. Building a New SolutionChoose template: content type<br />Packaged and deployed as a web feature<br />
    69. 69. Building a New SolutionChoose template: workflow<br />This project template cannot be sandboxed<br />
    70. 70. Building a New SolutionChoose template: workflow<br />Sequential workflow is designed to execute a series of predefined steps to accomplish a certain task<br />State machine workflows are designed to work in event-driven scenarios. A state machine workflow contains two or more states, with one state being the active state at any given time<br />
    71. 71. Building a New SolutionChoose template: workflow<br />“State machine” wizard<br />Choose history and tasks lists.* Also choose a list if you selected a list workflow type<br />Workflow initiation options<br />
    72. 72. Building a New SolutionChoose template: workflow<br />Designer has different options for site and list workflows<br />
    73. 73. Building a New SolutionChoose template: workflow<br />Add sequential workflow, with its own designer<br />
    74. 74. Building a New SolutionChoose template: workflow<br />Creates separate elements file for each workflow<br />
    75. 75. Content<br />Building a new solution<br />Creating a new solution<br />Choose a project template<br />Setup trust level<br />Adding new components<br />One-click deploy or package<br />Upgrading an existing solution<br />Version management<br />
    76. 76. Introducing<br />Your very own sandbox!<br />
    77. 77. Building a New SolutionSetup trust level<br />Choose your destiny<br />
    78. 78. Building a New SolutionSetup trust level<br />To trust, or not to trust?<br />Sandbox solutions is a way for you to deploy a set of features and components to your SharePoint site collection that will have no effect on other site collections<br />Sandbox solutions have limited support for extensibility and not all SharePoint customizations are allowed<br />Sandboxed solutions can be installed and deployed by site owner from site settings<br />
    79. 79. Building a New SolutionSetup trust level<br />What does this setting change?<br />This setting does not get written to WSP package, but will allow VS to validate your content is supported within a sandboxes solution<br />Solution assemblies within a sandboxed solution are not installed to GAC/Bin, and not running on W3WP process. Instead they run under SPUCWorkerProcess<br />Sandboxed solutions can be deployed as a full-trusted solution as well<br />
    80. 80. Building a New SolutionSetup trust level<br />What is supported within a sandbox solution?<br />List Definitions, List Instances, Content Types/Fields<br />Web Parts (non visual)<br />Event receivers: Item, List or Web<br />Declarative workflows, Custom Actions (Ribbon)<br />Onet.xml, WebTemplate feature element (instead of Webtemp.xml) allows for site collection level site definitions!<br />More…<br />
    81. 81. Building a New SolutionSetup trust level<br />What is not supported within a sandbox solution?<br />Mapped folders (14 hive)<br />Some API will not work in sandboxed mode<br />Visual Web Parts<br />Application Pages<br />Custom Action Group<br />HideCustomAction element<br />Web Application/Farm-scoped features<br />Workflows with code<br />
    82. 82. Building a New SolutionSetup trust level<br />How do I deploy a sandbox solution?<br />Upload to Solutions gallery<br />Activate<br />
    83. 83. Building a New SolutionSetup trust level<br />Cannot activate solution?<br />Go to central administration and make sure windows SharePoint user code service is started<br />
    84. 84. Building a New SolutionSetup trust level<br />Keep in mind:<br />Deploying a sandbox solution automatically activates features within (unless specifically specified not to in the feature)<br />To disable support for sandbox solutions simply stop the user code service<br />Upgrading sandbox solutions are done manually site collection at a time<br />
    85. 85. Content<br />Building a new solution<br />Creating a new solution<br />Choose a project template<br />Setup trust level<br />Adding new components<br />One-click deploy or package<br />Upgrading an existing solution<br />Version management<br />
    86. 86. Building a New SolutionAdding new components<br />It is extremely easy to add any component to any project you like<br />This allows you to easily create more complex solutions that includes several types of customizations such as:<br />Feature – for activation<br />Web parts – for visual UI<br />Lists and list definitions for storing data<br />Field types, event handlers, workflows and much more!<br />
    87. 87. Building a New SolutionAdding new components<br />Add mapped folder<br />
    88. 88. Building a New SolutionAdding new components<br />Add other components<br />
    89. 89. Content<br />Building a new solution<br />Creating a new solution<br />Choose a project template<br />Setup trust level<br />Adding new components<br />One-click deploy or package<br />Upgrading an existing solution<br />Version management<br />
    90. 90. Building a New SolutionOne-click deploy or package<br />Feature and Package editors available<br />
    91. 91. Building a New SolutionOne-click deploy or package<br />Project menu allows you to build, deploy to development server, and to package using a WSP<br />Build = compile code only<br />Package = compiles and builds the WSP package<br />Deploy = compile, package anddeploy the package (customizable!)<br />Retract = removes the solutionpackage from server<br />
    92. 92. Content<br />Building a new solution<br />Upgrading an existing solution<br />Upgrading a non-VSeWSS solution<br />Upgrading a 2005/2008 VSeWSS solution<br />Upgrading a WSP package<br />Version management<br />
    93. 93. Upgrading an Existing SolutionUpgrading an existing solution<br />
    94. 94. Content<br />Building a new solution<br />Upgrading an existing solution<br />Upgrading a non-VSeWSSsolution<br />Upgrading a 2005/2008 VSeWSS solution<br />Upgrading a WSP package<br />Version management<br />
    95. 95. Upgrading an Existing SolutionUpgrading non-VSeWSS solution<br />Case study: Upgrading KWizCom SharePoint List Forms Extensions<br />What we had in 2007:<br />controltemplates ASCX files. New control templates and updating existing ones*<br />Application settings pages<br />List settings link<br />Feature activated, MSI installer<br />External references to utilities/shared resources<br />
    96. 96. Upgrading an Existing SolutionUpgrading non-VSeWSS solution<br />SLFE version 1.*.*<br />
    97. 97. Upgrading an Existing SolutionUpgrading non-VSeWSS solution<br />What we added in 2010:<br />List settings ribbon buttons<br />Add CSS file using Delegate<br />WSP packaging<br />
    98. 98. Live Demo<br />SLFE Project<br />Live demo of SLFE in Visual Studio 2010<br />
    99. 99. Upgrading an Existing SolutionUpgrading non-VSeWSS solution<br />2010 New UI<br />Ribbon (resizable)<br />Using image store filesand CSS class<br />
    100. 100. Live Demo<br />SLFE Solution<br />Live demo of SLFE in SharePoint<br />
    101. 101. Upgrading an Existing SolutionUpgrading non-VSeWSS solution<br />Conclusion<br />In order to make the most of VS2010 and VS2010 extensions for WSS its best to build a new project skeleton and import existing code into it.<br />If you already have a WSP package you can use it to build your project skeleton from it (reverse engineer) but your .NET code will not be included!<br />
    102. 102. Upgrading an Existing SolutionUpgrading non-VSeWSS solution<br />Steps for upgrading a project<br />Estimated ~1 hour to 4 hours of 1 developer to have the solution ready for packaging.<br />
    103. 103. Content<br />Building a new solution<br />Upgrading an existing solution<br />Upgrading a non-VSeWSSsolution<br />Upgrading a 2005/2008 VSeWSSsolution<br />Upgrading a WSP package<br />Version management<br />
    104. 104. Upgrading an Existing SolutionUpgrading 2005/2008 VSeWSS<br />Unfortunately, you cannot convert VS2005/2008 projects using visual studio alone<br />Trying to do so will invoke this error:“The project type is not supported by this installation.”<br />
    105. 105. Upgrading an Existing SolutionUpgrading 2005/2008 VSeWSS<br />But fear not! VSeWSS2010 comes with a conversion tool (VSeWSS 2008 only).<br />For all other projects that used WSP for deployment - This next option might be what you are looking for!<br />
    106. 106. Content<br />Building a new solution<br />Upgrading an existing solution<br />Upgrading a non-VSeWSSsolution<br />Upgrading a 2005/2008 VSeWSSsolution<br />Upgrading a WSP package<br />Version management<br />
    107. 107. Upgrading an Existing SolutionUpgrading a WSP package<br />If you have a WSP packaged solution, you can import it into 2010!<br />
    108. 108. Upgrading an Existing SolutionUpgrading a WSP package<br />Import wizard<br />Your code does<br />not get<br />imported!<br />
    109. 109. Upgrading an Existing SolutionUpgrading a WSP package<br />The import process will build your skeleton for you<br />After the import is done, some work is needed<br />
    110. 110. Live Demo<br />SLFE Solution<br />Importing WSP package<br />
    111. 111. Upgrading an Existing SolutionImporting a WSP package<br />
    112. 112. Content<br />Building a new solution<br />Upgrading an existing solution<br />Version management<br />How can I mark versions<br />Shared resources<br />Upgrade / downgrade solution version<br />
    113. 113. Version ManagementVersion management<br />Why do we need version management?<br />Tractability of bugs or changes<br />Perform upgrade operations on existing installations (add a field, create hidden list etc.)<br />Monitor Dev, Staging and production deployment running code<br />Not for ISV only!<br />In house development team? Get used to working with versioned packages!<br />
    114. 114. Content<br />Building a new solution<br />Upgrading an existing solution<br />Version management<br />How can I mark versions<br />Shared resources<br />Upgrade / downgrade solution version<br />
    115. 115. Version ManagementHow can I mark versions<br />Cannot change assembly version!<br />Currently no supportfor marking package,but you can markfeatures:<br />Mark versionnumber in yourcode:<br />
    116. 116. Content<br />Building a new solution<br />Upgrading an existing solution<br />Version management<br />How can I mark versions<br />Shared resources<br />Upgrade / downgrade solution version<br />
    117. 117. Version ManagementShared resources<br />You may need to add shared resources to your projects<br />DLL’s (utility classes, base classes)<br />Sandbox – no problem<br />GAC – no problem<br />BIN deployment – version collisions may occur.<br />Shared resources (Images/CSS files)<br />Use sub folders with utilities version number.For example:/_layouts/KWizCom_Shared_2.0.01<br />
    118. 118. Content<br />Building a new solution<br />Upgrading an existing solution<br />Version management<br />How can I mark versions<br />Shared resources<br />Upgrade / downgrade solution version<br />
    119. 119. Version ManagementUp/downgrade solution version<br />Built in support for upgrade operations!<br />SharePoint will allow mark if feature requires upgrade<br />Many upgrade operations supported, and custom upgrade handlers can be coded<br />
    120. 120. Version ManagementUp/downgrade solution version<br />Upgrading / downgrading is easy!<br />Once you deploy several versions of same solution you will be able to upgrade instead of activate!<br />
    121. 121. Content<br />Building a new solution<br />Upgrading an existing solution<br />Version management<br />
    122. 122. Summary<br />You now have real-world experience in upgrading components into 2010<br />There is a lot more to see<br />Come visit us at our booth for more information and for 1 on 1 talks!<br />Overall, It’s been a pleasure!<br />
    123. 123. Contact Us<br />For more information on SharePoint 2010 please don’t hesitate to contact us!<br /><ul><li>At our booth out side
    124. 124. Email: shai@kwizcom.com
    125. 125. Online: http://www.kwizcom.com
    126. 126. Blog: http://kwizcom.blogspot.com</li></ul>* Learn * Plan * Deploy * Build *<br />Call to learn how KWizCom can assist you!<br />
    127. 127. Learn More about SharePoint 2010<br />Information forIT Prosat TechNet<br />http://MSSharePointITPro.com<br />Information forDevelopersat MSDN<br />http://MSSharePointDeveloper.com<br />Information forEveryone<br />http://SharePoint.Microsoft.com<br />
    128. 128. KWizCom<br />Contact:<br />Shai Petel (shai@kwizcom.com)<br />VP R&D, Microsoft Certified Trainer<br />KWizCom Corporation<br />
    1. A particular slide catching your eye?

      Clipping is a handy way to collect important slides you want to go back to later.

    ×