-
Notifications
You must be signed in to change notification settings - Fork 14
Tutorial 04 03 Add Traditional Bridge Library Code
At this point we'll use the Harmony Core Upgrade Tool to make sure the Traditional Bridge templates and library code are up to date. The Harmony Core upgrade tool does three things:
-
Check all of your projects and make sure you are using the latest released version of Harmony Core and appropriate versions of all dependencies.
-
Provide updated versions of all CodeGen templates.
-
Add Traditional Bridge library code into your new
Bridge
folder.
-
In Visual Studio select
Tools > Command Prompt (x64)
to open a command prompt window. -
Then select
File > Close Solution
from the Visual Studio menu to close the Harmony Core solution. -
In the command prompt window, move up one level to your main solution directory and execute the following command:
cd .. harmonycore upgrade-latest
You will be required to enter
YES
to confirm the upgrade, and you should see output like this:Scanning 'C:\hc\tutorial\MyApi' for HarmonyCore project files Using MSBuild from path: C:\Program Files\dotnet\sdk\6.0.402 This utility will make significant changes to projects and other source files in your Harmony Core development environment. Before running this tool, we recommend checking the current state of your development environment into your source code repository or making a backup copy of the environment if you don't use source code control. Type YES to proceed: YES Updating template files in C:\hc\tutorial\MyApi\Templates Found template files in C:\hc\tutorial\MyApi\Templates\MySQL Found template files in C:\hc\tutorial\MyApi\Templates\SignalR Found template files in C:\hc\tutorial\MyApi\Templates\ReactRedux Found template files in C:\hc\tutorial\MyApi\Templates\TypeScript Found template files in C:\hc\tutorial\MyApi\Templates\TraditionalBridge Updating traditional bridge files in C:\hc\tutorial\MyApi\TraditionalBridge\Bridge
-
Close the command prompt, and then open the solution in Visual Studio.
Next topic: Add Traditional Bridge Routines
-
Tutorial 2: Building a Service from Scratch
- Creating a Basic Solution
- Enabling OData Support
- Configuring Self Hosting
- Entity Collection Endpoints
- API Documentation
- Single Entity Endpoints
- OData Query Support
- Alternate Key Endpoints
- Expanding Relations
- Postman Tests
- Supporting CRUD Operations
- Adding a Primary Key Factory
- Adding Create Endpoints
- Adding Upsert Endpoints
- Adding Patch Endpoints
- Adding Delete Endpoints
-
Harmony Core Code Generator
-
OData Aware Tools
-
Advanced Topics
- CLI Tool Customization
- Adapters
- API Versioning
- Authentication
- Authorization
- Collection Counts
- Customization File
- Custom Field Types
- Custom File Specs
- Custom Properties
- Customizing Generated Code
- Deploying to Linux
- Dynamic Call Protocol
- Environment Variables
- Field Security
- File I/O
- Improving AppSettings Processing
- Logging
- Optimistic Concurrency
- Multi-Tenancy
- Publishing in IIS
- Repeatable Unit Tests
- Stored Procedure Routing
- Suppressing OData Metadata
- Traditional Bridge
- Unit Testing
- EF Core Optimization
- Updating a Harmony Core Solution
- Updating to 3.1.90
- Creating a new Release
-
Background Information