Our company has a product lifecycle management system that has a client which is dependent upon running Windows XP. Each user runs the client application which establishes a connection to an application server process. The application server process then communicates directly with a database. App dependencies are DotNet 1.1 & GDM Tools.
My first question is - would an app like this in general be a good candidate for packaging?
I have been trying to do a proof of concept to see if it would be possible to package such a client.
When I package the client and try to run the package, the program starts up but upon initializing, the following exception comes up and the program crashes before initialization completes:
Pop Up message titles "Exception in PiSA cubes Client"
Exception code: 001 (DTVEXC_SYSTEM_ERROR)
Exception text: Exception raised by operating system.
Exception info: System error C0000005 at address 00ABCFD4:
"Access Violation"
This client does write to the registry every time the user logs in. This means the application would try to write to the packaged virtual OS registry. At this point, this seems to be the most likely cuprit for my issues.
Does anyone have any suggestions? Are there some tips and tricks to try or would this app not be a good candidate for packaging?