Skip to main content

Pangea

Here are the steps to be able to work on the

Running Pangea code compiling and running locally

  1. CloneImport the Pangeasigning Repo (here  is the link to it)
  2. Put this EFCO.zip folder in the ../Pangea/Migration/Lib folder
certificate
    • (Note: There should now be 'Desktop', 'EFCO', and 'Utopia' folders in the 'Lib' folder. Also make sure that the Workflows.dll file is the only child of the EFCO folder you just added to Lib)
  1. Open Visual Studio and open the Tandoori Tool solution
    3.1. Navigate to branch 'pwilliams/serverDataAccessDllUpdate'
    3.2. Once this pull request goes through we can remove steps 3.1 and 3.2
  2. Build the entire solution (it will fail)
  3. Navigate to ../Pangea/Migration/Pangea\Migration\Tandoori Tool/Tool\Tandoori Tool and double click efcKey.pfx.
  4. This will pop open a wizard to walk you through importing the 'efcKey.pfx'signing file
    5.1.certificate.
    5. Leave
  5. Just hit next and leave all thesetting configurationsto asdefault default, and when it asksuntil you forprompted ato keyenter the password.
  6. The password can be found in the 'sign_file.bat'.pfx whichcertificate' cansecure note in last pass.
  7. You should be foundgood to go. Just hit Start in ../Pangea/Publishingvisual studio.
    Publishing
  • Instructions

    • (weWe willhave bea backbuild herepipeline inthat later steps so keepdoes this openfor inyou, Filebut Explorer)if you ever do need do a build locally you can follow these steps.

  1. Clean and Rebuild the entire solution (itin shouldthe build'Release' successfully)configuration and 'any cpu' platform selected.
  2. Now back in the ../Pangea/Publishing folder, edit the publish_base.bat so that the variable 'msbuild' looks similar to 'C:\Program Files\Microsoft Visual Studio\2022\Professional\MSBuild\Current\Bin\MSBuild.exe'
  • (or wherever your Visual Studio is installed. The most important part is that this points to the MSBuild.exe file)
  1. You can now run 'publish_production.bat' and it should run'publish_staging.bat' to completion
  2. First time it will create an 'output' folder inside of ../Pangea/Publishing - navigate to Publish_Production
  3. You can now runall the migrationfiles tool by running setup.exe
 
  • (first time it willthat need to download,be justpublished acceptto everythingS3. andThey continue.can Itbe willfound alsoat say that Windows doesn't trust it but just run anyway)Pangea\Publishing\output.
Back to top