User Interface for course directory, implemented using the provider portal APIs. Contains provider portal Azure resources in the Resources directory.

Manually create an empty database named CourseDirectoryTesting:

create database CourseDirectoryTesting;
ALTER DATABASE CourseDirectoryTesting SET ALLOW_SNAPSHOT_ISOLATION ON;

Run the tests.

The dacpac will automatically be deployed and create all the database schema and tables.

• Get user secrets from another developer on the team.

• Manually create empty database CourseDirectory:

create database CourseDirectory;
ALTER DATABASE CourseDirectory SET ALLOW_SNAPSHOT_ISOLATION ON;

• Right-click "Publish" on the database project then deploy to database CourseDirectory.

Temporarily configure user secret ConnectionStrings:DefaultConnection for project CourseDirectoryTesting to point to database CourseDirectory.

Run the tests in Dfc.CourseDirectory.WebV2.Tests, this will cause the dacpac to deploy.

Undo the temporary user secret configuration change.

Run project Dfc.CourseDirectory.Web

Navigate to https://localhost:44345/ in a browser.

Ask the team to make you a valid DfE Sign-in account with provider(s) associated with it.

This project depends on multiple deployed Azure function app resources:

• dfc-providerportal-courses
• dfc-providerportal-fileprocessor
• dfc-providerportal-tribalexporter
• dfc-providerportal-ukrlp

The projects in the Legacy solution folder were inherited without good test coverage and are not in an easily testable state.

New code is being written in the WebV2 project that is test-driven and uses modern patterns of development to achieve cleaner testable code.

See the WebV2 readme for details of the patterns in use.

The WebV2 controllers are made available under the legacy Dfc.CourseDirectory.Web project so that we can move routes across one at time. As such to run the WebV2 code you actually need to run the original "Web" project.