Challenges and Opportunities in Migrating to ASP.NET Core
Migrating to ASP.NET Core
Migrating to ASP.NET Core
Challenges & Opportunities
Dino Esposito
#NoEstimates
#LongWayToTipperary
#WorkInProgress
#PlansSubjectToChange
See You in H2 2017
(and that will be at most v2.0)
.NET Core and friends
is more crucial for Microsoft
than the rest of us
(but it’s still a relevant update)
FOR
EVERYBODY
?
It’s a relevant update …
Migration
?
•
X
-
p
l
a
t
f
o
r
m
•
I
m
p
r
o
v
e
d
A
P
I
•
S
a
m
e
M
V
C
p
a
r
a
d
i
g
m
M
V
C
o
n
l
y
C
#
o
n
l
y
N
e
w
A
P
I
N
e
w
h
o
s
t
i
n
g
m
o
d
e
l
N
o
I
I
S
-
c
e
n
t
r
i
s
m
N
e
w
.
N
E
T
F
X
Challenges
Opportunities
YOU DECIDE.
What We Have Now…
AD HOC
system.web
ASP.NET
W
e
b
A
P
I
.
N
E
T
F
r
a
m
e
w
o
r
k
IIS
OWIN
W
e
b
F
o
r
m
s
M
V
C
ASP.NET
.
N
E
T
F
r
a
m
e
w
o
r
k
WEB SERVER
OWIN
M
V
C
INTEGRATION
Changes
T
i
g
h
t
c
o
u
p
l
i
n
g
b
e
t
w
e
e
n
A
S
P
.
N
E
T
a
n
d
I
I
S
•
Presented as a big win only a few years ago
P
l
a
t
f
o
r
m
d
e
p
e
n
d
e
n
c
e
•
Windows only
S
y
s
t
e
m
.
w
e
b
i
s
l
e
g
a
c
y
c
o
d
e
•
Devised back in 1997
When they took
SYSTEM.WEB apart …
•
From EMPTY to
FUNCTIONAL in Visual
Studio 2015
ASP.NET CORE has a nice programming
interface and an interesting set of new
programming features.
Would be the perfect vN+1
It’s a complete change of platform and to
some extent also tools and habits
Migration Facts
F
i
n
d
o
u
t
w
h
o
m
o
v
e
d
t
h
e
c
h
e
e
s
e
•
ASP.NET CORE has a high cost of setup
•
Costs tend to zero over time
F
i
n
d
o
u
t
w
h
y
t
h
e
y
m
o
v
e
d
t
h
e
c
h
e
e
s
e
•
Some good reasons
•
Some "other" reasons
Good Reasons
N
e
w
r
u
n
t
i
m
e
e
n
v
i
r
o
n
m
e
n
t
•
Unification of ASP.NET and WebAPI pipelines
•
Old system.web dropped
•
Memory footprint
A
l
l
w
e
b
a
p
p
s
e
r
v
i
c
e
s
d
e
c
o
u
p
l
e
d
t
o
i
n
t
e
r
f
a
c
e
s
•
Authentication
•
Static files management
•
Exception handling and logging
Microsoft’s Motivation
T
a
k
i
n
g
m
o
r
e
p
e
o
p
l
e
t
o
t
h
e
c
l
o
u
d
L
o
y
a
l
c
u
s
t
o
m
e
r
s
m
o
v
e
d
a
l
r
e
a
d
y
t
o
A
z
u
r
e
o
r
a
r
e
l
i
k
e
l
y
t
o
d
o
i
t
W
h
a
t
a
b
o
u
t
o
t
h
e
r
p
e
r
s
p
e
c
t
i
v
e
c
u
s
t
o
m
e
r
s
?
•
Oh yes, they’re using Mac computers and Linux …
DECISION POINT
You and IIS
H
a
v
i
n
g
p
r
o
b
l
e
m
s
w
i
t
h
I
I
S
?
•
Looking for Apache Server?
S
o
m
e
n
o
d
e
.
j
s
n
o
s
t
a
l
g
i
a
?
•
Wishing to call yourself a "geek" again?
H
a
v
i
n
g
p
r
o
b
l
e
m
s
w
i
t
h
W
e
b
F
o
r
m
s
?
•
Looked into ASP.NET MVC and/or plain SPAs?
H
a
v
i
n
g
p
r
o
b
l
e
m
s
w
i
t
h
A
S
P
.
N
E
T
M
V
C
?
•
Looked into Web Forms and/or plain SPAs?
S
u
r
e
i
t
’
s
n
o
t
y
o
u
r
c
o
d
e
t
h
a
t
s
u
c
k
s
?
DECISION POINT
You and ASP.NET
There’s not much left that
can be added to ASP.NET
•
Battle-tested, well-known and stable
•
Room for small improvements
–
Razor
–
DI
–
Azure integration
–
Pipeline customization
What if you’re planning a
complete rewrite?
What’s different?
C
o
n
f
i
g
u
r
a
t
i
o
n
,
s
t
a
r
t
u
p
,
p
i
p
e
l
i
n
e
•
Free IoC though
•
Full rewrite of HTTP modules (including tools)
N
e
w
w
a
y
s
o
f
d
o
i
n
g
o
l
d
t
h
i
n
g
s
•
Core authentication (except Identity)
•
Embedded resources
•
Project management
D
e
v
e
l
o
p
m
e
n
t
e
x
p
e
r
i
e
n
c
e
•
Test, build, deploy, manage dependencies
ASP.NET MVC
N
o
s
u
p
p
o
r
t
f
o
r
W
e
b
F
o
r
m
s
M
i
g
r
a
t
i
n
g
c
o
d
e
i
s
o
v
e
r
a
l
l
d
o
a
b
l
e
S
w
i
t
c
h
i
n
g
t
o
A
S
P
.
N
E
T
C
o
r
e
m
i
n
d
s
e
t
i
s
e
a
s
y
•
Aside a few new APIs to learn, it’s all the same
•
Plus minor features in Razor
The underlying .NET
.
N
E
T
F
r
a
m
e
w
o
r
k
•
As above
.
N
E
T
C
o
r
e
(
x
-
p
l
a
t
f
o
r
m
)
•
EF Core
•
No SignalR
•
No 3
rd
party frameworks (if not ported)
•
Subset of the .NET Framework (and no VB)
P
l
a
n
m
o
v
i
n
g
t
o
A
S
P
.
N
E
T
C
o
r
e
e
s
p
e
c
i
a
l
l
y
i
f
y
o
u
’
r
e
e
x
p
e
r
i
e
n
c
i
n
g
a
n
y
o
f
t
h
e
f
o
l
l
o
w
i
n
g
:
•
Issues with IIS and system.web
•
Issues with the app on the cloud
•
Performance issues in the core runtime
•
… or see a business opportunity in x-plat
hosting
Inevitably the future.
But nobody knows when
the future will be.
Delve into the world of ASP.NET Core migration as Dino Esposito explores the challenges and opportunities it presents. From platform independence to improved APIs, discover the shifts in the MVC paradigm and embrace the evolving landscape of .NET development.
Download Presentation
Please find below an Image/Link to download the presentation.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author. Download presentation by click this link. If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.
E N D
Presentation Transcript
Migrating to ASP.NET Core Challenges & Opportunities Dino Esposito @despos | facebook.com/naa4e
#NoEstimates #LongWayToTipperary #WorkInProgress #PlansSubjectToChange See You in H2 2017 (and that will be at most v2.0) @despos | facebook.com/naa4e
.NET Core and friends is more crucial for Microsoft than the rest of us (but it s still a relevant update) @despos | facebook.com/naa4e
Its a relevant update FOR EVERYBODY? @despos | facebook.com/naa4e
Migration? Challenges Opportunities X-platform Improved API Same MVC paradigm MVC only C# only New API New hosting model No IIS-centrism New .NET FX YOU DECIDE. @despos | facebook.com/naa4e
What We Have Now @despos | facebook.com/naa4e
.NET Framework ASP.NET INTEGRATED PIPELINE Web Web API API Web Web Forms Forms MVC MVC AD HOC system.web OWIN IIS @despos | facebook.com/naa4e
.NET Framework ASP.NET MVC MVC OWIN INTEGRATION WEB SERVER @despos | facebook.com/naa4e
Changes Tight coupling between ASP.NET and IIS Presented as a big win only a few years ago Platform dependence Windows only System.web is legacy code Devised back in 1997 @despos | facebook.com/naa4e
When they took SYSTEM.WEB apart @despos | facebook.com/naa4e
From EMPTY to FUNCTIONAL in Visual Studio 2015 @despos | facebook.com/naa4e
ASP.NET CORE has a nice programming interface and an interesting set of new programming features. @despos | facebook.com/naa4e
Would be the perfect vN+1 @despos | facebook.com/naa4e
Its a complete change of platform and to some extent also tools and habits @despos | facebook.com/naa4e
Migration Facts Find out who moved the cheese ASP.NET CORE has a high cost of setup Costs tend to zero over time Find out why they moved the cheese Some good reasons Some "other" reasons @despos | facebook.com/naa4e
Good Reasons New runtime environment Unification of ASP.NET and WebAPI pipelines Old system.web dropped Memory footprint All web app services decoupled to interfaces Authentication Static files management Exception handling and logging @despos | facebook.com/naa4e
Microsofts Motivation Taking more people to the cloud Loyal customers moved already to Azure or are likely to do it What about other perspective customers? Oh yes, they re using Mac computers and Linux @despos | facebook.com/naa4e
DECISION POINT You and IIS Having problems with IIS? Looking for Apache Server? Some node.js nostalgia? Wishing to call yourself a "geek" again? cmd.exe C:\> _ @despos | facebook.com/naa4e
DECISION POINT You and ASP.NET Having problems with Web Forms? Looked into ASP.NET MVC and/or plain SPAs? Having problems with ASP.NET MVC? Looked into Web Forms and/or plain SPAs? Sure it s not your code that sucks? @despos | facebook.com/naa4e
Theres not much left that can be added to ASP.NET Battle-tested, well-known and stable Room for small improvements Razor DI Azure integration Pipeline customization @despos | facebook.com/naa4e
What if youre planning a complete rewrite? @despos | facebook.com/naa4e
Whats different? Configuration, startup, pipeline Free IoC though Full rewrite of HTTP modules (including tools) New ways of doing old things Core authentication (except Identity) Embedded resources Project management Development experience Test, build, deploy, manage dependencies @despos | facebook.com/naa4e
ASP.NET MVC No support for Web Forms Migrating code is overall doable Switching to ASP.NET Core mindset is easy Aside a few new APIs to learn, it s all the same Plus minor features in Razor @despos | facebook.com/naa4e
The underlying .NET .NET Framework As above .NET Core (x-platform) EF Core No SignalR No 3rdparty frameworks (if not ported) Subset of the .NET Framework (and no VB) @despos | facebook.com/naa4e
Plan moving to ASP.NET Core especially if you re experiencing any of the following: Issues with IIS and system.web Issues with the app on the cloud Performance issues in the core runtime or see a business opportunity in x-plat hosting @despos | facebook.com/naa4e
Inevitably the future. But nobody knows when the future will be. @despos | facebook.com/naa4e
