Need help! Please show me how to organize this.
Need help! Please show me how to organize this.
Years ago we decided to move our codebase from Delphi 7 to XE2. So we checked all our needed Components (Devart, Devexpress, Rave Reports, Gnostice) are aviable for XE2. When all was ok, we moved forward to XE2. We testet all our modules and it was not a big thing to get all work fine. But it takes time. Not a lot of, but enough.
Since then i made nearly the same procedure for Delphi XE6. Then i stopped introducing new versions. To much efort. We do not have any phone apps at moment (but planned in future). We have a huge inhouse ERP system, tons of webservices and software for our customers out there. For this part of software the most of the funky new stuff is useless, because it works as it is and there is no need to rewrite something to make it hip.
The main problem is: EMB can make as much marketing bling as they want. We can't upgrade to a new version until all of our component vendors are ready. If one of them stops to make the version race, we also stop to upgrade Delphi.
Also, as mentioned, we wants to start developing phone apps.
At moment, our goal is to keep all our codebase to one delphi version.
Is this the wrong approach?
Should we have for every software project we build using the expected Delphi version (include the external components)?
Some years ago i tryed to install serveral Delphi versions in a same VM but i failed to run it properly. So should i have one VM for each Delphi version?
How could that be handled if you are more than one developer (We are three at moment)?
You see, i'm a little confused at moment. I do not know how to organize that.
Years ago we decided to move our codebase from Delphi 7 to XE2. So we checked all our needed Components (Devart, Devexpress, Rave Reports, Gnostice) are aviable for XE2. When all was ok, we moved forward to XE2. We testet all our modules and it was not a big thing to get all work fine. But it takes time. Not a lot of, but enough.
Since then i made nearly the same procedure for Delphi XE6. Then i stopped introducing new versions. To much efort. We do not have any phone apps at moment (but planned in future). We have a huge inhouse ERP system, tons of webservices and software for our customers out there. For this part of software the most of the funky new stuff is useless, because it works as it is and there is no need to rewrite something to make it hip.
The main problem is: EMB can make as much marketing bling as they want. We can't upgrade to a new version until all of our component vendors are ready. If one of them stops to make the version race, we also stop to upgrade Delphi.
Also, as mentioned, we wants to start developing phone apps.
At moment, our goal is to keep all our codebase to one delphi version.
Is this the wrong approach?
Should we have for every software project we build using the expected Delphi version (include the external components)?
Some years ago i tryed to install serveral Delphi versions in a same VM but i failed to run it properly. So should i have one VM for each Delphi version?
How could that be handled if you are more than one developer (We are three at moment)?
You see, i'm a little confused at moment. I do not know how to organize that.
Comments
Post a Comment