web browser control based on Microsoft Edge

[Otto]

Dear Antonio,
Thank you.
What do we have to change if we want to use MSVC.

Can I download a FIVEWIN version where all is set up for MSVC?
This way, I could make a fresh installation on a different PC.

Best regards,
Otto

[Antonio Linares]

dear Otto,

all you need is to install Visual Studio Community

then go to fwh\samples and do buildh32. bat tutor01

[TimStone]

Antonio,

Remember to use the Harbour version for MSVC.

Otto,

I have used MSVC for my distribution builds for many years. I never have a problem with it. The reason in my mind is simple. Microsoft makes Windows, and therefore, any coding built with Microsoft Tools will be a "best fit." Using another product, like Borland, may require that developer to make significant updates to work with the new release versions of Windows, and that may not happen quickly.


I have recently created a Virtual Machine and updated my Windows 10 Pro to Windows 11 Pro Beta. I also have the beta installed for Visual Studio 2022 Community Version. I took my existing source code for my primary application, allowed Visual Studio to update the version of controls ( a single keystroke does this automatically ), and then did a clean and build. The project compiled and linked without any modification, and works perfectly.

Microsoft is making changes, and soon will start updating everyone ( with modern computers ) to Windows 11, and all of their applications will be undated also. Since most of us develop for businesses, they will want the connectivity of the latest technology to compete with their "rivals". I feel I can do that only if I stay with the most current releases of the software Microsoft releases. My personal viewpoints about the company are irrelevant. It's what most business people will buy and use.

Tim

[cnavarro]

Tim, I agree completely

[vilian]

Tim,
What do you use as a Resource Editor ?
Do you make your app build in 32bits or 64 bits ?

[TimStone]

1). I do not use a resource editor. I hand code my dialogs in the .rc file because I can get them positioned very precisely. Originally I used Borland, then Pelles but years ago I started doing it all manually. This way I have perfect alignment, and my screens are often very complex.

2) Several years ago I worked with 64 bit builds, but since the Microsoft Office apps were still only 32 bit, and there were "cautions" about 64 bit apps, I didn't do it then. Also, there were some FWH capabilities not in 64 bit. Perhaps one of the biggest problems was that one 3rd party app, my spell checker, made no improvements, but offered a 64 bit build of their library at a ridiculous price, and I wasn't willing to pay it. I didn't find another spell checker, so I stuck with 32 bits. I may revisit this in the future.