Application Lifecycle – Reasonable expectation of the new operating system?

My company has a desktop application originally developed for Windows XP. The original programmer was fired (I might add extreme biases). I have fixed different applications Program, but in general trying to avoid it, it is a mess, the only real solution is to completely rewrite it, which may take a year.

We have been trying to “forget” this application , But to guide the client to use our web version, this version is updated, easier to maintain, easier to expand, and easier to support. Most customers agree that the web version is better.

However, we There is a customer who insists on using the desktop application. The application needs some tape to run on Vista, but now it is completely broken on Windows 7. I am not even sure if all the fixes will make it work on Win7 (current time estimate The value is “miracle”) But after installing the RELEASE build and running the DEBUG build from Visual Studio, the application has errors in almost every user operation, and from the high-level test run I can see that they are not related.

Since Windows 7 did not exist when this application was developed, does my company really want to be able to make all the necessary changes to make it run “smoothly” as it does on XP?

Edit: Management wants to know “What is the industry standard to support the new operating system?” Because I have no real answer to that.

Windows 7 XP mode will be your best choice.

http://www.microsoft.com/windows/virtual -pc/download.aspx

It took a long time for lol to release this, but to support it to run in XP mode, otherwise it is not worth it to support the development of a new application. If he wants to continue running It puts it in XP mode.

The same goes for video

http://www.microsoft.com/windows/virtual-pc/support/default.aspx

My company has a desktop application originally developed for Windows XP. The original programmer was fired (I might add extreme biases). I have fixed different applications Program, but in general trying to avoid it, it is a mess, the only real solution is to completely rewrite it, which may take a year.

We have been trying to “forget” this application , But to guide the client to use our web version, this version is updated, easier to maintain, easier to expand, and easier to support. Most customers agree that the web version is better.

However, we There is a customer who insists on using the desktop application. The application needs some tape to run on Vista, but now it is completely broken on Windows 7. I am not even sure if all the fixes will make it work on Win7 (current time estimate The value is “miracle”) But after installing the RELEASE build and running the DEBUG build from Visual Studio, the application has errors in almost every user operation, and from the high-level test run I can see that they are not related.

Since Windows 7 did not exist when this application was developed, does my company really want to be able to make all the necessary changes to make it run “smoothly” as it does on XP?

Edit: The management wants to know “What is the industry standard to support the new operating system?” Because I have no real answer to that.

Windows 7 XP mode will be your best choice.

http://www.microsoft.com/windows/virtual-pc/download.aspx

lol took a long time to release this, but it is supported to run in XP mode, otherwise it is not worth supporting the development of a new application. If he wants to continue running it will put it in XP mode.

The same goes for videos

http://www.microsoft.com/windows/virtual-pc/support/default.aspx

Leave a Comment

Your email address will not be published.