This document provides an overview of a conference on .NET application modernization with Pivotal and Azure DevOps from October 7-10, 2019 in Austin. It includes presentations from Jason Stevens of Microsoft and Shawn Neal of Pivotal on approaching modernization, the state of .NET, modernization journeys, and using pipelines and environments. There are also sections on Pivotal and Spring logos and brands.

1. .NET Application Modernization
with Pivotal and Azure DevOps
October 7–10, 2019
Austin Convention Center
Jason Stevens - Senior Software Engineer (Microsoft)
Shawn Neal - Principal Solutions Architect (Pivotal)

2. Unless otherwise indicated, these slides are © 2013-2019 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/
Safe Harbor Statement
The following is intended to outline the general direction of Pivotal's offerings. It is intended for information
purposes only and may not be incorporated into any contract. Any information regarding pre-release of
Pivotal offerings, future updates or other planned modifications is subject to ongoing evaluation by Pivotal
and is subject to change. This information is provided without warranty or any kind, express or implied, and
is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making
purchasing decisions regarding Pivotal's offerings. These purchasing decisions should only be based on
features currently available. The development, release, and timing of any features or functionality described
for Pivotal's offerings in this presentation remain at the sole discretion of Pivotal. Pivotal has no obligation to
update forward looking information in this presentation.

3. Unless otherwise indicated, these slides are © 2013-2019 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/
Approaching Modernization

4. State of the .NET Union
.NET Framework is the implementation of .NET that’s installed on over one billion machines and thus needs
to remain as compatible as possible. Because of this, it moves at a slower pace than .NET Core. Even
security and bug fixes can cause breaks in applications because applications depend on the previous
behavior. We will make sure that .NET Framework always supports the latest networking protocols, security
standards, and Windows features.
.NET Core is the open source, cross-platform, and fast-moving version of .NET. Because of its side-by-side
nature it can take changes that we can’t risk applying back to .NET Framework. This means that .NET Core
will get new APIs and language features over time that .NET Framework cannot. At Build we showed a demo
how the file APIs are faster on .NET Core. If we put those same changes into .NET Framework we could
break existing applications, and we don’t want to do that.

5. .NET Framework, .NET Core, and .NET 5
· .NET Framework 4.8 will be the last major version of .NET Framework.
· Given many of the API additions in .NET Standard 2.1 require runtime changes in order to be meaningful,
.NET Framework 4.8 will remain on .NET Standard 2.0
· After .NET Core 3.0 we will not port any more features from .NET Framework.
· New applications should be built on .NET Core. .NET Core is where future investments in .NET will
happen.
· Existing applications are safe to remain on .NET Framework which will be supported. Existing applications
that want to take advantage of the new features in .NET should consider moving to .NET Core.
· .NET 5 = .NET Core vNext
· All new development and feature capabilities will be part of .NET 5, including new C# versions.

7. .NET Portfolios Can Be Complex
Invest : Greenfield Invest/Maintain: Modernize Maintain: Legacy, Lift-and-shift Divest
.NET Framework Traditional
Cloud unfriendly Windows tech:
COM+, GAC, registry, MSIs,
Windows auth, file system, etc.
Older workloads for which there
is no dedicated team.
The .NET Core future
Opportunity for new
patterns like microservices,
functions, event-driven
architectures, etc.
.NET Framework Cloud Ready
More easily transformable to a
cloud-friendly (and eventually,
cloud-native) state.
FunnyQuotes UI WebformsFunnyQuotes UI Core Owin Service

8. FunnyQuotes

9. Modernization Journey
Cloud Friendly Cloud NativeTraditional
On Premise
Windows Server Pets
Installed Dependencies
Large Single Deployable
Scaling is Manual
On Premise/Public Cloud
Windows Server Cattle
Bin Deploy Dependencies
CI/CD
On Premise/Public Cloud
Linux/Windows Containers
Multiple Deployable Units
Service Discovery
Resiliency patterns

10. Finding all 12 Factors in .NET
Codebase in source
control
Dependencies Config
Build, Release, Run Port Binding Stateless Processes Concurrency
Disposability Dev/prod parity Logs Admin Processes
Backing Services
✔ App
Platform
✔ App
Platform
✔ App
Platform
✔ App
Platform
✔ App
Platform
✔ App
Platform
✔ App
Platform
✔ App
Platform
✔ App
Platform
Steeltoe Framework Steeltoe Framework
Steeltoe Framework

11. Unless otherwise indicated, these slides are © 2013-2019 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/
Modernization: The Swift Method

12. Swift Method of Software Modernization
https://www.swiftbird.us/
- Answers the Why of modernization
- Technology Agnostic
- Business outcome focused

13. - Cross-discipline Conversation
- Service Candidates
- Bounded Contexts
- Clumps of Business Events
Boris Exercise SNAP-E
Event
Storming
The Swift Method

14. - Cross-discipline Conversation
- Service Candidates
- Bounded Contexts
- Clumps of Business Events
Boris Exercise SNAP-E
Event
Storming
The Swift Method

15. - Cross-discipline Conversation
- Service Candidates
- Bounded Contexts
- Clumps of Business Events
Boris Exercise SNAP-E
Event
Storming
The Swift Method

16. - Relationship Modeling
- Reveal Target Architecture
- Services, APIs, Events
SNAP-E
Event
Storming
The Swift Method
Boris Exercise

17. - Quickly Document Outcome
- API, Data, External Systems, UI
- Stories, Risks
Event
Storming
The Swift Method
SNAP-EBoris Exercise

18. - Quickly Document Outcome
- API, Data, External Systems, UI
- Stories, Risks
Event
Storming
The Swift Method
SNAP-EBoris Exercise

19. Address Risks
- Changes to legacy code will need
to happen
- Increase Existing Release Velocity
- Leverage platform as a service

20. Unless otherwise indicated, these slides are © 2013-2019 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/
Modernization: Pipelines &
Environments

21. Azure DevOps Overview
Azure Boards delivers a suite of Agile tools to support planning and tracking work, code
defects, and issues using Kanban and Scrum methods
Azure Repos provides Git repositories or Team Foundation Version Control (TFVC) for
source control of your code
Azure Pipelines provides build and release services to support continuous integration and
delivery of your apps
Azure Test Plans provides several tools to test your apps, including manual/exploratory
testing and continuous testing
Azure Artifacts allows teams to share Maven, npm, and NuGet packages from public and
private sources and integrate package sharing into your CI/CD pipelines

22. Pipelines can be connected to
many different repository types.
They’re defined in YAML and
added to the repo for version
control.
Environments are collections of
resources that can be targeted by
a deployment job within the
pipeline.

23. Dev
DevOps Pipeline
Build
Pipeline
Release
Pipeline
UAT
UAT
Dev
Prod
artifactssource
git push
click to approve
click to approve

24. Azure DevOps Pipeline Goals
5
DB
M
igrations
CF
run-task
to
execute
DB
m
igrations
using
bound
service
instance
4
Push
Apps
Blue/Green
deploy
updated
app
code
to
PCF
3
UnitTestsRealunittests
as
defined
by
being
fast,
isolated,and
predictable.
Static
Analysis
Program
m
atically
enforce
style,secure
coding,and
otherpractices
21
Com
pile
+
Package
Com
pile
w
ebsite,libs,and
tests
to
deployable
artifacts
6
Sm
oke
Tests
Use
headless
brow
serorAPItests
to
validate
entire
stack
w
orks
together
Build Pipeline
Release Pipeline

25. Websites (artifact)
Built using standard publish mechanism in .NET
Publish Profile +
1 Compile + Package
/p:DeployDefaultTarget=WebPublish
/p:DeployOnBuild=true
/p:ArtifactStagingDirectory="$(Build.ArtifactStagingDirectory)"
/p:PublishProfile=FolderProfile
<PublishUrl>
$(ArtifactStagingDirectory)/$(MSBuildProjectName)
</PublishUrl>

26. 3 Unit Tests
Static Analysis2

27. Release Pipeline

28. Websites (artifact)
Cloudfoundry tasks
Task Groups
4 Push Apps

29. DB Migration Script/Task
Backwards compatible migrations
On app start?
Cf run-task
5 DB Migrations
$webConfig = "$PSScriptRootWeb.config"
$binDir = "$PSScriptRootbin"
.binmigrate.exe FunnyQuotesCookieDatabase.dll
/startupConfigurationFile=$webConfig /StartUpDirectory=$binDir /verbose

30. Smoke Tests
Execute WebDriver Tests
Real Environment
End to end validation
Similar pattern for UAT and service tests
6 Smoke Tests

31. Build Pipeline Summary
Compile & Package all Commits
Run tests and static analysis
Automatic Deployment to Dev
Deploy all commits automatically
Database Migrations Require Care
Backwards compatibility
Approvals
Require approvals for promotion

32. Dev Stage
- cf push App
- Migrate DB
- Smoke Tests

33. Cf Push Task
steps:
- task: ms-vsts.cloud-foundry-build-extension.cloud-foundry-task.CloudFoundry@1
displayName: 'Push App'
inputs:
cfEndpoint: api.pcf.example.com
org: 'contosoedu'
space: dev
cfManifest: '$(System.DefaultWorkingDirectory)/_sneal.contoso-university/contoso-web/website/manifest.y
additionalDeployArgs: '-n "dev-contoso"'
workingDirectory: '$(System.DefaultWorkingDirectory)/_sneal.contoso-university/contoso-web/website'

34. Cf Push Task

35. Migrate DB Task
steps:
- task: ms-vsts.cloud-foundry-build-extension...
displayName: 'Migrate DB'
inputs:
cfEndpoint: api.pcf.example.com
org: 'contosoedu'
space: dev
cfCommand: 'run-task'
cfArguments: 'contoso "powershell.exe -ExecutionPolicy Bypass -file .migrate.ps1"'

36. Migrate DB Task

37. Smoke Tests
- Headless Chrome Webdriver
- App URL Environment Variable
steps:
- task: VSTest@2
displayName: 'Smoke Tests'
inputs:
uiTests: true
testRunTitle: 'Contoso Smoke Tests'
testAssemblyVer2: ContosoUniversity.SmokeTests.dll
searchFolder: '$(System.DefaultWorkingDirectory)/_sneal.contoso-university/contoso-web/smoketests'

38. Smoke Tests

39. Smoke Tests Summary

40. Deploy to Next Environment

41. Stay Connected.
@snealnet
#springone@s1p

42. Unless otherwise indicated, these slides are © 2013-2019 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/
Body Slide — Light Background
All body text is Proxima Nova Regular
• Subhead
• Level Two
• Level Three
• Level Four
4
2


43. Unless otherwise indicated, these slides are © 2013-2019 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/
Body Slide — Dark Background
All body text is Proxima Nova Regular
• Subhead
• Level Two
• Level Three
• Level Four
4
3

44. Unless otherwise indicated, these slides are © 2013-2019 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/
4
4

// This is Roboto Mono: 42pt or higher please
public class TransferServiceImpl implements TransferService {
public TransferServiceImpl(AccountRepository ar) {
this.accountRepository = ar;
}
…
}

45. Unless otherwise indicated, these slides are © 2013-2019 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/
4
5
// This is Roboto Mono: 42pt or higher please
public class TransferServiceImpl implements TransferService {
public TransferServiceImpl(AccountRepository ar) {
this.accountRepository = ar;
}
…
}

46. Unless otherwise indicated, these slides are © 2013-2019 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/
Design Assets

47. Unless otherwise indicated, these slides are © 2013-2019 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/
Pivotal Product Logo Library
One-color versions

48. Unless otherwise indicated, these slides are © 2013-2019 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/
Spring Logo and Project Icons
Spring
Framework
Spring
Security
Spring
Data
Spring
Batch
Spring
Integration
Project
Reactor
Spring
AMQP
Spring
Hateoas
Spring
Mobile
Spring
Android
Spring
Social
Spring
Web Services
Spring
Web Flow
Spring
XD
Spring
Boot
Spring
LDAP
Spring Tool
Suite
Spring Cloud
Data Flow
Spring
Kafka
Spring
Cloud

49. Unless otherwise indicated, these slides are © 2013-2019 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/
Icon Library
Router Team Metrics Service Broker Server Permissions Database
Cloud Mobile Workstation Browser Laptop IoT Security
CLI User 1 User 2 User 3 Alert
Star Deploy/Ship
Agile Container Microservice Monolith Application
File / Log
Checklist

50. Unless otherwise indicated, these slides are © 2013-2019 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/
Icon Library

51. Unless otherwise indicated, these slides are © 2013-2019 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/
Event Logos
On dark
Horizontal Vertical
On light
On mint

52. Unless otherwise indicated, these slides are © 2013-2019 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/
Looking for other logos?
Visit our BrandFolder >
(pw: keepitsimple)
There you’ll find all our:
• Product Logos
• OSS Logos
• PCF Service Icons
• Brand Fonts & Colors
• And more!

53. Unless otherwise indicated, these slides are © 2013-2019 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/
Brand Colors
SpringOne Platform 2019
Primary Colors
Spring
Brand Color
Pivotal
Brand Color
#1ab9a5ff
#13377dff
#ffffffff
#6db33fff #1ab9a5ff
#00253eff

54. Unless otherwise indicated, these slides are © 2013-2019 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/
Sample Table
5
4
2007 2008 2009 2010
Category 1 2.4 6.4 4.1 6.6
Category 2 8.2 4.5 3.2 3.8
Category 3 4.6 3.2 1.9 9.6
Category 4 6.7 3.3 3.4 2.2
Category 5 4.3 5.6 7.1 3.4

55. Unless otherwise indicated, these slides are © 2013-2019 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/
Sample Table
5
5
2007 2008 2009 2010
Category 1 2.4 6.4 4.1 6.6
Category 2 8.2 4.5 3.2 3.8
Category 3 4.6 3.2 1.9 9.6
Category 4 6.7 3.3 3.4 2.2
Category 5 4.3 5.6 7.1 3.4