New FWH 15.05

[Antonio Linares]

viewtopic.php?f=16&t=30835#p177533

[Antonio Linares]

New build 2 of FWH 15.05 is already available to download

[Antonio Linares]

New build 3 of FWH 15.05 is already available to download

viewtopic.php?p=177924#p177924

[driessen]

Thanks, Antonio.

[TimStone]

Antonio,

On build 3, are the Microsoft libraries for VS 2013 or VS 2015. I recently suggested having an alternate name for the 2015 Community builds because many of us are experimenting with it, but using 2013 for actual productive work.

Tim

[Antonio Linares]

Tim,

The included libraries are for VS 2013.

Moisés needs them for VS 2010 and you want to try VS 2015.

And I need to figure how to organize it

[TimStone]

Antonio,

In the last version you provided all three builds. In my suggestion, keep the current names for the libraries for VS 2013. They should also work for 2010 since the C++ code was the same. However, new code was used in 2015, so simply add an x to the names of those libraries ( eXperimental ), and distribute them with the others. We can link those versions to our VS 2015 project.

Eventually 2015 Community will have a lot of popularity, so this resolves the issue.

Tim

[Antonio Linares]

Tim,

The problem is that a different Harbour is required for each of them, so that means using three different Harbours.

Besides that, it forces me to have VS2010, VS2013 and VS2015 on my computer.

Its a mess...

[TimStone]

Antonio,

I have two Harbour builds that you provide and they should be fine for awhile. You created the one Harbour that works fine with VS 2013, and that is what most people have for productivity work. That is what you are including in the FWH distribution now, and I believe that is how it should be.

We also are looking at the future, and VS 2015 Community will likely be chosen by many. Eventually, that is what everyone may use, but it is still early. It is not even in final release yet, just a Release Candidate version. You have provided us FWH libraries for it under the same name as the VS 2013, but we know they are not compatible. Adding x to the .lib file names ( two files ) is a way to make it easier for you since you are creating the builds anyway. Then everyone can have a copy and you don't have to email them.

Sorry, but 2010 is "old". Anyone using it can upgrade to the released version of Visual Studio 2013 Community for free without changing their code. Then we are back to two versions: 2013 for ongoing production work, and 2015 to bridge into the future.

Tim

[Antonio Linares]

Tim,

According to Moisés comments, VS2010 is the only one capable to build apps that properly work on Windows XP.

I can't confirm this. I would like to get others VS users comments:

Moisés comments:

Con XP, del que todavía hay muchos usuarios usándolo, el compilador que funciona correctamente es MSVC 2010, digan lo que digan algunos compañeros (de hecho, he probado por curiosidad sus programas en XP y no funcionan)

He says that EXEs that have been built with VS higher than 10 don't run on XP.

[TimStone]

Antonio,

I do not think that is correct. Of course I do not know why anyone is running XP. My clients who were slow to make the switch had disasters and lost much data with the malware attacks pointed at XP.

Tim

[MOISES]

Tim,

There are many users in Spain and Latin America that they are still using XP with an updated Antivirus. We can´t force them to upgrade it, as many are waiting for Windows 10 when it become estable and properly debuged.

Also, try your software compiled with MSVC2011 or higher and you will see what´s happening.

My two cents

[luisduque]

Maestro Antonio,

Tengo un ERP instalado en Ordenadores Con Windows XP,Vista,7,Windows Server 2012, Windows 8, Windows 8.1 y funciona perfecto en todos los windows
y en el caso de 64bit totalmente transparente.
Y actualmente trabajo FW 15.05 y Visual Studio 2013 Y por supuesto se debe mirar a futuro Visual Studio 2015

Ing. Luis Duque

[TimStone]

Antonio,

I can't test it with XP because I do not have it anywhere, nor do my reliable clients.

I can tell you that people here have tried the "best" anti-virus software available, on XP, and still had major intrusions. The reliable companies don't even provide an XP version of their software any longer.

Windows 10 will cost people, so the smart decision, in my view, would be to upgrade to 7 or 8.1 and then get the free upgrade to Win 10 for free when they are ready.

Tim

[Antonio Linares]

Tim,

According to Luis, VS2013 is properly running on XP.

To me VS2013 is the way to go for users that want to use Visual Studio.