Different CLR Exception behaviour on Windows 2000 and XP
I have been developing a .Net rich client application in C# for internal company use. My machine is running Windows 2000 and I am using Visual Studio 2003 for development I decided to use wizard control from
Tim Dawson . I have created a form and placed the wizard control on the form. From the application I open the form containing the wizard using ShowDialog() and then close the form using this.close(). This works perfectly well on Windows 2000, but when I install the application on Windows XP, a CLR unexpected exception error occurs when you I try to close the wizard control form and I have to close the application. I changed the code to use this.dispose() but I still get the problem, again it works perfectly on Windows 2000 and fails with the same unexpected exception error on Windows XP.
I know the joke with Java is that it is a "Write Once test everywhere" solution. After this experience I am beginning to wonder if this is also true of .Net. I would expect there to be difference in behaviour between Windows 9x and Windows 2000/XP but I am surprised about there being a big difference between 2000 and XP.
I am curious if anyone can help me and explain the differences between the CLR exception handling on 2000 and XP , if there are any and areas where I should check. I have tried to google for for information but without much joy.