I am glad to announce that the new CTP of the Blend 2 is out

Недавно столкнулся с такой вот проблемой: есть контролы в отдельной ассембле, есть сателитные ассембли с локализированными версиями ресурсов для контролов, и то и другое лежит в GAC.
Есть проэкт в котором используется контрол из вышеупомянутой ассембли, и потому есть референс на ассемблю с контролом (естественно на GAC, соответственно в референсе есть только название ассембли - никаких путей).
Нужно задеплоить программу через ClickOnce.

И вот сама проблема: при деплойменте сателитные ассембли студия не находит, и потому не деплоит. Если добавить локализированные ресурсы в референсы, то ассемблю деплоймент положит не в папку с нужным языком, а просто рядом с программой, что собственно проблему не решит.

... >>>

Нарыл вот в блогах интересный пост, мож кому нада будет..

Цытирую:

I've created a control based on the ASP.NET AJAX Control Toolkit that gives a web site the ability to easily add cross browser support for CardSpace and othe Identity Selectors.

The concept comes is loosely based on dominick baier's CardSpace Control for ASP.NET, however I think that you'll find that it should be more flexible in regards to the UI abilities.

I have offered the control to the ASP.NET AJAX Control Toolkit team and they are considering its inclusion in the project.

This prototype code is attached to this blog entry.

CsAjax.zip

First of all, what is this misterious thing, MarkupExtension? As it follows from it's name, this is some kind of the extension for the XAML markup syntax, and in our case that is an the extension that allows user to shorten or simplify some operations in XAML, or at least provide some non-string data in case TypeConverter can not be used. One of the most common examples of the MarkupExtension is a shortened declaration of a data binding, like {Binding Path}. {StaticResource key} is also widely used, and that is also a MarkupExtension. Both of them can be declared in element syntax, but that is not widely used because the amount of XAML needed in such case is a bit larger, so I will use attribute syntax in my samples.

I have just found out one cool feature in WPF: there is one cool markup extension called ThemeDictionaryExtension, that can provide ResourceDictionary, associated with a current theme.

Думаю, уже об этом многие читали, но я осмелю повториться: очередная версия Бленда увидила свет: Expression Blend 2 September Preview уже доступен к скачиванию.

... >>>

Есть в WPF пару забавных механизмов, которые не так уж и хорошо описаны в нете - это рендеринг, компоновка и измерение.
Про них и я буду писать некоторые свои познания. (думаю будет полезно почитать особенно тем, кого интересует вопрос производительности програмного обеспечения написанного на WPF)

... >>>

What is WPF

WPF (part of WinFX/.NET Framework 3.0) is a brand-new presentation framework, built on top of the .NET Framework 2.0, that was originally designed to be used on Windows Vista, but it was also adopted for Windows XP as well. It allows developers and designers to create applications with much higher level of usability and incredible visual appearance, spending less time to the development and allowing designers to show full power of their imagination.

Sometimes you need to add some elements to the children collection of some container, for example, panel.

So you just write down my_panel.Add( child );

Later you find out that you need to find this element using it's name. You have specified it even before adding element to the container, so you expect it to be found be calling FindName method of the container.

But when you call FindName and provide it the name of the added in runtime element, it returns just null. Note: in case with elements, added throung the XAML this method works fine.

So what is the difference? The name has been set and the element is in logical children collection - it just must work.

After a short investigation it turned out that FindName method does not take elements children collection content into account - it get a INameScope and uses it to resolve the element by it's name. So after you add element in runtime, you should do the following:

System.Windows.NameScope.GetNameScope( elements parent ).RegisterName(name, object to link name with );

Hope it will help someone :)