Releases: jweber/WcfClientProxyGenerator
v2.0.9
Added support for registering multiple predicate/delegate combinations for the same Exception
or TResponse
types for use in the RetryOnException
, RetryOnResponse
and HandleResponse
proxy configuration options.
v2.0.8
Added overloads for HandleResponse<T>
that do not require a value to be returned.
Note:
The version information starting at this release will be synchronized between the NuGet version number and assembly version number. In past releases, the assembly version was unintentionally mismatched from the NuGet version (e.g. release v2.0.7 was at assembly version 2.0.20.0).
v2.0.7
v2.0.6
Added full support for executing WCF calls asynchronously by using async/await. Async calls will work properly for OperationContract methods that return Task
or Task<T>
. For OperationContract methods that do not return a Task
, using WcfClientProxy.CreateAsyncProxy<T>()
will enable asynchronous calls to be made.
For more information, view the async section of the readme.
Added the ability to rewrite responses received from remote services by using the HandleResponse configuration option.
Remove the default failed request retry functionality. By default, failed calls will only be attempted one time. Overriding this behavior can still be accomplished by setting the MaximumRetries value
v2.0.0-beta
Added support for executing WCF calls asynchronously by using async/await. Async calls will work properly for OperationContract methods that return Task
or Task<T>
. For OperationContract methods that do not return a Task
, using WcfClientProxy.CreateAsyncProxy<T>()
will enable asynchronous calls to be made.
For more information, view the async section of the readme.
v1.2.5
v1.2.4
Includes changes from pull requests #3 and #4.
- Adds new
OnBeforeInvoke
andOnAfterInvoke
event handlers to the WcfClientProxy creation configuration - Adds better error checking for attributes and type visibility on the WCF contract interface.
Thanks @varkkjuh for the contributions!
v1.2.3
v1.2.2
v1.2.1
An issue was fixed with the IL that was generated for the proxy type. For projects in which 32bit assemblies were preferred (i.e. <Prefer32Bit>true</Prefer32Bit>
set in the project file), an InvalidProgramException
exception with the message "JIT Compiler encountered an internal limitation." would be thrown upon calling into the WCF service.