Skip to content
Hallway
0:00 / 0:00

#dotnetcore#dotnetframework#migration

Tips and Tricks on Moving to .NET Core

Microsoft Visual Studio

345K subscribers • 8 videos on Hallway

YouTube
  • Recommended by 1 person: 1 in engineering communities.
  • Made by the vendor. The company whose product it covers made or sponsored it.
  • May be out of date. The tools, versions or practices it shows have likely moved on.

Intermediate. Assumes working knowledge.

10K views7 years ago1 recommendation

Systems programmingTools and practiceBuild systems and packagingC# and .NET

Microsoft engineers explain the key differences between .NET Framework and .NET Core and offer tips for migrating existing projects.

Announcing .NET Core 3.0: aka.ms/dotnetcore3 #dotNETConf .NET Core is the future of .NET! Find out how to leverage the ways it differs from the .NET Framework like the new project system and deployment models. Understanding the big picture of .NET Core will help you build great applications.

Why it's here

1 person recommends this

What people say. Recommended for developers looking to migrate WPF and other legacy .NET Framework projects to .NET Core.

Moments people linked to

u/jasonsteeljin r/dotnet • Recommends

On “How do I migrate a WPF project from framework 4.6.2 to Core 3?”

Edit: Here is the video from the release live stream: link to this video During the live stream event, MS people specifically said update first to target at least 4.7.2. Step 1. Upgrade the project to target at least 4.7.2. Step 2. Fix any issues and verify that the app functions as expected in 4.7.2. E.g. run unit tests/integration tests/etc or go through each thing and click/edit/save/delete Don’t do any major refactoring. If something breaks you don’t want to be in a situation where you’re not sure if the bug is in the framework retargeting or your refactor. Step 3 upgrade to .NET Core 3. 0. Retest the app.
12View on Reddit