QESTNET Internal:Developer Setup QESTNET - Revision history

David.lucas at 00:14, 17 November 2015

2015-11-17T00:14:11Z

←Older revision		Revision as of 00:14, 17 November 2015
Line 12:		Line 12:
	*Run the batch file '''~\qestnet\QESTNET\copy_default_config.bat'''		*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.		*The batch file will go through the qestnet repository and create '''.config''' files from the '''.default''' files.

			=====Unhandled Login Fault Exception=====
			*Open '''~\qestnet\QESTNET\QESTNET.sln'''
			*Go to '''Debug > Exceptions'''
			**Find '''System.ServiceModel.FaultException`1'''
			**Uncheck '''User-unhandled'''.<BR> This will stop the debugger breaking on a fault exception catch every time you login. It is on a "to do" list somewhere to fix... really I (DL) promise.

	=====QESTLab Schema Generator Setup=====		=====QESTLab Schema Generator Setup=====

Sean.brimble at 00:39, 17 August 2015

2015-08-17T00:39:53Z

←Older revision		Revision as of 00:39, 17 August 2015
Line 22:		Line 22:
	*Open '''~\qestnet\QESTNET\QESTNET.Service\QESTNET.Sessions\app.config'''		*Open '''~\qestnet\QESTNET\QESTNET.Service\QESTNET.Sessions\app.config'''
	*Open '''~\qestnet\QESTNET\QESTNET.Custom\QESTNET.Custom.Fugro.DataBackbone.Tests\app.config'''		*Open '''~\qestnet\QESTNET\QESTNET.Custom\QESTNET.Custom.Fugro.DataBackbone.Tests\app.config'''
	*Open '''~\qestnet\QESTNET\QESTNET.~~Service~~.Lab\Tester\app.config'''		*Open '''~\qestnet\QESTNET\QESTNET.Sessions.Lab\Tester\app.config'''
	**Check or change the storage location.<br><br>''<add key="fileStorePath" value="<span style="color:#0000FF">C:\NEEDSTOEXIST</span>" />''<br><br>		**Check or change the storage location.<br><br>''<add key="fileStorePath" value="<span style="color:#0000FF">C:\NEEDSTOEXIST</span>" />''<br><br>
	*Open the program '''Windows PowerShell ISE''' with Administrator rights.		*Open the program '''Windows PowerShell ISE''' with Administrator rights.

Sean.brimble at 00:35, 17 August 2015

2015-08-17T00:35:08Z

←Older revision		Revision as of 00:35, 17 August 2015
Line 35:		Line 35:
	**Click “set as default” on the open with window.		**Click “set as default” on the open with window.
	**Click OK.		**Click OK.
	The file can now be run using PowerShell by double clicking on it in Visual Studio.		The file can now be run using PowerShell by double clicking on it in Visual Studio. Run this file.

	=====Build QESTLab.Data=====		=====Build QESTLab.Data=====

Sean.brimble at 00:00, 17 August 2015

2015-08-17T00:00:50Z

←Older revision		Revision as of 00:00, 17 August 2015
Line 31:		Line 31:
	*In Visual Studio, right-click the '''GenerateDataSchema.ps1''' file under QESTNET.Sessions.Lab\QESTLab.Data\Entities and select Open With		*In Visual Studio, right-click the '''GenerateDataSchema.ps1''' file under QESTNET.Sessions.Lab\QESTLab.Data\Entities and select Open With
	**Click add new program (“Add...”)		**Click add new program (“Add...”)
	**Enter the PowerShell ~~folder~~ (C:\WINDOWS\system32\WindowsPowerShell\v1.0)		**Enter the PowerShell Executable (C:\WINDOWS\system32\WindowsPowerShell\v1.0\powershell_ise.exe)
	**Enter a Friendly Name (i.e. ~~Windows Power Shell~~)
	**Click OK?		**Click OK?
	**Click “set as default” on the open with window.		**Click “set as default” on the open with window.

Sean.brimble at 23:58, 16 August 2015

2015-08-16T23:58:26Z

←Older revision		Revision as of 23:58, 16 August 2015
Line 32:		Line 32:
	**Click add new program (“Add...”)		**Click add new program (“Add...”)
	**Enter the PowerShell folder (C:\WINDOWS\system32\WindowsPowerShell\v1.0)		**Enter the PowerShell folder (C:\WINDOWS\system32\WindowsPowerShell\v1.0)
			**Enter a Friendly Name (i.e. Windows Power Shell)
	**Click OK?		**Click OK?
	**Click “set as default” on the open with window.		**Click “set as default” on the open with window.

Sean.brimble at 23:54, 16 August 2015

2015-08-16T23:54:50Z

←Older revision		Revision as of 23:54, 16 August 2015
Line 24:		Line 24:
	*Open '''~\qestnet\QESTNET\QESTNET.Service.Lab\Tester\app.config'''		*Open '''~\qestnet\QESTNET\QESTNET.Service.Lab\Tester\app.config'''
	**Check or change the storage location.<br><br>''<add key="fileStorePath" value="<span style="color:#0000FF">C:\NEEDSTOEXIST</span>" />''<br><br>		**Check or change the storage location.<br><br>''<add key="fileStorePath" value="<span style="color:#0000FF">C:\NEEDSTOEXIST</span>" />''<br><br>
	*Open the program Windows PowerShell ISE with Administrator rights.		*Open the program '''Windows PowerShell ISE''' with Administrator rights.
	**Enter '''set-executionpolicy remotesigned''' into the console		**Enter '''set-executionpolicy remotesigned''' into the console
	**This comes up, click Yes		**This comes up, click Yes

Weiwen.chi at 03:08, 29 July 2015

2015-07-29T03:08:54Z

←Older revision		Revision as of 03:08, 29 July 2015
Line 62:		Line 62:
	**The batch file assumes naively that InstallUtil.exe is installed at "C:\Windows\Microsoft.NET\Framework\v4.0.30319\InstallUtil.exe". If it is not, you will need to change the batch file to suit your local machine. Do not commit these changes.		**The batch file assumes naively that InstallUtil.exe is installed at "C:\Windows\Microsoft.NET\Framework\v4.0.30319\InstallUtil.exe". If it is not, you will need to change the batch file to suit your local machine. Do not commit these changes.
	*Open Services from the control panel.		*Open Services from the control panel.
	*Right click the QESTNET service and select properties. Change the Log On permissions to your account ("sqaus/''your.name''") 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.		*Right click the QESTNET service and select properties. Change the Log On permissions to your account ("sqaus\''your.name''") 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		*Start the service
	[[Image:QESTNET Service.jpg]]		[[Image:QESTNET Service.jpg]]

Shane.rowley: /* QESTLab Schema Generator Setup */

2015-07-21T03:14:13Z

QESTLab Schema Generator Setup

←Older revision		Revision as of 03:14, 21 July 2015
Line 19:		Line 19:
	**Open the app.config file in the project QESTNET.Service\QESTNET.		**Open the app.config file in the project QESTNET.Service\QESTNET.
	*Edit the QESTLab_Data connection string to point to the QESTLab database you want to connect to.<br><br>''<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="<span style="color:#0000FF">data source=ADLD0031;initial catalog=fugro_20150320_qestlab;</span>integrated security=True;multipleactiveresultsets=True;App=EntityFramework"" providerName="System.Data.EntityClient" />''<br><br>		*Edit the QESTLab_Data connection string to point to the QESTLab database you want to connect to.<br><br>''<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="<span style="color:#0000FF">data source=ADLD0031;initial catalog=fugro_20150320_qestlab;</span>integrated security=True;multipleactiveresultsets=True;App=EntityFramework"" providerName="System.Data.EntityClient" />''<br><br>
	*Open '''~\qestnet\QESTNET\QESTNET.Service.Lab\~~QESTNET~~\app.config'''		*Open '''~\qestnet\QESTNET\QESTNET.Service\QESTNET\app.config'''
			*Open '''~\qestnet\QESTNET\QESTNET.Service\QESTNET.Sessions\app.config'''
			*Open '''~\qestnet\QESTNET\QESTNET.Custom\QESTNET.Custom.Fugro.DataBackbone.Tests\app.config'''
			*Open '''~\qestnet\QESTNET\QESTNET.Service.Lab\Tester\app.config'''
	**Check or change the storage location.<br><br>''<add key="fileStorePath" value="<span style="color:#0000FF">C:\NEEDSTOEXIST</span>" />''<br><br>		**Check or change the storage location.<br><br>''<add key="fileStorePath" value="<span style="color:#0000FF">C:\NEEDSTOEXIST</span>" />''<br><br>
	*Open the program Windows PowerShell ISE with Administrator rights.		*Open the program Windows PowerShell ISE with Administrator rights.

Shane.rowley: /* Build QESTLab.Data */

2015-07-20T08:08:34Z

Build QESTLab.Data

←Older revision		Revision as of 08:08, 20 July 2015
Line 37:		Line 37:
	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.		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		*Exclude '''QESTLab_Data_Views.tt''' from the QESTLab.Data project
			** Right-click file name and select to exclude it from the menu.<br>[[Image:QESTNet_Build_Fugro_Exclude.png]]
	*Build QESTLab.Data project		*Build QESTLab.Data project
	*Include '''QESTLab_Data_Views.tt'''. If you cannot see this file, click the "Show All Files" button on the Solution Explorer toolbar.		*Include '''QESTLab_Data_Views.tt'''. If you cannot see this file, click the "Show All Files" button on the Solution Explorer toolbar.

Shane.rowley: /* Rebuild QESTNET */

2015-07-20T07:58:50Z

Rebuild QESTNET

←Older revision		Revision as of 07:58, 20 July 2015
Line 66:		Line 66:
	=====Rebuild QESTNET=====		=====Rebuild QESTNET=====
	*Open '''~\qestnet\QESTNET\QESTNET.sln'''		*Open '''~\qestnet\QESTNET\QESTNET.sln'''
			*Unload non-Fugro projects
			**Highlight all non-Fugro Projects under '''QESTNET.Custom''', right-click and '''Unload Projects'''<br>[[Image:QESTNet_Build_Fugro_UnloadNonFugroProjects.png]]
	*Build the solution. If there are no errors the QESTNET service has been successfully built and the service restarted.		*Build the solution. If there are no errors the QESTNET service has been successfully built and the service restarted.