![]() The most important step was to correctly locate the necessary files, in my case: Starting from the example in the folder fw \ makes I managed to build my first executable in MSVC 2019 written in. Posting my progress on migrating to MSVC, I first decided to learn about generating the project build. The FWH libraries are automatically part of your download, and the Harbour build for MSVC is also available on the FTDN download page. If you are using BCC proprietary controls, those will need to be changed. Once you have it setup you can try a build and see what happens with your existing code. I believe the setup info is still available in the FWH files, but if not, feel free to email me and I'll send over specific guidance. I use it because it is the most tightly intertwined with Windows 10 which is what all my clients have on their systems. I would suggest you start by downloading Visual Studio 2019 Community. YAs Antonio said, there is a constantly evolving editor on this forum that is designed for FW and many people use it. You could distribute what you build in MSVS, and you can even incorporate your editor into the Visual Studio interface. It's fast, and another button will move the build to the distribution folder. When I'm ready to do a release of the application ( usually an update ), I have a button in UES that executes a batch file, setting the environment, and then it executes the. When I make edits to the UES code, and save it, then I do a quick build with Visual Studio ( one button click ) to test my work. My project is also loaded into Visual Studio. It's certainly not the only option, but it works well for me. Could you help me find more information on how to compile? Thank you in advance. My idea is to switch to MSVC and Harbour32. My current project (over 30 years old) has 654 PRG, use BCC74 and xHarbour123. I've been thinking about migrating to MSVC for a long time, and this text of yours inspired me a lot, I would like to know more details about your environment, do you use the MSVC IDE? I started MSVC 2017 about a year ago for small mobile applications, and I would like to migrate my project in xHarbour to this environment. I also have an older version of the commercial xHarbour. TimStone wrote:For many years, I have used Microsoft Visual Studio + Harbour + FWH. Updates are steady, and apply automatically in VS, so you never lose time reconfiguring. You can work 100% in Visual Studio, and even have it use your preferred editor. It works, it's easy to use, there is no cost for the Visual Studio, There are also options. Thankfully we have options, but I prefer this one. So, the process is simple: Edit in UES, then click on the build option in VS which compiles changed files, links, and starts the program. However, for testing, I have the program setup in Visual Studio. I do my editing in Ultra Edit Studio, and my builds for distribution are created with a make file called from UES. No other tools supported it, but my clients have had the benefit of using it now for several years. Antonio quickly made it happen with the ability to use capabilities supplied in Visual Studio. For example, a few years ago, we wanted a photo taking option in our product. Some options are simply not available with other compilers. Visual Studio is constantly updated and provides for every feature in WIndows development. My clients all use Windows, and no other product is designed to be 100% compatible with the current OS. I also have an older version of the commercial xHarbour.Īll of my work is done with the Microsoft build for a simple reason. ![]() For many years, I have used Microsoft Visual Studio + Harbour + FWH.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |