Skip to content

Releases: jweber/WcfClientProxyGenerator

v2.0.9

14 Oct 05:54
Compare
Choose a tag to compare

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

14 Oct 00:49
Compare
Choose a tag to compare

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

08 Oct 07:46
Compare
Choose a tag to compare

Added a proxy configuration option for overriding the default use of the WcfRetryFailedException type when a request fails after more than one attempt.

This is a minor release for changes related to #10.

v2.0.6

08 Oct 00:55
Compare
Choose a tag to compare

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

18 Sep 07:54
Compare
Choose a tag to compare
v2.0.0-beta Pre-release
Pre-release

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

16 Jan 08:33
Compare
Choose a tag to compare

Fix for Issue #6 - Fixed build output to include XML documentation
Fix for Issue #5 - Exposed the ChannelFactory in the proxy configuration.
Fix for Issue #7 - Added an OnException event handler to the proxy.

Thanks @varkkjuh for the contributions!

v1.2.4

12 Nov 05:54
Compare
Choose a tag to compare

Includes changes from pull requests #3 and #4.

  • Adds new OnBeforeInvoke and OnAfterInvoke 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

03 Nov 23:49
Compare
Choose a tag to compare

Fix for issue #1

  • Generated proxies now account for out parameters on OperationContract methods.

v1.2.2

27 Jul 06:30
Compare
Choose a tag to compare

Added overloads to the WcfClientProxy<T>.Create() method to accommodate common WCF endpoint configurations.

See the Usage section of the readme for more details.

v1.2.1

25 Jul 06:32
Compare
Choose a tag to compare

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.