Mike Rousos

@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.

#DotNetConf Is it possible to upgrade an application to .NET 6 when it has NuGet package dependencies from the previous framework?

@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 github.com/dotnet/upgrade….

Does the upgrade assistance help with upgrading .Net Core 2.1 to Net 6.0? #dotnetconf

@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.

@cvillalobosm Not yet, but it's on the backlog. github.com/dotnet/upgrade…. 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.

@swehunter2000 Unfortunately not. Feel free to file an issue at github.com/dotnet/upgrade…. That would be a great feature.

#dotnetconf does the upgrade assistant support ef to ef core bu converting an EDMX to migrations-style code?

@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: docs.microsoft.com/en-us/dotnet/c…

Can Windows Service be build with .NET 6? #dotnetconf

@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.

#DotNetConf I understand it so that WCF is not a part of .net 6?, so the upgrade app will not be able to upgrade apps using wcf?

@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.

.NET Upgrade Assistant: Scott Hunter says "released", but it still version 0.3 :-( @dotnet @dotnetcnf #dotnetconf 2021

@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 nuget.org/packages/upgra… to see the latest versions.

#dotNETConf I am trying to install the Upgrade-Assistent, but it says I need a version parameter. What should this version be? You are attempting to install a preview release and did not use the --version option to specify the version.

@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.

#dotnetconf what's the oldest .Net framework the Upgrade Assistant will support?

@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.

@Alex79680422 Unfortunately, yes :)

@MJRousos ok, thanks, so it'll still be a lot of work :)

#dotnetconf will the Upgrade assistant also be able to covert projects that use Entity Fremdwort 5 or 6?

@Zeljko98701610 Not, currently. There are docs on C++/CLI upgrading at docs.microsoft.com/dotnet/core/po…, but the process looks a bit different from csproj's.

#dotnetconf Is there a plan to improve upgrade procedure of C++ CLI projects to .net 5.0? Especially multi-TFM procedure and nuget support?

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

@MJRousos but will the code generated from edml/edmx files work after convert?

@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.

#dotNETConf Does NET5 support the "Add Service Reference" from Net framework? Can the upgrade tool transfer the soap service without error?

@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!

@cathysull Will there eventually be a UI or @VisualStudio integration for the .NET Upgrade Assistant? #dotnetconf

@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.

#dotnetconf Should we be moving .net core solutions to .net 5 as well?

@sterenas We're planning to support VB.NET apps, but that isn't possible yet with the early previews available now.

#dotnetconf #dotNETConf Does upgrade-assistant support upgrading Winforms VB.NET applications to .net 5?

@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.

#dotnetconf wait wait wait, that looks amazing. What are the pre-requisites to use the upgrade assistant, i mean, if someone has a poor architecture or spaguetti code it also works?