OData CLI 0.3.1 Release

What's Changed

• fix build fail by @ElizabethOkerio in #314
• Make ODataT4CodeGenerator public by @KenitoInc in #310
• Fix/vsix signing by @ElizabethOkerio in #315
• Upgrade Newtonsoft.Json dependency to fix vulnerability by @gathogojr in #316
• Improve metadata uri handling by @Nthemba in #311
• Bump NuGet.Protocol from 6.1.0 to 6.2.2 in /src/Microsoft.OData.Cli by @dependabot in #320
• Fix .NET Foundation Code of Conduct Link by @gathogojr in #326
• Update version to v1.0.1 by @habbes in #334
• add code-signing for OData CLI by @ElizabethOkerio in #344
• Fix default value initialization for nullable properties by @habbes in #345
• Implement "No tracking" option for odata-cli by @marcmognol in #330
• add vs2022plus.dll to .tt file. by @ElizabethOkerio in #347
• fix CLI nupkg sign failure by @ElizabethOkerio in #348
• fix sign issue by @ElizabethOkerio in #354
• add task to get nupkg file by @ElizabethOkerio in #356
• add .net7.0 support by @ElizabethOkerio in #357
• add task to extract file name by @ElizabethOkerio in #358
• update variable name by @ElizabethOkerio in #359
• Bump NuGet.Protocol from 6.3.1 to 6.3.3 in /src/Microsoft.OData.Cli by @dependabot in #365
• rerun build by @ElizabethOkerio in #367
• bump up version by @ElizabethOkerio in #371
• Add SECURITY.md containing instructions for reporting security bugs by @gathogojr in #370
• Fix odata-cli exclusions by @gregwinterstein in #364
• Make odata-cli honor internal option (issue #268) by @gregwinterstein in #361
• Add no timestamp option (issue #349) by @gregwinterstein in #362
• Support omitting runtime version and code generation timestamp from generated files by @gathogojr in #383
• Fix missing ContainerProperty attribute on dynamic properties (issue #380) by @stanb in #381
• Add command-line option for ConnectedService.json file by @gregwinterstein in #363
• support arm64 product architecture by @ElizabethOkerio in #376
• Create valid property identifiers when generating OData client by @gregwinterstein in #333
• Fix dependencies and code violations warnings by @gathogojr in #388
• Bump version to 1.1.0 (CLI 0.3.0) by @gathogojr in #387
• Fix broken command line options by @gathogojr in #392
• Bump version to 1.1.1 (CLI 0.3.1) by @gathogojr in #396

New Contributors

• @marcmognol made their first contribution in #330
• @gregwinterstein made their first contribution in #364
• @stanb made their first contribution in #381

Full Changelog: v1.0.0...odatacli-v0.3.1

OData Connected Service 1.0.0 release

• Adds VS 2022 support

Microsoft.OData.Cli

A release of the odata-cli tool. The odata-cli is a CLI tool for generating strongly typed C# and Visual Basic client code for a specified OData service. It generates a DataServiceContext class to interact with the service and CLR types for each entity type and complex type in the service model. It does exactly what the OData Connected Service does.

OData Connected Service 0.13.0 release

• Fix issue where the Connected Service added to a VB.NET project fails to emit the service metadata into the XML file as expected
• Add support for emitting property attributes (e.g. MaxLength, etc) when generating Connected Service proxy classes
• Allow users the option of persisting custom HTTP headers and proxy credentials to the Connected Service configuration file
• Add support for emitting obsolete attributes when generating Connected Service proxy classes

OData Connected Service 0.12.1 release

• Fix invalid escaping of double quotes when generating VB.NET client proxy
• Fix invalid namespace emitted when generating client proxy with custom namespace supplied
• Restore namespace in the metadata document as the default namespace applied in the client proxy
• Fix non-compilable code emitted when the option to generate multiple files is checked and the model contains 2 types with the same name but in different namespace

OData Connected Service 0.12.0 Release

1. Fix regression errors when generating code for V1-V3 services
2. Fix regression errors caused by UI updates not running in UI thread
3. Improve error message when CLR type not found
4. Add support for reference model with relative URI
5. Set more logical default settings
6. Fix warnings displayed due to empty metadata file created when generating T4 template

OData Connected Service 0.11.1 Release

Fixes the signing and strong name issue that caused the connected service v0.11.0 not to be loaded by Visual Studio.

OData Connected Service 0.11.0 Release

• Adds search box for filtering entities to add on the Schema Types selection page
• Generate doc comments in generated code from description annotations in the OData schema
• Rename generated parameters source and keys to avoid name collisions with similar names in the model
• Fix build error cause by incompatible System.Text.Json version with new versions of OData client
• Display the number of selected operation imports
• Include enum types from enum collection properties in generated code to avoid compilation errors
• Fix issue where false is generated as False (uppercase F) in C# code, causing errors
• Fix issue causing undefined Edmx reference to appear in generated code

OData Connected Service 0.3.1 Release (Legacy)

This is a release of the legacy OData Connected Service version that supports previous versions of OData client (versions 6.x). It has been updated to support both VS 2017 and VS 2019.

OData Connected Service 0.10.0 Release

• Adds support for open types
• Fix issue loading generated Csdl.xml file when you have multiple generated client proxies in a project
• Properly escapes metadata path in the local filesystem when generating T4 templates
• Fix issue where unselecting an operation import auto-selects schema types that the operation depends on