Older projects sometimes have files placed in unconventional locations that can cause problems after upgrading. We replaced the verstamp.h include with ntverp.h and this error disappeared. The easiest way to find a symbol in the available include files is to use Find in Files ( Ctrl Shift F) and specify Visual C Include Directories. 1>C:\Program Files (x86)\Windows Kits\8.1\Include\shared\common.ver(212): error RC2104: undefined keyword or key name: VER_FILEFLAGSMASK It turns out there is just one symbol that is needed, VER_FILEFLAGSMASK. We wanted to find out what symbols were being used from that header file, to see if that file was really needed or if those symbols were defined elsewhere, so we commented out the header file declaration and recompiled. From an Internet search, we determined that this came from a DAO SDK, an obsolete data technology. One of the files that couldn't be found in Spy was verstamp.h. ![]() Upon building a newly converted project, one of the first things you'll often find is that header files that your project uses are not found. We have two projects, one with a large number of C files, and another a DLL that's written in C. More complex projects might not upgrade as easily, as discussed here.Īfter upgrading the two projects, our solution looked like this: The other is SpyHk, written in C, a supporting DLL. dsw files from Visual C 6.0, converted easily with no issues that require further attention. We considered this case to be typical for porting Windows desktop applications that use MFC and the Win32 API, especially for old projects that have not been updated with each release of Visual C since Visual C 6.0. The experience for Visual Studio 2017 or Visual Studio 2019 should be almost identical. We found an old version of it that was last compiled in Visual C 6.0 and ported it to Visual Studio 2015. This useful application has shipped with Visual Studio for many years. It shows the complete hierarchy of windows and provides access to metadata about each window and control. Spy is a widely used GUI diagnostic tool for the Windows desktop that provides all sorts of information about user interface elements on the Windows desktop. ![]() It's not meant to be a definitive guide to porting, since the experience of porting a project depends very much on the specifics of the code. This porting case study is designed to give you an idea of what a typical porting project is like, the types of problems you might encounter, and some general tips and tricks for addressing porting problems.
0 Comments
Leave a Reply. |