'master' branch (unless the development of a particular feature was enough large to have a dedicated branch). The results is that sometimes, some compilations for some platforms were not always tested (as It was laborious to check all platforms), leading to some unstable build on latest git. Also lots of users were asking for latest builds (because of the difficulty to meet all build requirements - VS 2012 Pro, Win SDK 7.1, DirectX June SDK 2010, Windows Phone 8 SDK...etc).'master_integration' branch along the previous 'master' is used as a the main development branch where all commits are pushed (including merge from user commits)'master_integration' are automatically pushed to 'master' when all projects are compiling fine for all targets (Net20, Net40, DirectX11.1, WinRT, WP8-x86/ARM * signed versions), including samples. Ideally this should also include unit tests, but they are not yet included.'master_integration' to 'master' (this process is running on my own PC). TeamCity is also checking commits on master_integration and should build everything automatically'master' should be the latest 'stable' development version.Release Notes (2012-12-21)
A new version 2.4.2 of SharpDX is available today for download.
This version is a maintenance version, mainly fixing several issues and improving the SharpDX Toolkit.
This release is also introducing some breaking changes, so this is actually not what could be called a 'minor' release:
This release is integrating several patches made by the community on github. Thanks to all of them!
Please find below an auto-generated list of all changes and fixes from previous 2.4.1 version.
Release Notes (2012-11-20)
A new version 2.4.1 of SharpDX is available today for download.
This version is a maintenance version, mainly fixing several issues and improving the SharpDX Toolkit.
PrimitiveBatch from DirectXTk has been ported to the Toolkit. Also, there is a new convenient method to draw a full screen quad using GraphicsDevice.DrawQuad. See details about changes in the Toolkit below.
Note about using the Toolkit effect compiler (tkfxc.exe): You can use either the version from:
Bin\Net40Release if you have DirectX End-User Runtime June 2010 installed.Bin\Win8Desktop-net40 which is shipped with D3DCompiler_46.dllAs It was explained in a previous post, SharpDX is now accepting code contribution from the community. This release is integrating contributions from early contributors to SharpDX on github!
Concerning the support, I'm focusing my primary support for the core functions of the following API:
For other API, I strongly encourage the community to participate to fix bugs and/or add improvements, as they have a lower priority support now in SharpDX.
Concerning the forum, my personnal investement to respond to API usage has now a much lower priority, as explained in the "Changes in Support and Community" post.
Also, as indicated on the contact form, I will not respond to any private inquiry about SharpDX bug notice or API usage. Thank you for your understanding.
Please find below an auto-generated list of all changes and fixes from previous 2.4 version.