QESTNET Internal:Developer Setup QESTField: Difference between revisions
David.lucas (talk | contribs) No edit summary |
David.lucas (talk | contribs) No edit summary |
||
| Line 7: | Line 7: | ||
**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. | **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. | ||
*Start Debugging ('''F5'''). <BR>This will launch a web browser. The choice of web browser is configured in Visual Studio where Start Debugging is. <BR>Google Chrome is the recommended choice for QESTField development. The browser will take you to the web address of a local ASP.NET Development Server which Visual Studio has spun up. The login page of QESTField should be displayed. <BR>You can login using any QESTLab login credentials which are available in the database and have permission to use QESTField. | *Start Debugging ('''F5'''). <BR>This will launch a web browser. The choice of web browser is configured in Visual Studio where Start Debugging is. <BR>Google Chrome is the recommended choice for QESTField development. The browser will take you to the web address of a local ASP.NET Development Server which Visual Studio has spun up. The login page of QESTField should be displayed. <BR>You can login using any QESTLab login credentials which are available in the database and have permission to use QESTField. | ||
**Error: "Underlying service failed to Open." - Check the Event Viewer log. It is normally due to the QESTNET service credentials not having permission to access the QESTLab database. | |||
Revision as of 03:27, 20 July 2015
QESTField
- Open ~\qestnet\QESTField MVC\QESTField.sln
- If the solution does not load, check that .NET Framework 4.5 and ASP.NET MVC 4 are installed on your local machine.
- Build the solution. There should not be any errors
- Go to Debug > Exceptions
- Find System.ServiceModel.FaultException`1
- Uncheck User-unhandled.
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.
- Start Debugging (F5).
This will launch a web browser. The choice of web browser is configured in Visual Studio where Start Debugging is.
Google Chrome is the recommended choice for QESTField development. The browser will take you to the web address of a local ASP.NET Development Server which Visual Studio has spun up. The login page of QESTField should be displayed.
You can login using any QESTLab login credentials which are available in the database and have permission to use QESTField.- Error: "Underlying service failed to Open." - Check the Event Viewer log. It is normally due to the QESTNET service credentials not having permission to access the QESTLab database.