After having worked a while with Silverlight you realize that you often keep a lot of things in resources in your Xaml. Not only do you add Storyboards for your animations, but you often also add styles and templates, and some converters and so on. The resources all of the sudden start taking up most if the rows in your Xaml. It becomes hard to read. Especially since Silverlight is all about styling and templating controls, which results in large amounts of Xaml.
It is also hard to share resources. Say that you have these converters that you use in several of your controls. How do you solve that? Having them declared in multiple places is no good.
In Silverlight 2 there wasn’t much you could do. You would just have to have all of those resources in your Xaml, and if you wanted to share them, they had to be in the App.xaml file.
20. December 2008
A couple of the guys at my company have started working on an internal Silverlight application. One of the guys is a former WPF developer, which gives him some serious advantages when starting with Silverlight. It actually gives him some serious advantages compared to my own sorry ass as well. However, it has some downsides as well. Downsides that sometimes end up with him sending me annoyed MSN messages.
He expects a bunch of WPF specific features to be available in Silverlight. I understand the "confusing". SIlverlight development is very close to WPF, except for the fact that Silverlight is in some aspects is tiny compared to WPF.
17. December 2008
I have spent a lot of time checking out Silverlight and its features. I have also spent a lot of time talking about it to a lot of people. And a reasonably large amount of the people I have talked to, have asked me about templating and styling and about how it works and the differences. I myself also had a little uphill battle to sort out the terms and get going... So I thought I would write an post about it... Sort of explaining it from my view.
13. October 2008
One of the more usefull extension points in EPiServer is the ability to create custom properties. That and GUI Plug-Ins. Those 2 extensions are probably the easiest and most used way to extend the functionality in EPiServer CMS. So how do you create a custom property? Well there are several ways to learn it. You can either go to one of our courses at EPiServer, and maybe even meet me, or you could read an article about it on http://world.episerver.com. It is actually a good article written by one of our developers in Ukraine, Denis Yakovlev. But you could also read this blog entry.