|
-
May 22nd, 2010, 04:58 AM
#1
Thread Starter
Fanatic Member
Maintenance Contract for legacy VB6 application
Years ago I created an application using VB6. Over the years I've updated and maintained it so that it works just fine with w9x, w2000, XP, Vista and Win7.
My customer now has a new IT/IS manager who would like to formulate some kind of maintenance contract so that he knows I will continue to keep the application working on future versions of windows.
He obviously accepts that it's an old application and that I'm not going to completely re-write it - for example I'm not going to make a .net or native 64 bit version as part of a maintenance agreement (that level of development would need to be negotiated separately)
So, the 'wording' of the contract would exclude that - in other words I'll maintain a 32bit application which works on 32bit windows and would depend on WOW64 if it was installed on a 64bit OS.
So, I'm happy to guarantee to keep it working on 32 bit windows but I can't guarantee that it'll work on WOW64 (or can I/should I ?)
How soon do you expect MS to stop actively selling 32bit Windows ?
Has anyone ever done any kind of maintenance agreement ? What did you include/exclude - any specific wording ? Suggestions ?
I've worked with this customer for almost 20 years so we're not going to screw each other I just want to make sure there's no misunderstandings.
Thanks
Ian
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|