This post originally comes from the blog of Igr Alexánder Fernández Saúco, one of the members of the Catel development team As you probably know by now, Catel.Fody will rewrite all properties on the ModelBase and ViewModelBase. So, if a property is written as this: public string FirstName { get; set; } it will be weaved into public string FirstName { get { return GetValue<string>(FirstNameProperty); } set { SetValue(FirstNameProperty, value); } } public static readonly PropertyData FirstNameProperty = RegisterProperty(“FirstName”, typeof(string)); But now we added a new feature to Catel.Fody. If a read-only computed property like this one exists: public string FullName { get { return string.Format(“{0} {1}”, FirstName, LastName).Trim(); }… read more →
All versions for Catel before 4.0 (the latest being 3.9.0) are released with the Ms-PL license. Start with Catel 4.0, the license will be changed from Ms-PL to MIT. The main reason for this is to simplify the license and to use a more commonly known license. Below is the new license: The MIT License (MIT) Copyright (c) 2008 – 2014 CatenaLogic Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the… read more →
It is now possible to step through the Catel code while debugging your software starting with version 4.0 (and the nightly builds for 4.0 already available via NuGet). The image below shows how an application steps into the Catel code: In very old versions of Catel, it was possible to step through the code while debugging your software. This was accomplished with the help of SymbolSource.org, a website that can host symbols and source code. To use this features, users would have to add SymbolSource as symbol server. Then Visual Studio would download the right symbols when required (but this could be slow). About 2 years ago, suddenly the SymbolSource feature… read more →
We are pleased to announce that we have been working very hard to support several new platforms in Catel: Xamarin.Android Xamarin.iOS Windows Phone 8.1 (Silverlight) Windows Phone 8.1 (Windows Runtime) As most libraries choose to support all platforms via PCL (Portable Class Libraries), Catel uses a different approach by implement a platform-specific assembly for each platform. Though this might sound crazy, this brings several advantages to Catel which are not available in other platforms. Introducing “true PCL” Portable Class Libraries (PCL) is a technique where developers can develop a single assembly that can be used by multiple platforms. The reason the team decided not to use PCL is that it… read more →
Today we released Catel 3.9.0. This post describes the most important changes. For a detailed list, see the full release notes. To get the latest bits of Catel, please update via NuGet or get the setup package at GitHub. Added multilingual support (also via bindings) Support for multilingual applications has been on our wish list for a long time. In this release we finally found time to actually implement this feature. To bind to resource files which are determined dynamically, simply use the following xaml: <TextBlock Text=”{LanguageBinding WarningTitle}” /> For more information, see the documentation. Improved handling of unloading of nested views In previous versions of Catel it was possible… read more →
Today we have released Catel.Fody 1.7.0. This is mostly a maintenance release and provides the following changes. Validate for automatic change notifications Catel.Fody already weaves regular properties with matching methods into Catel properties with change notifications: public int SomeProperty { get; set; } private void OnSomePropertyChanged() { // automatically called thanks to Catel.Fody } However, when a user accidentally added parameters to the method, it would cause invalid runtime issues: private void OnSomePropertyChanged(int parameter) { // now broken } The new version of Catel.Fody will show a warning and give the developer two options: 1) Rename the method to get rid of the warning and remove accidental usage of the… read more →
It has been a long time since we last released a version of Catel.Fody. In the past few months, we have been working very hard to add new features and combine smart functionality in Catel to allow users to get the best out of Catel. This blog post will describe the most important changes in Catel.Fody 1.6. The reason that the new release took so long is because Catel.Fody is fully refactored under the hood, which allows us to add new features in the future in a modular way. Weaving properties Before Catel.Fody 1.6, weaving of properties was pretty basic. It was only possible to automatically weave any auto-property to… read more →
Most commands are registered per view and available per view model. Some commands (such as commands on a Ribbon or Toolbar) are application-wide. Catel supports both types, and this blog post explains how to use the ICommandManager to work with application-wide commands such as Refresh with a key bound to F5. Note that this information is based on the latest nightly build, this functionality will be included in Catel 3.9.0 Introduction to CommandManager There is no generic way to specify application-wide commands in WPF and Silverlight. To overcome this issue, Catel introduces the CommandManager. This manager allows to create commands which are hosted by the CommandManager. The commands on the… read more →
Today we released Catel 3.8.1. This is a hotfix release and contains a single change: Prism Extension throws exception for non-existing NuGet catalogs
Today we released Catel 3.8.0. This post describes the most important changes. For a detailed list, see the full release notes. To get the latest bits of Catel, please update via NuGet or get the setup package at GitHub. IoC components improvements Several improvements were made to the IoC components in Catel. The IoC components are ServiceLocator, TypeFactory and DependencyResolver. The first feature is that Catel now allows registration and resolving of generic types. This means that one can now register an open generic type like IDictionary<,> and resolve it as IDictionary<string, int> The second change is that Catel internally uses the IDependencyResolver instead of ServiceLocator to resolve types from… read more →
