QESTNET Internal:Developer Setup QESTNET

App Configuration

Config files often have ever changing information specific to your setup in them. As such files with extension .config are ignored by git. See .gitignore files for other files git will ignore. All config files have an associated default file. e.g., app.config has app.config.default. This will give a new setup a starting template. If you add additional configuration properties make sure the .default file is updated as this is the only one committed to git.

• Run the batch file ~\qestnet\QESTNET\copy_default_config.bat
• The batch file will go through the qestnet repository and create .config files from the .default files

Create QESTNET Service

• Run ~\qestnet\QESTNET\bin\install_qestnet_debug.bat. This will create a QESTNET windows service on your machine.
• Open Services from the control panel.
• Right click the QESTNET service and select properties. Change the Log On permissions to your account or the windows NETWORK SERVICE account. If you use the NETWORK SERVICE account you will need to ensure it has the necessary permissions to ports and files the qestnet service will use.
• Start the service

QESTLab Schema Generator Setup

• Open ~\qestnet\QESTNET\QESTLab.SchemaGenerator\ QESTLab.SchemaGenerator.sln.
  • Build the solution, there should be no errors.
• Open ~\qestnet\QESTNET\QESTNET.sln
  • Open the app.config file in the QESTNET project.
  • Edit the QESTLab_Data connection string to point to the QESTLab database you want to connect to.

<add name="QESTLab_Data" connectionString="metadata=res://*/Spectra.QESTLab.Data.Entities.QESTLabModel.csdl|res://*/Spectra.QESTLab.Data.Entities.QESTLabModel.ssdl|res://*/Spectra.QESTLab.Data.Entities.QESTLabModel.msl;provider=System.Data.SqlClient;provider connection string="data source=ADLD0031;initial catalog=fugro_20150320_qestlab;integrated security=True;multipleactiveresultsets=True;App=EntityFramework"" providerName="System.Data.EntityClient" />

• Open the program Windows PowerShell ISE.
  • Enter set-executionpolicy remotesigned into the console
  • This comes up, click Yes

• Right-click the GenerateDataSchema.ps1 file in QESTLab.Data and select Open With
  • Click add new program (“Add...”)
  • Enter the PowerShell folder (C:\WINDOWS\system32\WindowsPowerShell\v1.0)
  • Click OK?
  • Click “set as default” on the open with window.
  • Click OK.

The file can now be run using PowerShell by double clicking on it in Visual Studio.

Build QESTLab.Data

The first time QESTLab.Data is built on a machine or if the bin is cleaned out for the project the following steps will need to be done. This is due to a circular reference that exists in QESTLab.Data. The QESTLab_Data_Views.tt references the QESTLab.Data.dll which is built using the QESTLab_Data_Views.tt output.

• Exclude QESTLab_Data_Views.tt from the QESTLab.Data project
• Build QESTLab.Data project
• Include QESTLab_Data_Views.tt
• Right click QESTLab_Data_Views.tt and select Run Custom Tool
• Build QESTLab.Data project

Update QESTLab.Data Schema

The following steps will update the QESTLab.Data schema to match the QESTLab database structure

• Run GenerateDataSchema.ps1
• Build QESTLab.Data project
• Right click QESTLab_Data_Views.tt and select Run Custom Tool
• Build QESTLab.Data project.

It is on the "to do" list to get the PowerShell script to do all the last three steps as well. This was initially a one click operation but no one can stop the inexorable march of progress.

Build QESTNET

• Open ~\qestnet\QESTNET\QESTNET.sln
• Build the solution. If there are no errors the QESTNET service has been successfully built and the service restarted.