Nothing works

[ladeak]

I have been applying the same steps manually for a long time on all sorts of ASP.NET Webapi projects (to be converted to ASP.NET Core) as this tool provides. I have tried to use this tool multiple times throughout its existence.

It never worked for me. I get all sorts of errors, I had to run it multiple times to execute some steps.

Things bother me like:

• it does not remove Microsoft.AspNet.WebApi packages (had to manually remove it)
• it does not update remove usings (2nd run removed those)
• it does not add Asp.Net Core usings.
• it updates the TargetFramework once to netstandard2.0, once to net6.0
• it does not update controller-action return types
• etc.

The only thing it did I can do in 10 seconds, but as it stands today, this is unusable for me. However, I would love to use it a lot.
I am happy to engage through some official channels though, as I cannot share details of my project in public.

[sunandabalu]

@ladeak thanks for reach out. Currently UA does not have extensive support for Webapi upgrade, including the ones you called out about removal of webapi packages or removal of usings. Although I'm surprised for the same project, UA changed the TFM to netstandard2.0 and on the next run to net6.0, when web dependencies are involved UA will always pick .NET 6.0 instead of netstandard2.0, could you share your csproj so we can take a look?
@mjrousos anything else that you want to add here, since you have more context on the webapi area?
/cc @cathysull

[ladeak]

Thanks for clarifying, that means I shall have no expectations because officially not supported. (that explains my findings).
It is an aspnet webapi project project, but only a dll containing some of the controllers. So it is not the host application. -> that might explain the reason. I can provide a minimal sample, but only tomorrow.
It also has Directory.Build.props and targets file, that can cause some of the other findings. (like it said it is removing Microsoft.AspNet.WebApi nuget package but it did not)

In the csproj it is added such as:

<ItemGroup>
   <PackageReference Include="Microsoft.AspNet.WebApi.Core" Version="$(someVersionDefinedInDirectoryBuildProps)" />
</ItemGroup>

[mjrousos]

We would like to improve the tool to better support WebAPI scenarios. @ladeak, if there are specific changes the tool could make that would be useful, can you please file individual issues for them so that we can track getting that functionality added?

[ladeak]

Sure