While developing a Windows Store app I run into a Blend issue that caused me some headache.
I tend to define common converters in external assemblies in order to reuse them in other projects, so i added a reference to a Windows Store library project containing the converters I needed then swiched to Blend to use them from Create DataBinding dialog, and here’s what i got:
Problem: My library was not listed.
Really weird since here’s what I got doing the same from Visual Studio 2012
My MvvmHelper library is listed.
Using Visual Studio to add the assembly resulted in following Blend error:
Ok, i presume you probably want to know the reason (and how to fix it): The problem was caused by projects having different build configurations: that main project has a X86 configuration (required by Bing Maps component) while all referenced libraries where AnyCPU and looks like that Blend 2012 doesn’t like it.
Moving the entire solution to X86 solved the issue.
Blend team is working on having it fixed before Blend 2013 release.
Note: Many thanks to @unni for helping me on this.
Reason of this, comes from the fact that is a ‘scripting’ language, thus incomplete when compared with other languages like C# (no complete support for OOP concepts, partial type system) and from a characteritic tha represents one of its strength: being a dynamic language thus not allowing development tools like Visual Studio to provide compile time checking and full intellisense support (while getting better with each release)
Chapter 3 is dedicate to language core concept like Types, Modules, Interfaces, Classes and so on while next introduces more advanced concepts like Module organization, scope, inheritance etc.
Recent Generics addition is not covered, probably because book went out before TypeScript team released them.
I really enjoyed this ebook, reading goes fast and smooth and it uses a pratical approach, something not always true in language related books, i got what expected: a broader view of what TypeScript is and how to begin using it.