wpfshadergenerator Releases Rss Feed

Updated Release: WPF ShaderEffect Generator 1.7.1 (Sep 06, 2010)

NickDarnell — Sun, 24 Oct 2010 19:37:10 GMT

I've fixed some of the bugs reported with Silverlight; correct wrapper code should now be generated. I've added a template for it as well.

Released: WPF ShaderEffect Generator 1.7.1 (Sep 06, 2010)

Sun, 24 Oct 2010 19:37:10 GMT

I've fixed some of the bugs reported with Silverlight; correct wrapper code should now be generated. I've added a template for it as well.

Updated Release: WPF ShaderEffect Generator 1.7.1 (Sep 06, 2010)

NickDarnell — Mon, 06 Sep 2010 23:34:23 GMT

I've fixed some of the bugs reported with Silverlight; correct wrapper code should now be generated. I've added a template for it as well.

Released: WPF ShaderEffect Generator 1.7.1 (Sep 06, 2010)

Mon, 06 Sep 2010 23:34:23 GMT

I've fixed some of the bugs reported with Silverlight; correct wrapper code should now be generated. I've added a template for it as well.

Created Release: WPF ShaderEffect Generator 1.7.1 (Sep 06, 2010)

NickDarnell — Mon, 06 Sep 2010 23:11:16 GMT

WPF ShaderEffect Generator 1.7.1

Updated Release: WPF ShaderEffect Generator 1.7 (Aug 11, 2010)

NickDarnell — Thu, 12 Aug 2010 05:05:00 GMT

I've fixed a few bugs (defaultValue), and added a new feature (DdxUvDdyUvRegisterIndex). Enjoy.

Changes

DdxUvDdyUvRegisterIndex has been added as a comment tag on the file, just provide it the index of the register you want bound to that property in the generated C# code.
Compiled everything against the June DirectX SDK.
Updating the DirectX Runtime web setup in the installer.
Fixing some bugs relating to defaultValue being set correctly on some registers.
Updating the fx file template to use the starting color, 255,0,0,0 instead of 0,0,0,0.

Released: WPF ShaderEffect Generator 1.7 (Aug 11, 2010)

Thu, 12 Aug 2010 05:05:00 GMT

I've fixed a few bugs (defaultValue), and added a new feature (DdxUvDdyUvRegisterIndex). Enjoy.

Changes

DdxUvDdyUvRegisterIndex has been added as a comment tag on the file, just provide it the index of the register you want bound to that property in the generated C# code.
Compiled everything against the June DirectX SDK.
Updating the DirectX Runtime web setup in the installer.
Fixing some bugs relating to defaultValue being set correctly on some registers.
Updating the fx file template to use the starting color, 255,0,0,0 instead of 0,0,0,0.

Created Release: WPF ShaderEffect Generator 1.6.1 (Apr 15, 2010)

NickDarnell — Fri, 16 Apr 2010 05:14:44 GMT

Just a minor release to fix the problem with resource Uri generation in the C# Shadereffect files.

Changes

The Uri should be correctly generated now in the ShaderEffect files.

Released: WPF ShaderEffect Generator 1.6.1 (Apr 15, 2010)

Fri, 16 Apr 2010 05:14:44 GMT

Just a minor release to fix the problem with resource Uri generation in the C# Shadereffect files.

Changes

The Uri should be correctly generated now in the ShaderEffect files.

Updated Release: WPF ShaderEffect Generator 1.5 (Feb 19, 2010)

NickDarnell — Sat, 06 Mar 2010 01:53:23 GMT

Visual Studio 2008 and RC 2010 are now supported. Different profiles can now be used to compile the shader with.

Changes

Visual Studio RC 2010 is now supported much better than in 1.1. It appears as an extension in the extension manager and follows the newer conventions of VS2010.
Both the VS2008 and VS2010 plug-ins are now packages, so that future changes will be possible and will include additional features that are more involved than the custom tool.
In Alpha 1.1 it was hard coded compile using ps_3_0. This is no longer the case, the default is ps_2_0, however you can now use the <profile>ps_2_0</profile> tag in the comment section at the top of your effects file to control which profile is used to compile the shader.
The classes generated by the custom tool no longer have "Effect" appended to the end of the class name. You won't notice this change until the custom tool is re-run on the .fx file.
The WPF Effect Template has been updated, it now contains additional examples of tags that can be used in the comments, including an example of the profile tag.

Released: WPF ShaderEffect Generator 1.5 (Feb 19, 2010)

Sat, 06 Mar 2010 01:53:23 GMT

Visual Studio 2008 and RC 2010 are now supported. Different profiles can now be used to compile the shader with.

Changes

Visual Studio RC 2010 is now supported much better than in 1.1. It appears as an extension in the extension manager and follows the newer conventions of VS2010.
Both the VS2008 and VS2010 plug-ins are now packages, so that future changes will be possible and will include additional features that are more involved than the custom tool.
In Alpha 1.1 it was hard coded compile using ps_3_0. This is no longer the case, the default is ps_2_0, however you can now use the <profile>ps_2_0</profile> tag in the comment section at the top of your effects file to control which profile is used to compile the shader.
The classes generated by the custom tool no longer have "Effect" appended to the end of the class name. You won't notice this change until the custom tool is re-run on the .fx file.
The WPF Effect Template has been updated, it now contains additional examples of tags that can be used in the comments, including an example of the profile tag.

Updated Release: WPF ShaderEffect Generator 1.1 (Feb 10, 2010)

NickDarnell — Sat, 06 Mar 2010 01:48:18 GMT

I'm going to keep this release in alpha for now. But I've added VS2010 support and .Net 4 support to the addin.

Released: WPF ShaderEffect Generator 1.1 (Feb 10, 2010)

Sat, 06 Mar 2010 01:48:18 GMT

I'm going to keep this release in alpha for now. But I've added VS2010 support and .Net 4 support to the addin.

Updated Release: WPF ShaderEffect Generator 1.0 (Feb 05, 2010)

NickDarnell — Sat, 06 Mar 2010 01:46:30 GMT

This is the first release. Only VS2008 is supported right now. Just download and install.

Released: WPF ShaderEffect Generator 1.0 (Feb 05, 2010)

Sat, 06 Mar 2010 01:46:30 GMT

This is the first release. Only VS2008 is supported right now. Just download and install.

Updated Release: WPF ShaderEffect Generator 1.5 (Feb 19, 2010)

NickDarnell — Sat, 06 Mar 2010 01:45:33 GMT

Visual Studio 2008 and RC 2010 are now supported. Different profiles can now be used to compile the shader with.

Changes

Visual Studio RC 2010 is now supported much better than in 1.1. It appears as an extension in the extension manager and follows the newer conventions of VS2010.
Both the VS2008 and VS2010 plug-ins are now packages, so that future changes will be possible and will include additional features that are more involved than the custom tool.
In Alpha 1.1 it was hard coded compile using ps_3_0. This is no longer the case, the default is ps_2_0, however you can now use the <profile>ps_2_0</profile> tag in the comment section at the top of your effects file to control which profile is used to compile the shader.
The classes generated by the custom tool no longer have "Effect" appended to the end of the class name. You won't notice this change until the custom tool is re-run on the .fx file.
The WPF Effect Template has been updated, it now contains additional examples of tags that can be used in the comments, including an example of the profile tag.

Updated Release: WPF ShaderEffect Generator 1.6 (Mar 05, 2010)

NickDarnell — Sat, 06 Mar 2010 01:44:14 GMT

Several improvements and bug fixes have gone into the comment parsing code for the registers. The plug-in should now correctly pay attention to the tags placed into the comments. There is now a test project in the source tree that is being used to test out changes in future releases to prevent regressions.

Changes

The parser should pay attention to comments such as <type></type> and <summary></summary> now above the register.
Fixed an issue with some simple register types not being detected correctly (float, int...etc), the code was ignoring any register type without a number.
Added code to report warnings to the log for register types that the code doesn't know how to map to .Net (ex, float4x4, is not mapped in WPF's shader wrapper)
Beginning to add support for multiline comments inside of a block so that summary tags could stretch over multiple lines. It's not there yet, so I don't recommend using it, it won't correctly remove the extra /// comment slashes inside of comments.

Released: WPF ShaderEffect Generator 1.6 (Mar 05, 2010)

Sat, 06 Mar 2010 01:44:14 GMT

Changes

The parser should pay attention to comments such as <type></type> and <summary></summary> now above the register.
Fixed an issue with some simple register types not being detected correctly (float, int...etc), the code was ignoring any register type without a number.
Added code to report warnings to the log for register types that the code doesn't know how to map to .Net (ex, float4x4, is not mapped in WPF's shader wrapper)
Beginning to add support for multiline comments inside of a block so that summary tags could stretch over multiple lines. It's not there yet, so I don't recommend using it, it won't correctly remove the extra /// comment slashes inside of comments.

Created Release: WPF ShaderEffect Generator 1.6 (Mar 05, 2010)

NickDarnell — Sat, 06 Mar 2010 01:38:06 GMT

Changes

The parser should pay attention to comments such as <type></type> and <summary></summary> now above the register.
Beginning to add support for multiline comments inside of a block so that summary tags could stretch over multiple lines. It's not there yet, so I don't recommend using it, it won't correctly remove the extra /// comment slashes inside of comments.

Updated Release: WPF ShaderEffect Generator 1.5.1 (Mar 02, 2010)

NickDarnell — Wed, 03 Mar 2010 04:40:52 GMT

Minor bug fix to the installer to make sure the latest version of the DirectX runtime is installed.

Changes

Updating the installer to install the latest version of the DirectX runtime (Feb 2010).