The Pain of Visual Studio Languages and DLL Files of Microsoft

in visual-cplusplus •  5 years ago 


So discouraging to have my programming application not work on other computers but only on the computer I programed. This is a famous problem with programs born from Microsoft Visual Studio. The need to install MS VS same versions on the other machines that will use the program in order for it to work is ridiculous. Otherwise, I will have missing DLL errors when the program runs. Installing the .Net Frameworks or Visual C++ Redistributables that would provide runtime environments don’t remedy many situations, but the whole Visual Studio IDE must be installed in the production machine to have that program compatible. I had this problem with Visual Basic .Net programs, C# programs, VC++, and almost anything complex produced via Visual Studio Integrated Developer Environment.

Those who are responsible in many corporations who choose VS IDE as their language choice are not aware of this problem only when all is completed and they have to spend about the same amount of time testing and fixing their software to make it run when it leaves its original machine. I personally saw many problems like these and also heard from other companies who spent about two years with several programmers and 100K--1M dollars in development and ran into hard times making their programs/software work at production environment.

Authors get paid when people like you upvote their post.
If you enjoyed what you read here, create your account today and start earning FREE STEEM!