If I can help it, this is the absolute last time that I'll involve myself in a project that creates a Windows application program for end user consumption as an ISV.

Basically I don't want to involve myself in a Windows application project which will be available to the general public via the internet. The scope of such a project is just too great for an ISV to handle, mainly in the areas of support and testing.

A Windows applicaiton requires much broader test enviroments unlike a web browser which typically just requires you surf your site with the different web browsers.

When something goes wrong and the application crashes, there's just so many things that could be the problem, maybe there's insufficient RAM? hard disk space? Antivirus program? Spyware? As an ISV it's really hard to offer support to the client's target users cause an ISV is typically not in the business of supporting large global deployments.

How's this different from making a program for a client's internal use? For one thing said client would already have it's own IT support infrastructure thus you don't have to worry about the things like helping the user run an antivirus scan, or wheter his RAM is faulty or not. It's much easier to get answers about the system configuration compared to having to get it from your typical home end user.

Yup... this is the last time..