OData Connected Service is a tool that generates code to faciliate consumption of OData services. This tool will generate a DataServiceContext and classes for each of the entity types and complex types found in the service description. This tool is functionally equivalent to the Add Service Reference for OData V3 service.
Support generating code for OData V3 service.
Support generating code for OData V4 service.
Support generating client CLR classes into project.
Support including the T4 files(used to generate client CLR classes) into project.
Support generating client code into a certain folder which named by user.
Support updating generated client code.
Supports Visual Studio 2017.
Adds support for Visual Studio 2019
Allows user to make generated types internal
Upgrade Microsoft.OData.Client to version 7.6.3
Added a feature to open the generated files in visual studio after code generation.
Enable generated functions to be mockable
Removed Microsoft WCF toolkit dependency
Support for setting custom request headers to be used when fetching the metadata document
Support for splitting the generated code into multiple files
Save the service model in a file by default instead of as a literal string in the generated code
Fixes a bug introduced in v0.6.0 in relation to a feature for supporting writing service metadata to a file.
The service model will be embedded in the generated code as a string by default as it was before v0.6.0.
Added support for VB projects
Allow users to select which function/imports to include or exclude from the generated code
Allow users to provide proxy config and credentials for fetching metadata behind a network proxy
Fixed bug causing code generation to fail if metadata is loaded from a local file
Fixed bug causing service name to be reset to default when updating a connected service
Add support for loading configuration settings from an existing configuration file
Add support for saving the configuration wizard state when navigating through the pages
Emitting service metadata to an XML file
Excluding schema types from being emitted onto the Connected Service proxy class
Refinements and minor bug fixes
Auto-selects the last metadata endpoint used in generating proxy classes.
Enables multiple files generation using design-time T4 templates
Issue with wizard state persistence when updating an OData Connected Service Project fixed.
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
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
Moved extension to .Net Foundation
Fixed the strong name and signing issues that caused the connected service not to be loaded by Visual Studio