Catel

A few weeks back, we’ve updated the project and item templates and re-published them on the Visual Studio marketplace. This time it was time to update the code snippets and publish them via the marketplace instead of manual downloads as well. Today ... [More] we are happy to announce that we’ve moved the code snippets from the Catel repository to the Catel.Templates repository. The code snippets can now be installed and updated via the marketplace (directly from within Visual Studio): At the time of the release, the following code snippets are included: log model modelprop modelpropchanged vm vmcommand vmcommandwithcanexecute vmprop vmpropchanged vmpropmodel vmpropviewmodeltomodel vmtaskcommand vmtaskcommandwithcanexecute The post Code snippets now available on the Visual Studio marketplace appeared first on Catel. [Less]

A few weeks back, we’ve updated the project and item templates and re-published them on the Visual Studio marketplace. This time it was time to update the code snippets and publish them via the marketplace instead of manual downloads as well. Today ... [More] we are happy to announce that we’ve moved the code snippets from the Catel repository to the Catel.Templates repository. The code snippets can now be installed and updated via the marketplace (directly from within Visual Studio): At the time of the release, the following code snippets are included: log model modelprop modelpropchanged vm vmcommand vmcommandwithcanexecute vmprop vmpropchanged vmpropmodel vmpropviewmodeltomodel vmtaskcommand vmtaskcommandwithcanexecute [Less]

A few weeks back, we’ve updated the project and item templates and re-published them on the Visual Studio marketplace. This time it was time to update the code snippets and publish them via the marketplace instead of manual downloads as well. Today ... [More] we are happy to announce that we’ve moved the code snippets from the Catel repository to the Catel.Templates repository. The code snippets can now be installed and updated via the marketplace (directly from within Visual Studio): At the time of the release, the following code snippets are included: log model modelprop modelpropchanged vm vmcommand vmcommandwithcanexecute vmprop vmpropchanged vmpropmodel vmpropviewmodeltomodel vmtaskcommand vmtaskcommandwithcanexecute [Less]

Optimizing the performance and memory allocations is a continuous project that we try to keep in mind while doing minor releases. For the next upcoming release (5.12), we decided to focus on taking a look at the serialization engine in Catel. There ... [More] are a few pain points we’d like to address: Performance Memory allocations Re-using objects using graph ids Xml serialization We’ll focus on the XmlSerializer first, but any code written in the serializer base will benefit all serializers. The current version of Catel uses XDocument (and internally sometimes falls back to XmlWriter / XmlReader and turns that into XElement again). This is a bit heavy and it has always… read more → The post Improving the serialization engine appeared first on Catel. [Less]

Optimizing the performance and memory allocations is a continuous project that we try to keep in mind while doing minor releases. For the next upcoming release (5.12), we decided to focus on taking a look at the serialization engine in Catel. There ... [More] are a few pain points we’d like to address: Performance Memory allocations Re-using objects using graph ids Xml serialization We’ll focus on the XmlSerializer first, but any code written in the serializer base will benefit all serializers. The current version of Catel uses XDocument (and internally sometimes falls back to XmlWriter / XmlReader and turns that into XElement again). This is a bit heavy and it has always… read more → [Less]

Optimizing the performance and memory allocations is a continuous project that we try to keep in mind while doing minor releases. For the next upcoming release (5.12), we decided to focus on taking a look at the serialization engine in Catel. There ... [More] are a few pain points we’d like to address: Performance Memory allocations Re-using objects using graph ids Xml serialization We’ll focus on the XmlSerializer first, but any code written in the serializer base will benefit all serializers. The current version of Catel uses XDocument (and internally sometimes falls back to XmlWriter / XmlReader and turns that into XElement again). This is a bit heavy and it has always… read more → The post Improving the serialization engine appeared first on Catel. [Less]

Optimizing the performance and memory allocations is a continuous project that we try to keep in mind while doing minor releases. For the next upcoming release (5.12), we decided to focus on taking a look at the serialization engine in Catel. There ... [More] are a few pain points we’d like to address: Performance Memory allocations Re-using objects using graph ids Xml serialization We’ll focus on the XmlSerializer first, but any code written in the serializer base will benefit all serializers. The current version of Catel uses XDocument (and internally sometimes falls back to XmlWriter / XmlReader and turns that into XElement again). This is a bit heavy and it has always… read more → [Less]

A while back, we discovered an issue with the DispatcherService.InvokeAsync implementation when an async method / expression was passed in as parameter. We fixed this by adding an alternative method called  DispatcherService.InvokeTaskAsync. ... [More] Unfortunately, we could not simply remove / change the behavior of the InvokeAsync because it would be a breaking change (and we are not ready for a breaking change release yet). So we had a few considerations: 1. Mark the member obsolete => not possible because there is still valid use for this member, it should just not be abused. 2. Add warnings / code checking to Catel.Fody => great plan Then after a while… 3. Create Catel.Analyzers… read more → The post New component released: Catel.Analyzers appeared first on Catel. [Less]

A while back, we discovered an issue with the DispatcherService.InvokeAsync implementation when an async method / expression was passed in as parameter. We fixed this by adding an alternative method called  DispatcherService.InvokeTaskAsync. ... [More] Unfortunately, we could not simply remove / change the behavior of the InvokeAsync because it would be a breaking change (and we are not ready for a breaking change release yet). So we had a few considerations: 1. Mark the member obsolete => not possible because there is still valid use for this member, it should just not be abused. 2. Add warnings / code checking to Catel.Fody => great plan Then after a while… 3. Create Catel.Analyzers… read more → [Less]

A while back, we discovered an issue with the DispatcherService.InvokeAsync implementation when an async method / expression was passed in as parameter. We fixed this by adding an alternative method called  DispatcherService.InvokeTaskAsync. ... [More] Unfortunately, we could not simply remove / change the behavior of the InvokeAsync because it would be a breaking change (and we are not ready for a breaking change release yet). So we had a few considerations: 1. Mark the member obsolete => not possible because there is still valid use for this member, it should just not be abused. 2. Add warnings / code checking to Catel.Fody => great plan Then after a while… 3. Create Catel.Analyzers… read more → [Less]