All CLA requirements met.

@dougbu outside of the dependencies questions, I also had those two questions for you, thanks for the help!

Would it be possible to add target namespace, target folder, and api client class name parameters to the tool?
Why is the Option for CodeGenerator not using a generic type to pass the enum and leave the parsing to system.command line?

Would it be possible to add target namespace, target folder, and api client class name parameters to the tool?

That sounds like additional customization users could do based on the incredibly poor "documentation" in https://github.com/dotnet/aspnetcore/blob/main/src/Tools/Extensions.ApiDescription.Client/src/build/Microsoft.Extensions.ApiDescription.Client.props. I would recommend adjusting the defaults to your preferences in the Microsoft.OpenApi.Kiota.ApiDescription.Client package and adding a bit more information for users over complicating the tool w/ lots of new options. Editing the updated project file isn't that big a deal.

Why is the Option for CodeGenerator not using a generic type to pass the enum and leave the parsing to system.command line?

I don't remember the full history. @captainsafia made the most recent changes to the tool, @ryanbrandenburg wrote it, and @BillHiebert did the VS side of things and designed the service that provides some of the versioning. @bradygaster may also have context.

thanks for the additional information. I'm not able to understand how this file works and what pieces I need just from reading it. Schedule a meeting today with you to go over that together.

Update for everyone watching this PR, during our connect with Doug we've made some updates to the kiota packages that I still need to test and publish. microsoft/kiota#1604
Other than that, I need to connect with Brady to learn more about the TypeScript dependencies.

i'm here, watching. :) we touched base today but I'm slim on the NPM knowledge. Is this something with which @vijayrkn could help? Maybe @phil-allen-msft could guide us in the right direction? Thanks for pushing on this @baywet !

Update, I've made progress thanks to the help provided by Doug, and answer provided by Vijay

TypeScript

There are effectively two cases:

• asp.net mvc app (no SPA), the TypeScript source file gets generated to the obj folder. It's expected that people will copy it/serve it so they can use it on the front end. NSwag only relies on dependencies that are already in the Visual Studio TypeScript targets. So here we might be at a dead end where the build will complain about missing dependencies and we don't have a way to add them (either manually or programmatically)
• asp.net with SPA included. In this case a client SPA gets scaffolded with a package.json in ClientApp directory (or equivalent, denominated by SPARoot). In that case we try to run an npm install command, and if it fails, display a comprehensive message.

Dotnet

I got to a place where the packaging and the command seems to be structured properly, if I execute the command manually in the terminal, it works. However when I try to build the project (dotnet build) I get the following error message. I'm not sure where to go from there.

MSBUILD : error MSB1025: An internal failure occurred while running MSBuild.
Microsoft.Build.Framework.InternalErrorException: MSB0001: Internal MSBuild Error: Unexpected CopyLocal flag.
at Microsoft.Build.Tasks.CopyLocalStateUtility.IsCopyLocal(CopyLocalState state)
at Microsoft.Build.Tasks.ResolveAssemblyReference.LogResults(ReferenceTable dependencyTable, List`1 idealAssemblyRemappings, List`1 idealAssemblyRemappingsIdentities, List`1 generalResolutionExceptions)
at Microsoft.Build.Tasks.ResolveAssemblyReference.Execute(FileExists fileExists, DirectoryExists directoryExists, GetDirectories getDirectories, GetAssemblyName getAssemblyName, GetAssemblyMetadata getAssemblyMetadata, GetLastWriteTime getLastWriteTime, GetAssemblyRuntimeVersion getRuntimeVersion, GetAssemblyPathInGac getAssemblyPathInGac, IsWinMDFile isWinMDFile, ReadMachineTypeFromPEHeader readMachineTypeFromPEHeader)
at Microsoft.Build.Tasks.ResolveAssemblyReference.Execute()
at Microsoft.Build.BackEnd.TaskExecutionHost.Microsoft.Build.BackEnd.ITaskExecutionHost.Execute()
at Microsoft.Build.BackEnd.TaskBuilder.ExecuteInstantiatedTask(ITaskExecutionHost taskExecutionHost, TaskLoggingContext taskLoggingContext, TaskHost taskHost, ItemBucket bucket, TaskExecutionMode howToExecuteTask)
at Microsoft.Build.BackEnd.TaskBuilder.InitializeAndExecuteTask(TaskLoggingContext taskLoggingContext, ItemBucket bucket, IDictionary`2 taskIdentityParameters, TaskHost taskHost, TaskExecutionMode howToExecuteTask)
at Microsoft.Build.BackEnd.TaskBuilder.ExecuteBucket(TaskHost taskHost, ItemBucket bucket, TaskExecutionMode howToExecuteTask, Dictionary`2 lookupHash)
at Microsoft.Build.BackEnd.TaskBuilder.ExecuteTask(TaskExecutionMode mode, Lookup lookup)
at Microsoft.Build.BackEnd.TaskBuilder.ExecuteTask(TargetLoggingContext loggingContext, BuildRequestEntry requestEntry, ITargetBuilderCallback targetBuilderCallback, ProjectTargetInstanceChild taskInstance, TaskExecutionMode mode, Lookup inferLookup, Lookup executeLookup, CancellationToken cancellationToken)
at Microsoft.Build.BackEnd.TargetEntry.ProcessBucket(ITaskBuilder taskBuilder, TargetLoggingContext targetLoggingContext, TaskExecutionMode mode, Lookup lookupForInference, Lookup lookupForExecution)
at Microsoft.Build.BackEnd.TargetEntry.ExecuteTarget(ITaskBuilder taskBuilder, BuildRequestEntry requestEntry, ProjectLoggingContext projectLoggingContext, CancellationToken cancellationToken)
at Microsoft.Build.BackEnd.TargetBuilder.ProcessTargetStack(ITaskBuilder taskBuilder)
at Microsoft.Build.BackEnd.TargetBuilder.BuildTargets(ProjectLoggingContext loggingContext, BuildRequestEntry entry, IRequestBuilderCallback callback, String[] targetNames, Lookup baseLookup, CancellationToken cancellationToken)
at Microsoft.Build.BackEnd.RequestBuilder.BuildProject()
at Microsoft.Build.BackEnd.RequestBuilder.BuildAndReport()
at Microsoft.Build.BackEnd.RequestBuilder.RequestThreadProc(Boolean setThreadParameters)

After chatting further with Doug, he requested a binlog for that error, here is the file for everybody else.
msbuild.zip

I just noticed this PR. Looks like it's been silent for nearly a year... is this still being worked on or should it be closed at this point?

I think it should be fine to close this. We'll likely want to put in some design work into how the client gen code can support new providers. @baywet Thoughts?

Thanks for the nudge here. Deferring to @darrelmiller who wanted me to keep things open until discussions pan out a while ago.