NewUlmGuy
Member
It has been nearly 10 years since I last had to work on CNC issues, so I am a bit out of date.
I am currently working for a client who has not built a full package in over 2 years. They now want to deploy some modifications which require new business functions (and therefore a new DLL). As I recall, deploying such changes necessitate a full build.
The applications manager is concerned that the full build will overwrite the processing option and data selection changes that have been made in Production over the course of those 2 years.
I know that there is a version compare report that compares versions between environments, but I need to compare deployed vs saved within the same environment.
Does anyone have any ideas on how to do this in an efficient manner?
Thanks very much.
Steve
I am currently working for a client who has not built a full package in over 2 years. They now want to deploy some modifications which require new business functions (and therefore a new DLL). As I recall, deploying such changes necessitate a full build.
The applications manager is concerned that the full build will overwrite the processing option and data selection changes that have been made in Production over the course of those 2 years.
I know that there is a version compare report that compares versions between environments, but I need to compare deployed vs saved within the same environment.
Does anyone have any ideas on how to do this in an efficient manner?
Thanks very much.
Steve
