Mike Rousos

Software engineer on Microsoft's .NET Customer Engagement Team.

[Mike Rousos @MJRousos]

@mattthouvenot Yes. In that scenario, Upgrade Assistant will attempt to upgrade those packages to newer versions that will work with .NET 6. If there aren't any newer versions that will work, it will still make other changes it can and give you a warning to look at that dependency manually.

[Mike Rousos @MJRousos]

@wqwalter The tool could be expanded to handle that scenario more fully, though. So, if there are changes you'd like to see taken care of going 2.1->6, drop a feature suggestion over at https://t.co/sH3WhYt3j0.

[Mike Rousos @MJRousos]

@wqwalter Yes and no. 😀 The focus of the tool is .NET Framework to .NET 6, so most rules relate to that scenario. That said, if you feed it a .NET Core 2.1 app, it should update the target to .NET 6 which may be all that's needed.

[Mike Rousos @MJRousos]

@cvillalobosm Not yet, but it's on the backlog. https://t.co/BUW05E3OXW. One challenge is that Upgrade Assistant builds the project as part of upgrading, so (currently, at least) it needs to run in an environment where the input project can be built. For NetFx inputs, that's Windows.

[Mike Rousos @MJRousos]

@swehunter2000 Unfortunately not. Feel free to file an issue at https://t.co/rJ0trEh0aH. That would be a great feature.

[Mike Rousos @MJRousos]

@JustProgrammer Sure can! The only difference compared to .NET Framework is that the install process is different (you'll use it sc.exe, like other Windows Services, instead of InstallUtil). These docs cover it well: https://t.co/pfUhaFYA0k

[Mike Rousos @MJRousos]

@neslekkim WCF client apps work on .NET 6 and Upgrade Assistant is helpful for those. For WCF *server* apps, though, you are correct. Upgrade Assistant will not help with that scenario. If I remember right, it notices that scenario and actually ends early with a helpful message.

[Mike Rousos @MJRousos]

@DOTNETDOKTOR @dotnet @dotnetcnf Yea, the versioning is a little confusing. It's released in that it's ready for (and is seeing) public use and the repo is open. The tool is changing rapidly, though, so it's not 1.0 yet to reflect that the surface area is still shifting and additional features are in progress.

[Mike Rousos @MJRousos]

@clausbarthmsnc1 That shouldn't be necessary for installing. Can you confirm the command you're using to install is `dotnet tool install -g upgrade-assistant`?

If you do need to find a specific version, check out https://t.co/mSvz4x3TvK to see the latest versions.

[Mike Rousos @MJRousos]

@cobalt_soft That's a good question! We've only tested it with apps as old as .NET Framework 3.5, but I can't think of any reason it wouldn't work with older ones. We'll need to try that out.

[Mike Rousos @MJRousos]

@ashirwad_1998 That's right at the top of our to-do list. Not available in the current early previews, but this feature should be coming soon.

[Mike Rousos @MJRousos]

@Alex79680422 Unfortunately, yes :)

[Mike Rousos @MJRousos]

@Zeljko98701610 Not, currently. There are docs on C++/CLI upgrading at https://t.co/ejAT7n8p5R, but the process looks a bit different from csproj's.

[Mike Rousos @MJRousos]

@Alex79680422 There will likely need to be updates to that code based on changes to EF.

[Mike Rousos @MJRousos]

@BallebyMark Currently, the upgrade assistant won't change code brought in as a service reference. In some cases, the code will continue to work with just a few changes, but at the moment upgrade assistant doesn't help there.

[Mike Rousos @MJRousos]

@poweredbyaltnet @cathysull @VisualStudio Adding a good UI experience is on the roadmap, though we're still figuring out exactly what form that will take. Input is appreciated!

[Mike Rousos @MJRousos]

@DavidTa56645896 As .NET Core 3.1 leaves support, those apps should be updated to .NET 5 or .NET 6. There are fewer differences between .NET Core and .NET 5 than between Framework and .NET 5, though, so those updates should be simpler.

[Mike Rousos @MJRousos]

@sterenas We're planning to support https://t.co/gEGAduNCx1 apps, but that isn't possible yet with the early previews available now.

[Mike Rousos @MJRousos]

@pipetabor It should still be helpful in those cases! The tool will still be able to make common updates like updating project file format, updating NuGet package versions, and fixing up simple source code changes.