Developer Initial Setup

This is a short guideline of the initial set up for a developer to work on the Blazor helpers

1. Core Environment & Infrastructure

• IDE: Visual Studio 2022 is the required standard for this project.

• VPN Connection: You must be connected to the VPN to view GAP packages and open the DCP (Development Control Plane).

• Account Syncing: Your local machine account must be linked/configured with your GAP account to ensure seamless access to NuGet packages.

• Helpdesk Permissions: Ensure you request all necessary permissions from HelpDesk before starting the setup.

1. Telerik Configuration

• GAP Email Registration: You must create a Telerik account using your GAP email address.

• Authentication: This account is mandatory; the system will prompt for these credentials whenever it attempts to resolve or restore Telerik packages.

1. Code Quality & SonarQube

• SonarCloud Access: Log in to sonarcloud.io using your GAP credentials.

• SonarLint Extension: To identify Code Smells in real-time, install the SonarLint for Visual Studio 2022 extension. Note: Contact Carlos Chevez to assist with the binding configuration.

1. Alpha Generation & Unit Testing

• Mandatory Testing: You cannot generate Alphas in the Blazor DCP or the HTML Generator without Unit Tests.

• SonarQube Coverage: Any Alpha build must meet the code coverage threshold required by SonarQube; otherwise, the build process will fail.

1. NuGet Packages & Pipelines

• Manual NuGet Generation: The Blazor DCP does not generate NuGets automatically. You must navigate to the Pipeline, trigger a manual run, and select the required branch.

• HTML Generator: This tool handles Alphas but shares the same dependency: no Alpha will be created without Unit Tests.

1. The Migrator (Special Requirements)

• Framework Dependency: You must have .NET Framework 4.6 installed specifically for the Migrator to function.

• README Compliance: Strictly follow the steps outlined in the README file.

• Build Folder Programs: You must run two programs located in the build folder. Critical Note: These programs point to a filesystem/folder that is only accessible via a Mobilize account.

1. DCP Solution Compilation Requirements

• Local NuGet Feed: Because the Telerik v12 packages are in .zip format, you must extract them to a local folder and add that folder as a Package Source in Visual Studio (Tools > NuGet Package Manager > Package Manager Settings > Packages Sources).

Steps to manually install Telerik v12 packages in Visual Studio, follow this steps to configure as local source:

• Click on 'Package Source' to view all available sources.

• Click the '+' (plus) button to add a new package source.

• Click the ellipsis button '...' to browse to the folder where you extracted the packages. Once selected, you can rename it for easier identification.

• Verify that the path points to the local folder and click 'Ok'.

Or you can follow Telerik download and installation from Download to install DevExpress version 21, proceed by installing the Trial version.