4 Commits

Author	SHA1	Message	Date
Doug Bunting	5cd86977ed	Rename client code generation components ... - #8523 - main project / package --> `Microsoft.Extensions.ApiDescription.Design` - tasks assembly and namespace --> `Microsoft.Extensions.ApiDescription.Tasks` - tool namespace --> `Microsoft.Extensions.ApiDescription.Tool` - targets --> verbs e.g. `GenerateTypeScriptNSwag` and `GenerateDocumentDefault` - `@(ServiceProjectReference)` metadata -> align with common MSBuild project properties - exception: `$(MSBuildProjectExtensionsPath)`; it's readonly and `%(ProjectExtensionsPath)` is unambiguous - use `%(ProjectExtensionsPath)` - also add `%(Targets)` metadata and remove unused `%(ProjectRuntimeIdentifier)` - `@(<ServiceProjectReferenceMetadata)` metadata -> align with MSBuild project properties - exceptions: `$(MSBuildProjectDirectory)`, `$(MSBuildProjectExtensionsPath)` and `$(MSBuildProjectName)` - readonly properties and names already unambiguous	2018-10-10 14:52:57 -07:00
Doug Bunting	6ffcf3571e	Remove T4 custom tool ... - use same generator as most other projects in aspnet repos - were not using named arguments to resource methods anyhow - update resources to use regular (numbered) format parameters - adjust to new `Resources` namespace; no need for separate `using` - use `Format...(...)` methods as necessary	2018-10-10 14:52:54 -07:00
Doug Bunting	25d0916b49	Use one namespace for the three client code generation projects ... - also cleared out most uses of `GetDocument` and `GenerationTasks` in MSBuild and strings - temporarily fixed up T4 templates, adding Resources.tt (will remove custom generation soon)	2018-10-10 14:52:53 -07:00
Doug Bunting	95b4dc8ca0	Add first cut of Microsoft.Extensions.ApiDescription.Client package / project ... - WIP in a number of ways	2018-10-10 14:52:36 -07:00