Application Recovery and Restart C# Quick Reference

April 20, 2010

Background Application Recovery and Restart (ARR) is a feature that allows you to prepare for the impossible (?) case where your application crash or waits forever (“Not Responding”) The feature lets you “register” for these cases in order to give you the opportunity to save the application data or do some clean up operations, before it ends its life. This feature exists from Windows Vista, but it seems that not enough people knows it, so let’s see how can anyone use the Windows API Code Pack to easily integrate ARR in their applications. More information on the feature can be found at Application...

Windows Ribbon Framework – Visual Basic .NET Samples

April 15, 2010

Since so many people asked, I’ve created a Visual Basic .NET version of the Windows Ribbon for WinForms samples using Instant VB by Tangible Software Solutions. Their demo version is limited to converting projects up to 1000 lines, but this was enough for me to convert the samples project. The new VB.NET samples have been uploaded to the project site. That’s it for now, Arik Poznanski.
one comment

Crash while closing application that uses Windows Ribbon Framework

April 14, 2010

Since that’s the third time I’ve been asked about it, and in fact came across the problem myself, I thought I should blog my reply to help future users. Problem Description You use the Windows Ribbon Framework, either directly (in C++) or in managed code using my Windows Ribbon for WinForms library. You add a close button to the ribbon which closes the application. The application crash on close. Don’t cut the branch you sit on The problem is that you try to call ribbon.DestroyFramework, which ultimately calls IUIFramework.Destroy from a ribbon command handler. So while handling the ribbon event you try to...
tags: , , ,
no comments

WPF: Animate Visibility Property – Update

April 13, 2010

Back in this post I showed you how you can easily add a fade-in / fade-out effect to a UIElement that changes its Visibility property, using a simple attached property. Some people encountered a problem using this property when they bind the UIElement to a model which initially hides the control. Since the default value of the Visibility property is Visible, using the attached property created an unwanted fade-out animation when the application started. To fix this issue I added another attached property that allows the user to skip the first animation. Also, I’ve fixed a minor issue with the double animation...
no comments