Is it possible to declare a type alias name in XAML?

I'm not sure if you can do the aliasing directly in XAML, but it's easiest to use the aliased name in XAML by simply subclassing the collection in code (or heck, renaming the collection class itself if it won't adversely affect the rest of your code): public class Blobs : BlobCollection {} It does seem unnecessary to have to do this, but it's all I can think of right now.

I fear that this is the only solution; but I'm hoping someone knows a XAML-only way to achieve the same thing. I've updated my question. – stakx Sep 4 at 20:21 2 +1; @stakx: If this is something you'll bolt on to generated or existing code (your comments on the OP seem to indicate this), then you still have an option of creating another assembly that just defines your aliases, and importing that.

If this is just getting around generics support, then it seems like such support might already exist in more recent XAML standards?. If you can't use more recent XAML standards, there's also other questions on work-arounds for generic support – Merlyn Morgan-Graham Sep 4 at 21:52 1 @Merlyn: Thanks for the hint about generics support in XAML 2009. Updated my question to reflect that it's not just about generics.

– stakx Sep 4 at 22:01.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.