FiveTech Software tech support forums

Tim,

RichEdit is working fine here.

I send you my full working VS2012 project.

Antonio, i like test in VS2013 too, im using FWH14.04, can you send me the lib updated? thanks

Norberto,

Already sent to your email.

I have already installed VS2013 Ultimate and I am already using it for testing and exploring its posibilities

Antonio,

The lastest build you sent me of your project still is using an older format and VS 2013 Pro wants to update it ( which I do ). I'm also getting an error trying to do a build.

I saw you put in a ton of additional .lib files. Are they all necessary ?

I'm wondering if my harbour version is too old ? It's the last one you had me download, but it is from April 2013.

Tim

Tim,

Today I installed Visual Studio 2013 Ultimate, Update 2. Is the same update that you are using ?

Don't worry for the list of libraries in the project, only the ones that are used will get linked into the EXE.

Please run Harbour.exe and let me know the version and build number that you get, thanks

My ultimate project is very large and so I don't want to add in every library. Because I have a successful build in UE Studio using VS 2012, I linked in those libraries that I figured I would need to specify in the IDE build ( Harbour and Microsoft SDK libs). I still have the following unresolved externals, all called rom the FiveHC32.lib. Actually, it looks for these functions even though I do not use them in my program. Thus, VS 2013 IDE may be linking everything even if it is not used. Perhaps we need to find a setting for it.

Here are the unresolved externals:

Code: Select all  Expand view

1>Fivehc32.lib(RICHEDIT.obj) : error LNK2019: unresolved external symbol _GetFileVersionInfoSizeA@8 referenced in function _HB_FUN_REDLLVERSION
1>Fivehc32.lib(RICHEDIT.obj) : error LNK2019: unresolved external symbol _GetFileVersionInfoA@16 referenced in function _HB_FUN_REDLLVERSION
1>Fivehc32.lib(RICHEDIT.obj) : error LNK2019: unresolved external symbol _VerQueryValueA@16 referenced in function _HB_FUN_REDLLVERSION
1>Fivehc32.lib(RICHEDIT.obj) : error LNK2019: unresolved external symbol _OleUIPasteSpecialA@4 referenced in function _HB_FUN_REPASTESPECIAL
1>Fivehc32.lib(IMAGELIS.obj) : error LNK2019: unresolved external symbol __imp__ImageList_AddMasked@12 referenced in function _HB_FUN_ILADDMASKED
1>Fivehc32.lib(TOOLBARS.obj) : error LNK2019: unresolved external symbol __imp__InitCommonControls@0 referenced in function _HB_FUN_INITCOMMONCONTROLS
1>Fivehc32.lib(TOOLBARS.obj) : error LNK2019: unresolved external symbol __imp__InitCommonControlsEx@4 referenced in function _HB_FUN_INITCOMMONCONTROLSEX
1>Fivehc32.lib(DATEPICK.obj) : error LNK2001: unresolved external symbol __imp__InitCommonControlsEx@4
1>C:\Users\TimsAIO\documents\visual studio 2013\Projects\MLS Service Writer 10\Debug\MLS Service Writer 10.exe : fatal error LNK1120: 7 unresolved externals

 

And now there are 4:

1>libcmt.lib(crt0init.obj) : warning LNK4098: defaultlib 'msvcrt.lib' conflicts with use of other libs; use /NODEFAULTLIB:library
1>Fivehc32.lib(RICHEDIT.obj) : error LNK2019: unresolved external symbol _GetFileVersionInfoSizeA@8 referenced in function _HB_FUN_REDLLVERSION
1>Fivehc32.lib(RICHEDIT.obj) : error LNK2019: unresolved external symbol _GetFileVersionInfoA@16 referenced in function _HB_FUN_REDLLVERSION
1>Fivehc32.lib(RICHEDIT.obj) : error LNK2019: unresolved external symbol _VerQueryValueA@16 referenced in function _HB_FUN_REDLLVERSION
1>Fivehc32.lib(RICHEDIT.obj) : error LNK2019: unresolved external symbol _OleUIPasteSpecialA@4 referenced in function _HB_FUN_REPASTESPECIAL
1>C:\Users\TimsAIO\documents\visual studio 2013\Projects\MLS Service Writer 10\Debug\MLS Service Writer 10.exe : fatal error LNK1120: 4 unresolved externals

I took 100% of the files that I linked in previously ( all Microsoft SDK files and VC libs ) in my earlier builds.
All four unresolved externals relate to RICHEDIT.obj in the latest Fivehc32.lib. I do not use RICHEDIT so why they even appear I do not know. Apparently there is one more lib that holds these. Can anyone identify it ?

Tim,

Please link version.lib and OleDlg.lib from Microsoft.

Don't worry for RichEdit, its FWH the one which uses it so it gets linked in.

Both of those are linked in already ... have been since the beginning.

Tim,

I just did a "wild" search for one of those symbols in the Visual Studio C/C++ libs folder and it is there.

Please check that you are linking that library and not other, thanks:

Thanks. I was drawing from the Microsoft SDK files ( which interestingly still work when building from the UE Studio make file ). However, they only have 7.1
Moving to Windows Kits directory, and using those files, resolves all but one:

1>Fivehc32.lib(BRUSHES.obj) : error LNK2019: unresolved external symbol __imp__AlphaBlend@44 referenced in function _HB_FUN_ABPAINT

Can you do a search to see what Lib file that is in ?

Also, did you find a setting to turn of intellisense ? It is really offended with some of the code symbols. It also is unhappy with #INCLUDE and #DEFINE in a .prg file.

Some things are strange.

Tim

RESOLVED

I got a build ...
For anyone tracking this, I have an application that uses nearly 100 .prg files. I've been successful using UE Studio to build it with Harbour and Microsoft Visual Studio 2012 VC++.

This project is to build it using the IDE in Microsoft Visual Studio 2013. The first step was to take the MAIN( ) file and get it to build with all the menu items / functions commented out.
That is now successful.

By Friday I expect to be able to build the entire application in the Visual Studio 2013 IDE !

Tim

Tim,

very good

Microsoft allows to implement support for new languages in VS, but the problem is that it is really complex and could take many days to build it

Anyhow I don't discard that we may do it

It is never easy.

I got a build, but when trying to run it ( debug ), I get the error that the application can't find the .pdb file. Of course it is right there in the debug folder where the .exe resides.

Strange behavior ... I will have to figure that one out tomorrow.

Tim

Tim,

In both project modes (debug and release) you have to adjust the settings: don't use precompiled headers. And for a complete rebuild of the project.

Here it is working fine, anyhow the more I use Visual Studio IDE the more I see its advantages (yesterday it was great to debug low level C code, something that I can't do using Borland) but, in example, you are not allowed to manually modify a RC file. If you do it, Visual Studio will not load it.

The source code editor, in my opinion, it is not as eficient as UEStudio one. Anyhow, until we don't get the right puggin for the Harbour language support, we are not seeing it in its full potential.