Hello Group,

I am about to start a KickStarter campaign to gather funds for 3 options, all to save existing vb6 projects.

They are:

1. Funding vbRichClient to become a full IDE and compiler replacement for vb6

or

2. Funds to pay developers to write a binding to QT or Lazarus or Delphi or Xercoder or even .net native.

or LAST RESORT!

3. Lawsuit against MS for dropping vb6 Support

...

So that is the overview. My thought is that the vb6 replacement has to compile at least 95% of current projects code, with 5% code changes necessary.

That means it needs to do 95% of what vb6 does now.

My question to you is, if you could import and compile your code with up to 95% compatibly, would you switch? I think that is the base goal, we must FIRST get vb6 compatibility and then move to improve things from there. What are your thoughts?

Thanks
WP