Net Express - We are running wrappacks from 6 - 12. - why the huge gap? When developers upgraded to Wndows 10 and something fails....the first response from Micro Focus is "You need to be on the latest wrappack" (Which agree with).....so those end up running on the latest wrappack.
I run windows 10 and I'm on wrappack 6. I upgraded from Windows 7 to Windows 10 and was not a new install.
Our compile server however is sitting at wrappack 6 to match the customers environment.
Probably 90% of our developers run Windows 10 (it might even be 100%), others are probably on Windows 8.
In our production code that shipped to the customer we actually set this "MFOLECL_NO_THREAD_INIT" in code.
In terms of the Micro Focus Server that our customers run on is based on wrappack 6. - To roll out any changes to the runtime is a massive task and not undertaken lightly. There are a lot of laws, processes, testing etc that would have to be undertaken by our customers to take any "fix" or changes.
Again there are other considerations that can effect deployment especially now UAC (User Access Control) is regarded as 'ON' on everybody machine. (We only support Windows 7 SP1 and higher, Server 2008 and higher as well as Azure)
I don't deploy under "Program Files" (Unless they are Windows services - as they run elevated)
All my executables are manifested "asInvoker"
All my executables are compiled "Shared dynamic" therefore the runtime location is derived from the registry.
The runtime is deployed under "Program Files\CompanyName"
To roll out the Visual COBOL runtime will involve a years testing and will only happen on a product release.
To sum it up.....we have more problems or issues with Net Express, we don't have any issues with Micro Focus Server or our application running under it.
Neil