I developed a standalone client app in VS2003 that runs fine with the .NET 1.1 Framework installed, as expected. It fails, however, when only .NET 2.0 is installed on the machine, giving a dialog box entitled " MyAppname.exe .NET Framework Initialization Error". I have read through the Microsoft article entitled "Microsoft .NET Framework 1.1 and 2.0 Compatibility," which says that Microsoft's goal was backward compatibility but that there are roughly 10 known breaking issues with backward compatibility.

My question is: How can I get some diagnostic information at runtime about what problems .NET 2.0 is encountering so that I can attempt to fix the problem(s)

Yes I understand the peaceful coexistence of 1.1 and 2.0, but that is not what Microsoft recommends as the first alternative. If the incompatibility is this definitive, then I don't understand why Microsoft has published articles such as this one:

http://msdn2.microsoft.com/en-us/library/ms994381.aspx

in which they state that "Microsoft's compatibility goal for .NET Framework 1.1 applications is that they should work smoothly on the .NET Framework 2.0 except for a set of documented changes as provided here." Are you saying that Microsoft completely failed in their effort to provide some measure of backward compatibility for 2.0 toward apps that were developed with 1.1