WPF ShaderEffect Generator

Closed Issue: URI not correctly generated [6148]

sbussinger — Thu, 16 May 2013 05:05:35 GMT

The "pixelShader.UriSource" statement in the generated constructor isn't generating the correct URI for the pixel shader.

Given a project folder structure like:

Opto.Imaging\
Effects\
OptoImagingEffect.fx

The generated URI looks like:

pixelShader.UriSource = new Uri("/Opto.Imaging;component/Imaging/Effects/OptoImagingEffect.ps", UriKind.Relative);

The "Imaging" in the middle of that URI shouldn't be there.

If I add a Custom Tool Namespace of "Opto.Imaging", the generated code looks like:

pixelShader.UriSource = new Uri("/Opto.Imaging;component/Imaging/OptoImagingEffect.ps", UriKind.Relative);

The Imaging in the in middle of the URI should be "Effects".

Source code checked in, #69631

Project Collection Service Accounts — Mon, 01 Oct 2012 21:13:48 GMT

Upgrade: New Version of LabDefaultTemplate.xaml. To upgrade your build definitions, please visit the following link: http://go.microsoft.com/fwlink/?LinkId=254563

Source code checked in, #69630

Project Collection Service Accounts — Mon, 01 Oct 2012 21:07:03 GMT

Checked in by server upgrade

Reviewed: WPF ShaderEffect Generator 1.7.1 (Thg9 12, 2011)

tbqh511 — Tue, 13 Sep 2011 03:05:49 GMT

Rated 5 Stars (out of 5) - great tool

New Post: Adding Shader Effect File crashes VS2010

NickDarnell — Wed, 12 Jan 2011 23:35:10 GMT

Good to know, thanks. I'll try and figure out what I'm missing for the next version.

New Post: Adding Shader Effect File crashes VS2010

tlmii — Wed, 12 Jan 2011 22:30:16 GMT

Just an FYI on this - I was getting the same error as Joachim with the 1.7.1 install (VS2010, Win7, 64bit). I downloaded the DirectX runtime updater you pointed to here, ran it, then reopened my project and tried it and it worked fine. Since Joachim didn't respond to you, I thought you might be interested in knowing that your solution did work. Hopefully that leads you to being able to fix it in a future release so we can skip that step.

New Post: Adding Shader Effect File crashes VS2010

NickDarnell — Thu, 30 Dec 2010 22:25:07 GMT

Hmm...the 1.7.1 version is suppose to be able to function without the latest DirectX runtime installed. But perhaps I missed something. Download the DirectX runtime updater from Microsoft here, http://www.microsoft.com/downloads/en/details.aspx?FamilyID=2da43d38-db71-4c1b-bc6a-9b6652cd92a3&displaylang=en . That's the only thing I could imagine would cause it to crash, because as soon as you add the templated item, it's going to attempt to compile it. So if for whatever reason the dlls I packaged with the 1.7.1 version are not enough that would cause it to crash for sure.

New Post: Adding Shader Effect File crashes VS2010

joachimb — Thu, 30 Dec 2010 21:03:24 GMT

Hello,

I am very keen to use your VS2010 plugin to create my own Shader Effects, but I have no luck with Version 1.7.1. Every time I create a new project and add the Shader Effect File Template, VS 2010 crashes. I tried it on a 64bit machine and now also on 32bit and it is always the same! Any idea what I could try to get it running?

regards

Joachim

New Post: Pixel Shader .ps file in WPF Shader Effect Generator

NickDarnell — Thu, 23 Dec 2010 16:41:44 GMT

Not that I know of, WPF expects the pixel shader URI to point to an already compiled pixel shader. The WPF ShaderEffect Generator will compile the effect file when you compile your C# code, so that you don't have to run external utilities to recompile it.

New Comment on "Documentation"

incandescent — Thu, 23 Dec 2010 10:11:44 GMT

Great for designing effects.

New Post: Pixel Shader .ps file in WPF Shader Effect Generator

incandescent — Thu, 23 Dec 2010 10:10:38 GMT

I create a new effect in WPF Shader Effect Generator in Visual Studio 2010.

The File creates a main and a new .cs codebehind file and a compiled .ps file that is embedded in the .fx file.

So Effect1.fx contains the HLSL code for the effect inside a pixel shader called main.

Then the Effect1 ShaderEffect-derived class is contained in the code behind with the Effect1.ps in its PixelShader property. As the Uri to the PixelShader file.

Is it possible to assign the .fx file without compiling it to .ps as a binary pixel shader to the effect.

I have another effect called particle.fx, which I wrote earlier.

I either want to generate the .ps or .vs pixel shader file or vertex shader binary file. This I can generate from the fxc.exe command line tool.

Or does the WPF ShaderEffect Generator automatically generate the pixel code from the HLSL within the compiler.

I.e. Is the fxc compiler accessible from the Project Item Template inside Visual Studio 2010.

Without resorting to the command-line utility available on either the DirectX SDK or obtaining the compiled .ps or .fxo from NVidia's FX Composer 2.5?

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.

Reviewed: WPF ShaderEffect Generator 1.7.1 (sept. 07, 2010)

carldebilly — Tue, 07 Sep 2010 15:02:18 GMT

Rated 5 Stars (out of 5) - This version is resolving the Silverlight compilation problem. Very nice job!

Reviewed: WPF ShaderEffect Generator 1.7.1 (sept. 07, 2010)

carldebilly — Tue, 07 Sep 2010 15:01:12 GMT

Rated 5 Stars (out of 5) - That's resolving the Silverlight compilation problem. Very nice job!

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

Source code checked in, #50238

NickDarnell — Mon, 06 Sep 2010 22:32:03 GMT

* Fixing some silverlight bugs * Switching over the installer to just copy the DirectX DLLs i need. * Adding a template that works with silverlight * Updating the templates to not require any assembly references as they may conflict with what is possible with a silverlight application.

Reviewed: WPF ShaderEffect Generator 1.7 (Sep 04, 2010)

rerdavies — Sun, 05 Sep 2010 05:24:55 GMT

Rated 5 Stars (out of 5) - Generating the C# wrappers from markup in the fx code just makes so much sense. I was just about to fire up code for a new effect, and I remembered the sense of tedium and dread involved in hooking up registers in the classic shadereffect generator integration. No question, this is the right way to do it. Clean, tidy, and easy to work with. Thanks.