I am glad you finally released the samples for the chromeless windows and draggable glass.  I plan to implement this in my program right away instead of using the 'manual way'.

 I was able to run this sample in Orcas but when I did it in VS 2005 SP1 I ran into a lot of issues. I successfully got the references loaded and declared as

<Window
 -----
xmlns:blendables="http://schemas.identitymine.com/blendables"
blendables:ChromelessWindow.EnableAeroGlassEffect="True"
blendables:ChromelessWindow.EnableWindowDrag="True" >

The bold text is coming up as a Warning: "The 'http://schemas.identitymine.com/blendables:ChromelessWindow.EnableGlassEffect' attribute is not declared."

Then when I go to debug, I get an unhandled argumentexception of Hwnd of zero is not valid.  Can anybody explain that???

eric_r...I found the descrepency in our documentation vs. the scenarios in the doc as well as the samples available.  In our doc we were referencing the attribute: EnableAeroGlassEffect in the "Implementation Notes".  It's actually just EnableGlassEffect (no Aero).

I have updated the documentation to correct this.  I also tried setting the EnableGlassEffect="True" and EnableWindowDrag="True".  Setting EnableWindowDrag="True" does not seem to cause the Hwnd error. 

So I believe setting EnableGlassEffect="True" without a binding in our samples causes the Hwnd error.  I've sent a note to one of the ENG leads to investigate further and they should have an answer soon for you.

Thanks for the feedback and we'll be sure to get back to you ASAP.

Kurt

Thanks Kurt.

 My issue still remains, I believe when I wrote out EnabledAeroGlassEffect (or something to that effect) it was just out of memory.  My code was correct and with EnableGlassEffect="True" I still come up with the Hwnd error.  Since I cannot see within your dll I can't explain it any further than that - but it seems as if you have a good grasp on what issue I'm experiencing.

 Would you say this will require an updated reference assembly?  Or is there some kind of workaround (you mentioned a binding) that I can use in the meantime?  Theoretically it would be much easier than using my glass helper class.. it's not nearly as useful!

We found that there was a bug setting the EnableGlassEffect="True" on startup.  This was fixed a couple weeks back and will be in the JuneCTP coming hopefully this week if all testing goes as planned.  It seems that setting this attribute at startup is the most logical place to use it so I feel bad that we let that one slip through.

-Kurt

This should now be fixed in the June CTP posted earlier today.

Click "download now" from blendables.com to get to the June CTP.

-Kurt