![]() You create a setup, which packages your EXE, ActiveX controls you used, VFP runtime DLL and Data files (DBFs etc) and provide that to customers. You have VFP as a developer, you finally build an EXE ![]() So again what you were already told and ignored: NET Framework in the installationĭistribution and Setup is part of the develoepr knowledge, don't skip that, it's like being a baker only knowing how to make dough, but not how to bake it. If you distribute an EXE made with the newest Visual Studio targetign the newest Framework you will also need to provide a setup installing a newer. NET Fraemweork is already a Windows component. a C# EXE only runs on otherĬomputers without a setup, as the. So don't get the wrong ide the EXE build process is buggy. It's a hurdle, once you have an EXE it simply runs on your PC but not on others, because it's not all in one file, it never is, also not in other programming languages. ![]() Others pick the free inno setup system and you find a lot of info about using Inno to distriubute VFP comes with Installshield Express and even with merge modules you need in such a Windows standard installer to provide the runtimes (bot C++ and VFP). What you can't distribute is VFP itself and so tools like tableĭesigner, but who needs that? Your audience ae end users, not developers. There is no need for customers, neither private nor government to have VFP itself just to run a VFP application, it just needs to be correctly built and distributed with an installer and runtimes. Is and that the easiest way is to have a main PRG file and also learn about READ EVENTS and what is and isn't available in EXE vs IDE, eg the IDE toolbars is not, yet _SCREEN remains available and it's easy to create a menu that has many/almost all the menu Also learn about what the main file of a project ![]() To start with just click the BUILD button on the project manager. Just get the building process straight and don't distribute source code files or even a VFP project, ie learn how to really build an application. ![]() On single desktops and with MS administrative tools like SCCM, that's not even your business.īut there is NO need to have licenses for running a VFP application, once it is build to an EXE, there are no license fees or CALs for data access too. Ther DevOps/Admins can install an MSI package you can create with install shield Again said: Your customers don't need VFP to run your application once you compile it into an EXE (or EXE+DLLs) and provide the roaylte free runtime, maybe even a setup. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |