# Developer Notes

This file contains notes, hints and information of interest for those developers wishing to compile Password Safe for Windows. Linux developers should read the file README.LINUX.DEVELOPERS.txt.

### Contents

1. Introduction
2. Installing Microsoft Visual Studio 2017 Community Edition
3. Microsoft Visual Studio Numbering Systems
4. Software Requirements
5. Building the Windows Version of Password Safe
6. XML Processing
7. Gtest
8. Building Xerces XML Parser for Windows
9. Bulding the wxWidgets User Interface for Windows
10. Wix MSI Installer
11. Minidumps

### Introduction

With Visual Studio 2015, Microsoft released the free Community Edition and it supports their MFC (Microsoft's Foundation Classes), unlike the previous Express editions, enabling Password Safe to be built using it. They have also released the same edition with the new Visual Studio 2017 (see note below re: minimum installation requirements for Visual Studio 2017).

1. Development tools: Microsoft's Visual Studio 2015 (referred to as 'VS2015' below) is currently the main development environment, and pwsafe-14.sln is the main top level "solution" file (the 14 refers to the version of the C++ compiler).
2. The new Visual Studio 2017 solution and project files (referred to as 'VS2017' below) have also been provided but Password Safe is not currently being built using this for official releases. The associated files end with 15 (see note below re: Microsoft's insane numbering system).
3. pwsafe_wx-14.sln is used to build the wxWidgets version under Windows, although this build is not formally supported. Note: the wxWidgets library must be built with the same version of Visual Studio as being used to build Password Safe or you will receive numerous compatibility error messages during the link phase.
4. The current version of wxWidgets for Windows is 3.0.2
5. Previous versions of Visual Studio, i.e., Visual Studio 2005 (MSVS8), 2010 (MSVS10), 2012 (MSVC11) and 2013 (MSVS12) are no longer maintained, but their solution and project files have been retained in the "old-sln" directory. Note, however, that they are no longer able to build the current MFC or wxWidgets versions of Password Safe due to the use of newer C++11 and C++14 features within the code.
6. User interface library: The currently supported version of Password Safe for Windows is built upon MFC (Microsoft's Foundation Classes). The wxWidgets version, which provides cross platform support can also be built on Windows and corresponds to that used on other platforms i.e. Linux and MAC OS. Note that the wxWidgets version in all environments does not support all features supported by the Windows MFC version, for example, different alphabet virtual keyboards. If you depend on such features, you should stick to the standard MFC build.
7. XML support: As Password Safe provides XML import/export capabilities, it can be configured to use one of several XML parsers (or none). The currently supported version of Password Safe for the MFC Windows build is the Microsoft XML parser.

To summarise: The 'official' version of Password Safe on Windows platforms is based on MFC (Microsoft's Foundation Classes), and uses Microsoft's XML parser. This corresponds to the Release configuration in the build environment, i.e., the release build using Microsoft's XML parser. This will build the required DLLs using their Release configuration (pws_at.dll for AutoType support and pws_osk.dll for the Virtual Keyboard) and the base resource DLL (pwsafe_base.dll used to create non-English language support).

The Visual Studio 2015 and 2017 projects have been updated to be able to generate the 64-bit versions of both the MFC and wxWidgets Password Safe executable. This has only been tested on a 64-bit Windows environment with the VC14 64-bit compiler. It has not been tested on a 32-bit Windows environment with a cross-compiler. For wxWidgets, you will need the 64-bit static libraries and they should be placed in a new directory 'lib64\vc140_lib' corresponding to the current 'lib\vc140_lib' for the 32-bit versions.

For each Configuration there is an associated platform. Unfortunately, Visual Studio adds all defined platforms to all defined configurations even if a particular combination is not valid. The supported combinations are:

- If the Configuration name does not end with '64', only platform "Win32" is supported.
- If the Configuration name does end with '64', only platform "x64" is supported.

No other combinations are supported or have been tested.

The current MFC configurations are:

- 32-bit versions - platform Win32:

- Debug - builds the debug version using the Microsoft XML parser and the required DLLs (pws_at_D.dll and pws_osk_D.dll).
- Release - builds the release version using the Microsoft XML parser and the required DLLs (pws_at.dll and pws_osk.dll). This will also contain the base language DLL used to generate I18N support.

- 64-bit versions - platform x64:

- Debug64 - builds the debug version using the Microsoft XML parser and the required DLLs (pws_at_D.dll and pws_osk_D.dll).
- Release64 - builds the release version using the Microsoft XML parser and the required DLLs (pws_at.dll and pws_osk.dll). This will also contain the base language DLL used to generate I18N support.

The current wxWidgets configurations are:

- 32-bit versions - platform Win32:

- Debugwx - builds the debug version using the Xerces XML parser
- Releasewx - builds the release version using the Xerces XML parser

- 64-bit versions - platform x64:

- Debugwx64 - builds the debug version using the Xerces XML parser
- Releasewx64 - builds the release version using the Xerces XML parser

Note that the core and os project files contain all of the above projects, even if you are only selecting one of the MFC or the wxWidgets builds. You should not have to select them individually as selecting the main Password Safe configuration will select the correct configuration for these projects. You should also be careful not to select all configurations in the Visual Studio Batch Build process either to build, rebuild or clean all configurations. Only select MFC configurations if using the MFC Password Safe solution (pwsafe-14.sln) and the wxWidgets configurations if using the wxWidgets Password Safe solution (pwsafe_wx-14.sln).

### Installing Microsoft Visual Studio 2017 Community Edition

After downloading the installation a stub from Microsoft (vs_Community.exe), on executing it, you are offered a number of development environments and, after selection, a number of optional items. Obviously, you can include a larger number of options than are required to build Password Safe if you perform other developement projects.

For Password Safe the following are required:

- Desktop developmentent with C++
- Additional required "optional" features

- Visual C++ ATL Support
- Windows 8.1 SDK and UCRT SDK
- MFC and ATL support (x86 and x64)

### Microsoft Visual Studio Numbering Systems

Microsoft has a number of numbering systems.

- First there is the year in which they released the Visual Studio edition e.g. 2008, 2010, 2012, 2013 and 2015.
- Next there is the compiler version. In general, this is one less than the year i.e. for Visual Studio 2015, the compiler version is 14.
- Next there is the "Platform Toolset" value within the project files and these are the compiler version * 10 i.e. 140 for VS2015.
- Lastly, there is the level of the compiler defined by pre-processor variable _MSC_VER and it has values:
  - 1700 for VS2012 VC11
  - 1800 for VS2013 VC12
  - 1900 for VS2015 VC14

  However, for Visual Studio 2017, Microsoft decided to change this. Although, one would expect the complier version for this edition to be 15, Microsoft decided to make it 14.1 and so the Platform Toolset has a value of 141. In addition, it decided to set the variable _MSC_VER to 1910. Furthermore, if and when they release VS2017 Update 1, the value of _MSC_VER will change to 1911 etc. for Update 2, 3 .... They say that this is to allow developers to decide what new features an update provides to include in their project.

  Password Safe doesn't use the actual value of _MSC_VER and only in 2 files (as of March 2017), although pugixml (used to parse the application preferences from the configuration file) does check that that it is greater than 1300 or 1600 and so the new value of this pre-processor variable should not affect Password Safe.

  To keep with Password Safe numbering, the VS2017 solution and project files will be named with suffix "15" even though the projects will refer to Platform Toolset of 141 internally. The Platform Toolset will be incremented as and when Microsoft release updates to VS2017. In general, we keep which-ever Visual Studio version we use fully up to date to ensure bugs that affect the quality of the generated application are fixed, rather than to utilise new features.

  ### Software Requirements

  ### Getting Source code

  The source code for Password Safe may be downloaded as a zip file, or retrieved from the git repository via "git clone https://github.com/pwsafe/pwsafe.git".

  Currently, the Windows version is built using Microsoft's development tools as described below.

  If you're going to commit code to the repository, please set your git client's configuration file as follows:

  In the file ".gitconfig"

      [core]
      	autocrlf = true
      	safecrlf = warn

  (This file under "C:\Users\<username>\" on Windows 7 and later. If using TortoiseGit client under Windows, this can be accessed by right clicking a file, selecting TortoiseGit and then select Settings from the menu. Within the "Git" setting "Config source", select the "Global" radio button and then set the "AutoCrlf" checkbox and set "SafeCrlf" to "warn". Alternatively, you can click the button "Edit global .gitconfig" to change the file manually).

  For Windows, when installing "Git for Windows" (required by TortoiseGit and most other Git clients), ensure that you select "Checkout as-is, Commit as-is" to prevent incorrect line endings.

  ### Building the Windows Version of Password Safe

  The Windows version of Password Safe can be built using Microsoft Visual Studio 2015 (C++ compiler for Password Safe ('VC14') and C# compiler if you wish to re-generate the Virtual Keyboard data, which is not normally necessary).

  The main (top level) Microsoft Visual Studio 2015 solution file is pwsafe-14.sln.

  In order to build the Windows version of Password Safe, you need to install the following freely available components, in addition to Visual Studio:

  - Microsoft's Windows SDK. For VS2015 and VS2017, you should use version V8.1, which can be installed as part of the Visual Studio istallation.
  - To compile and produce the Help files (.chm) then Microsoft's HTML Help Workshop is required. Note however that the headers and libraries necessary for compiling Password Safe itself are included in the Windows SDK mentioned above.
  - A git client, such as Tortoise git Client (for updating the revision number within Password Safe's version details)
  - For XML Support, one or more of the following is needed (see the XML processing section for more details):
    - Headers and libraries to support Microsoft's XML V6.0 are included in the Windows SDK mentioned above and do not need to be installed separately.
    - Xerces V3.1.4 XML Library
  - For unit testing, Google's gtest 1.7.0 library is used. This is only used to build the Debug version of the src/test project, which may be disabled if desired.

  In addition, since the implementation of support for the YubiKey hardware, the Windows Driver Kit must also be installed and its libraries made available to Visual Studio. For VS2015 and VS2017, WDK V8.1 should be used. This is normally installed as part of the Visual Studio installation.

  #### Compiling using Visual Studio:

  - If you're using Microsoft's Visual Studio, the file "UserVariables-14.props" for VS2015, or "UserVariables-15.props" for VS2017 must exist and describe the directories where the non-"Windows SDK" components have been installed. The solution will not open correctly without this file being present.
  - For your convenience, we've included simple Visual Basic scripts, "configure-14.vbs" and "configure-15.vbs" for VS2015 and VS2017, respectively, in the src/ui/Windows directory (src/ui/wxWidgets directory for the wxWidgets builds), that you can run to generate the above file with the correct values. These scripts must be run via "cscript" in a Command Prompt window in their directory. These scripts will also prompt for the location of the 64-bit Xerces libraries for 64-bit builds. If you are not going to build the wxWidgets version, you can accept the default location of both wxWidgets and Xerces XML processor and you do not have to install either of these software libraries nor generate their libraries.
  - When migrating from previous versions to VS2015 or VS2017, ensure that you run the configure-14.vbs or configure-15.vbs in order to add the location of the Windows Driver Kit for a successful build of the YubiKey library.

  ### XML Processing

  Originally, Password Safe used Microsoft's XML library for XML parsing and validation. For portability, we're now support the Xerces XML libraries, which are also available for non-Windows platforms. We recommend the latest version (currently 3.1.4 as of March 2017). For VS2015 (VC14), you will need to copy and modify the directory ..\xerces-c-3.1.4\projects\Win32\VC12 to ..\xerces-c-3.1.4\projects\Win32\VC14 and open the solution file xerces-all.sln in subdirectory xerces-all and let VS2015 convert the project. You only need to build the project "Static Debug" and/or "Static Release" configurations of project XercesLib. Note: for 64-bit Xerces builds, you must use the 64-bit versions of the Xerces libraries. See note below re: building Xerces XML libraries with Visual Studio 2017.

  It is important that you have the Xerces libraries built with the same version of Visual Studio as you are using to build Password Safe. You will receive numerous error messages during the link stage if they are not the same. The same applies to the wxWidgets library if building that version of Password Safe under Windows.

  To determine which XML library to use while building Password Safe, we've defined a pre-processor variable (USE_XML_LIBRARY). If NOT defined, the compiled Password Safe will not process XML files (databases or filter definitions in XML format). Filters within a database will be treated as 'Unknown Fields' and will remain unchanged so that other versions of Password Safe that do support XML parsing can still use them. Note, however, that the application will be able to write XML files.

  The two valid values of the USE_XML_LIBRARY variable are "MSXML" and "XERCES" corresponding to the two different implementations. For wxWidgets builds, only XERCES will be possible.

  Password Safe uses SAX2 processing for both Microsoft's and the Xerces' XML Parsers, which are full validating parsers and require the presence of the appropriate XSD Schema file (included in the distribution and in the "xml" sub-directory, to process either file or filter imports. This ensures that the data eventually hitting the SAX2 content handlers is correct and just needs placing in the appropriate fields.

  ### Gtest framework

  The following instructions were written for version 1.7.0 of gtest.

  Password Safe uses the gtest framework in the Debug build - specifically the Debug build of the coretest project.

  To generate the required library, open gtest.sln in the "msvc" sub-directory in the gtest directory. For Visual Studio 2017, its solution and project files are supplied a zip file in the Misc/gtest sub-directory. They have already been converted for VS2017 and should be extracted as described in the Notes.txt file.

  You only need to build the Debug version of gtest library (gtestd.lib) in the gtest project of the solution "gtest.sln". However, if you use the CMake process, it does require the "gtest_maind.lib" library and their Release equivalents. In this case, it is probably easier to right-click on the gtest_main project and build both configurations since this project builds both libraries.

  Password Safe does not use the "gtest-md.sln" solution nor following projects in gtest.sln:

  1. gtest_main (except if you use CMake as above)
  2. gtest_prod_test
  3. gtest_unittest

  The following changes should be made to the (converted) project file:

  1. Configuration Properties: General: (where NN is 14 for VS2015 & 15 for VS2017)
     - All configurations:
       Output directory: ..\build-vcNN/$(Configuration)\
       Intermediate Directory: $(Configuration)/$(ProjectName)\
     - Debug configuration:
       Target Name: $(ProjectName)d
     - Release configuration (not used by Password Safe):
       Target Name: $(ProjectName)
  2. Configuration Properties: C/C++: General
     - Debug configuration:
       Debug Information Format: Program Database (/Zi)
  3. Configuration Properties: C/C++: Output Files
     - Debug configuration:
       Program Database File Name: $(OutDir)\$(ProjectName)d.pdb
     - Release configuration (not used by Password Safe):
       Program Database File Name: $(OutDir)\$(ProjectName).pdb

  If you wish to build the 64-bit version, you will first have to create a new platform x64 and then make similar changes as above. Note: When creating the new platform via the Configuration Manager, it is easier to select copy from the current x86 platform and then just make the changes marked in bold below but do not forget to add WIN64 to the C pre-processor definitions for the x64 platform:

  1. Configuration Properties: General: (where NN is 14 for VS2015 & 15 for VS2017)
     - All configurations:
       Output directory: ..\build-vcNN/$(Configuration)64\
       Intermediate Directory: $(Configuration)/$(ProjectName)64\
     - Debug configuration:
       Target Name: $(ProjectName)d
     - Release configuration (not used by Password Safe):
       Target Name: $(ProjectName)
  2. Configuration Properties: C/C++: General
     - Debug configuration:
       Debug Information Format: Program Database (/Zi)
  3. Configuration Properties: C/C++: Output Files
     - Debug configuration:
       Program Database File Name: $(OutDir)\$(ProjectName)d.pdb
     - Release configuration (not used by Password Safe):
       Program Database File Name: $(OutDir)\$(ProjectName).pdb

  Please remember to (re-)run the Password Safe configure-14.vbs or configure-15.vbs script to set the necessary gtest include and library directories. These would normally be the subdirectories "include" and either "build-vc14" or "build-vc15" of the "gtest-1.7.0" directory.

  Note: you can also make the similar changes to those above in the projects not used by Password Safe in gtest.sln if you wish to run the gtest Test programs.

  ### Building Xerces XML Parser for Windows

  We have provided Visual Studio 2017 solution and project files to build the necessary Xerces libraries under Windows. They are in a zip file in the Misc/Xerces 3.1.4 subdirectory. Please follow the instructions in the Notes.txt file. Note: the Xerces solution has a large number of projects - most are not needed. Once the solution is loaded, the only project that needs to be built is "XercesLib". There are multiple configurations available but, again, the only configurations required are: "Static Debug" and "Static Release" for platforms x86 and x64. The resulting libraries should be moved into the directories specified in the UserVariables-15.props file. The x86 Static Debug and Static Release versions should be in the same x86 directory and x64 Static Debug and Static Release versions should in the same x64 directory.

  ### Bulding the wxWidgets User Interface for Windows

  The wxWidgets is used for the non-Windows User Interface but it can also be used under Windows. After downloading from the wxWidgets web site (currently V3.0.2), there are solution and project files up to Visual Studio 2013. However, we have provided a solution and associated project files for Visual Studio 2017 in the Misc/wxWidgets_VS_Updates directory. Please follow the instructions in the Notes.txt file in that directory.

  You will need to build the Debug and Release versions for x86 and x64. The resulting libraries

  will then need to be copied to a different location (or their directory names renamed from vc_lib and vc_64_lib to vc150_lib and vc150_64_lib respectively. Previous wxWidgets generation was via a batch command but Microsoft has not implemented the System Environment variable for VS2017 that would allow this to be used.

  ### Wix MSI Installer (Windows only)

  MSI installer files for the x86 and x64 platforms can be created using the Wix Toolset. The current version is 3.10. The Wix Toolset is available at http://wixtoolset.org/releases/

  To build the MSI files, open a command prompt and change to the root directory of your source tree. Run the following command.

       install\windows\BuildWixInstall.bat

  This will build MSI files for both x86 and x64 platforms in the root directory. The program version specified in version.mfc will be applied to the .msi file.

       pwsafe.msi
       pwsafe64.msi

  You can build the files individually this way.

       install\windows\BuildWixInstall.bat x86
       install\windows\BuildWixInstall.bat x64

  If you need to work on the Wix script (.wxs file), you can find it in the install\windows directory.

       pwsafe-template.wxs

  ### Minidump Production (Windows only)

  In order to help debug user problems when Windows just says "there has been an error", a "Windows Unhandled Fault Handler" has been added. This will create a minidump, which can then be used to find where the error took place and, hopefully, why.

  An extra "extended" Command Line flag of "--testdump" has been introduced for two reasons. Firstly, it allows the developer to test the minidump process, which is only available in the Release version of the executable and, secondly, allows the translators to check that the error screen displays as they wish.

  Note to Translators: the error screen is a basic Windows function and has a fixed width. This is the reason why the minidump file name and directory have been split onto separate lines.

  Note: Extended flags start with two minus signs ('--') and must be specified in full - i.e. no abbreviations. They are not displayed in the Usage notes for the normal users and no error message or display is shown if they are not recognised.

  With this flag set, an extra button will appear in the bottom right hand corner of the "About Password Safe" dialog. Click it, and a minidump should be produced.

  In order to process the minidump, either the free Microsoft Windbg program can be used (see Microsoft's site for details), or Visual Studio (VS) can be used. In the latter case (and probably the former too!):

  1. You need the source corresponding to the failing release version. This should be available from SourceForge web site either in the normal Download section or from the Subversion repository, based on the revision number associated with that release. Without the corresponding source, VS can only show Windows source and line numbers in Password Safe source. With the corresponding source, VS can show you the exact line in Password Safe where the error took place and also the other statements within Password Safe as you follow the stack trace.
  2. You need the Program Debug Database (pwsafe.pdb) associated with the failing release. This is not normally uploaded to the SourceForge web site with the release package. It is large (~11.5MB or ~3MB compressed). Since this must correspond to the Password Safe executable that had the error, maybe this and, possibly, the associated Link Map can be uploaded to a Developers section on this web site to aid all developers.
  3. You should probably maintain the directory structure of the project as described in the source downloaded from SourceForge and place the Program Debug Database file in the '..\build\bin\pwsafe\release' directory.
  4. Save the user's minidump file on your PC. Use VS to Open this as a Project (e.g. File->Open->Project/Solution).
  5. In the Debugging Options, specify the directory containing the corresponding PDB file. (Go to: Tools->Options->Debugging->Symbols and add this directory in the section entitled "Symbol file (.pdb) locations:").
  6. Press F5 to start debugging, and away you go.

  *** End of Developer Notes ***