Hi,

I was playing with Clarius SFT June 2007 CTP released and found these issues so far:

1. TypeAlias is not supported by Recipe designer. It seems that Recipe designer fails when .recipe file contains

<xi:include href="TypeAlias.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />Actuallydoes not show Wizard pages but does not sayanything and does not crash as well.

2. Validation passes when TypeAlliases are used but include element does not exsist

3. Designer does not serialize Bound attribute when the value is false. It seems that DSL designer thinks that default value is "false" but for GAT default value is "true". So it leads to creating unbound reference when action is applying.

Hi Evgeny,

Thanks a lot for your feedback. Let me address it one by one:

1. The Recipe Designer doesn't currently support using XInclude (this should be noted in the RecipeDesigner.pdf available for download). This is a known limitation and we're currently debating if using XInclude would be still needed if you don't need to mess directly with the XML. We've some scenarios where it may still be useful. If you have some thoughts on this please feel free to share them through here or to my email vga AT clariusconsultingDOT net.

2. This one is by-design actually. If you specify a non-valid type in an <Alias> that is not being used that won't cause a runtime error (as the Alias is not being used). That is the reason we are not complaining about this when validating. This allows us to make a faster validation.

3. This may be a bug, I'll check into this one and get back to you.

Thanks again for your feedback, and keeping it coming!

-Victor.

Hi Evgeny,

Thanks a lot for your feedback. Let me address it one by one:

1. The Recipe Designer doesn't currently support using XInclude (this should be noted in the RecipeDesigner.pdf available for download). This is a known limitation and we're currently debating if using XInclude would be still needed if you don't need to mess directly with the XML. We've some scenarios where it may still be useful. If you have some thoughts on this please feel free to share them through here or to my email vga AT clariusconsultingDOT net.

2. This one is by-design actually. If you specify a non-valid type in an <Alias> that is not being used that won't cause a runtime error (as the Alias is not being used). That is the reason we are not complaining about this when validating. This allows us to make a faster validation.

3. This may be a bug, I'll check into this one and get back to you.

Thanks again for your feedback, and keeping it coming!

-Victor.

Victor,

Thank you for fast response. All your point make sense for me.

And I got new trouble. I tried to add recipe binding on my DSL designer surface and it did very strange steps.. It change the extension of my recipies from .recipe to .xml I tried to rename it again to .recipe and open it using Recipe Designer. Designer fails I guess due to:

<HostData>

<CommandBar Name="Project" />

<CommandBar Guid="26ea7933-844d-49e4-9145-094a45fedb5c" ID="65536" />

</HostData>

these lines.

It seems that designer does not serialize HostData correctly. At least when I'm using Guid="26ea7933-844d-49e4-9145-094a45fedb5c" instead of named bar.