Pros Cons of Outsourcing for add/edit of records to standalone exe files
Hallo,
I am thinking about to outsource add/edit of records to own exe files.
I mean in the case of add/edit I would call with shellexecute this standalone exe.
Thank you in advance for your suggestions.
Best regards,
Otto
Otto,
what is the reason for this decision?
EMG
Hello Enrico,
I think one can take out complexity from a program.
You can start in a legacy app a new programming concept.
And updates are not so risky because not the whole application is addressed.
I think you can also uniform the look of your program.
Better for sharing work in a company.
Easier to find Errors.
What do you think.
Best regards,
Otto
Otto,
I don't know. I wouldn't use separate EXEs. Better use separate functions or classes or PRGs or LIBs, and so on.
EMG
1) I think one can take out complexity from a program.
2) You can start in a legacy app a new programming concept.
3) And updates are not so risky because not the whole application is addressed.
4) I think you can also uniform the look of your program.
5) Better for sharing work in a company.
6) Easier to find Errors.
Dear James,
yes you are right.
But I have a feeling it could be better dividing the program.
Therefore I posted the question.
When I read your post one thing immediately came in my mind.
Time reduction during testing.
Addedit.exe 123
Calls the addedit program for the customer address number 123.
In an all in one program I get the start screen then I have to select customer management and then edit.
I do use business objects.
Your post does not say that the way is wrong you say if I understand all well you say it is not necessary to do.
But do you see any disadvantages in dividing.
Best regards,
Otto
Otto,
I advise against using calls to external executables. How to know if an operation was successful or not? Eventually complicate programming: users, access, antivirus, firewall blocking .exe, etc ..
In cases that it is not choice but advise pass all parameters in a file addedit.exe FiParam.txt or FiParam.xml
It is true that sometimes the use of calls to external .exes is imperative. I found another use: simulate multithreading. But I find that the reasons why you want to do does not need to call an external executable.
My two cents.
When I read your post one thing immediately came in my mind.
Time reduction during testing.
