Installation Guide

Overview

This guide will walk you through installing and configuring Sistema de Seguimiento de Solicitudes on your local machine or server. The installation process involves setting up the database, configuring the API, and running the frontend application.

Estimated Time: 20-30 minutesDifficulty: Intermediate - Requires familiarity with .NET development and SQL Server

Prerequisites

Before you begin, ensure your system meets the following requirements:

Required Software

.NET 9.0 SDK

Download and install the .NET 9.0 SDK from Microsoft’s official website.Verify installation:

dotnet --version
# Should output: 9.0.x or higher

SQL Server

Install one of the following:

SQL Server 2019 or later (Express, Developer, or Enterprise)
SQL Server LocalDB
Azure SQL Database

Download from: Microsoft SQL Server

SQL Server Management Studio (SSMS)

Recommended for database management and import operations.Download from: SQL Server Management Studio

Visual Studio 2022 (Recommended)

Visual Studio 2022 or later with the following workloads:

ASP.NET and web development
.NET desktop development

Alternative: Visual Studio Code with C# extension

Keep Visual Studio updated to avoid framework compatibility issues.

Node.js (Optional)

Required only for accessibility auditing features.Version: 18.x or laterDownload from: Node.js

System Requirements

Component	Minimum	Recommended
OS	Windows 10, Windows Server 2016, Linux (Ubuntu 20.04+)	Windows 11, Windows Server 2022
RAM	4 GB	8 GB+
Disk Space	2 GB	5 GB+
CPU	2 cores	4+ cores

Step 1: Clone the Repository

First, clone or download the source code:

git clone <repository-url>
cd "Sistema de Seguimiento de Solicitudes"

Step 2: Database Setup

The application uses SQL Server as its database. Follow these steps to set it up:

Import the Database

The project includes a .bacpac file for easy database import.Using SQL Server Management Studio:

Open SQL Server Management Studio (SSMS)
Connect to your SQL Server instance
Right-click on Databases in Object Explorer
Select Import Data-tier Application…
Click Next, then Browse
Navigate to the project folder and select SistemaSolicitudes.bacpac
Click Next and ensure the database name is exactly: SistemaSolicitudes
Click Next and then Finish to complete the import

The database name must be exactly SistemaSolicitudes to match the connection string, or you’ll need to update the connection string accordingly.

Verify Database Schema

After import, verify the following tables exist:

-- Run in SSMS to verify tables
SELECT TABLE_NAME 
FROM INFORMATION_SCHEMA.TABLES 
WHERE TABLE_TYPE = 'BASE TABLE'
ORDER BY TABLE_NAME;

Expected tables:

Calendario
DiaInhabilManual
Expedientes
MT_EXPEDIENTE_ARCHIVOS
MT_RECURSO_REVISION
Usuarios

Configure Database Server

Note your SQL Server instance name. Common formats:

(local) - Local default instance
(localdb)\MSSQLLocalDB - LocalDB instance
.\SQLEXPRESS - SQL Server Express
SERVER_NAME\INSTANCE_NAME - Named instance
server.domain.com - Remote server

Test connectivity:

-- In SSMS, run:
SELECT @@SERVERNAME AS ServerName, 
       @@VERSION AS VersionInfo;

Step 3: Configure the API

Now configure the backend API to connect to your database:

Navigate to API Project

cd SolicitudesAPI

Update Connection String

Open appsettings.json and update the connection string:

appsettings.json

{
  "ConnectionStrings": {
    "DefaultConnection": "Server=(local); DataBase=SistemaSolicitudes; Trusted_Connection=True; TrustServerCertificate=True;"
  }
}

Replace (local) with your SQL Server instance name.

{
  "ConnectionStrings": {
    "DefaultConnection": "Server=(local); DataBase=SistemaSolicitudes; Trusted_Connection=True; TrustServerCertificate=True;"
  }
}

For production environments:

Never commit credentials to source control
Use environment variables or Azure Key Vault
Set TrustServerCertificate=False and configure proper SSL certificates

Configure JWT Settings

Update the JWT configuration in appsettings.json:

appsettings.json

{
  "Jwt": {
    "SecretKey": "B+UjX3CzV1xL5mPjYsQ0N6W7fZ9hRg2T",
    "Issuer": "Issuer",
    "Audience": "Audience"
  }
}

CRITICAL FOR PRODUCTION:

Generate a new, cryptographically secure secret key (minimum 32 characters)
Update Issuer to your domain name
Update Audience to your application identifier
Store the secret key in a secure location (Azure Key Vault, environment variables)

Generate a secure key:

# PowerShell
-join ((65..90) + (97..122) + (48..57) + (33..47) | Get-Random -Count 32 | ForEach-Object {[char]$_})

# Linux/Mac
openssl rand -base64 32

Review Launch Settings

Check Properties/launchSettings.json for API URLs:

Properties/launchSettings.json

{
  "profiles": {
    "https": {
      "commandName": "Project",
      "launchBrowser": false,
      "launchUrl": "scalar/v1",
      "applicationUrl": "https://localhost:7123;http://localhost:5273",
      "environmentVariables": {
        "ASPNETCORE_ENVIRONMENT": "Development"
      }
    }
  }
}

The API will run on:

HTTPS: https://localhost:7123
HTTP: http://localhost:5273

You can change launchBrowser to true to automatically open the Scalar API documentation when starting the API.

Restore NuGet Packages

dotnet restore

This installs all required dependencies:

Entity Framework Core 9.0.4
JWT Bearer Authentication
QuestPDF for PDF generation
Scalar for API documentation

Test API Connection

Verify the API can connect to the database:

dotnet build

If successful, you should see:

Build succeeded.
    0 Warning(s)
    0 Error(s)

Step 4: Configure the Frontend

Configure the Blazor WebAssembly frontend application:

Navigate to Frontend Project

cd "../Sistema de Seguimiento de Solicitudes"

Update API Base URL

Open Program.cs and verify the HttpClient configuration:

Program.cs

// Line 18
builder.Services.AddScoped(sp => new HttpClient 
{ 
    BaseAddress = new Uri("https://localhost:7123/") 
});

This URL must match your API’s HTTPS URL from the previous step.

If you changed the API port in launchSettings.json, update this URL accordingly.

Review Launch Settings

Check Properties/launchSettings.json for frontend URLs:

Properties/launchSettings.json

{
  "profiles": {
    "https": {
      "commandName": "Project",
      "launchBrowser": false,
      "applicationUrl": "https://localhost:7125;http://localhost:5216",
      "environmentVariables": {
        "ASPNETCORE_ENVIRONMENT": "Development"
      }
    }
  }
}

The frontend will run on:

HTTPS: https://localhost:7125
HTTP: http://localhost:5216

Restore NuGet Packages

dotnet restore

This installs all frontend dependencies:

Blazor WebAssembly 9.0.4
MudBlazor UI components
Radzen Blazor components
SweetAlert2 for notifications

Build Frontend

dotnet build

Verify successful build before proceeding.

Step 5: Run the Application

Now you’re ready to run both components:

Start the API (Backend)

In the SolicitudesAPI folder:

cd SolicitudesAPI
dotnet run --launch-profile https

You should see output similar to:

info: Microsoft.Hosting.Lifetime[14]
      Now listening on: https://localhost:7123
info: Microsoft.Hosting.Lifetime[14]
      Now listening on: http://localhost:5273
info: Microsoft.Hosting.Lifetime[0]
      Application started. Press Ctrl+C to shut down.

Leave this terminal window open. The API must be running for the frontend to work.

Start the Frontend (New Terminal)

Open a new terminal window and navigate to the frontend folder:

cd "Sistema de Seguimiento de Solicitudes"
dotnet run --launch-profile https

You should see:

info: Microsoft.Hosting.Lifetime[14]
      Now listening on: https://localhost:7125
info: Microsoft.Hosting.Lifetime[0]
      Application started. Press Ctrl+C to shut down.

Access the Application

Open your browser and navigate to:

https://localhost:7125

You should see the login page.

If you see a certificate warning, this is normal for local development. Click “Advanced” and “Proceed” to continue.

Access API Documentation (Optional)

The API includes Scalar documentation. Access it at:

https://localhost:7123/scalar/v1

This provides interactive API documentation for all endpoints.

Step 6: Initial Configuration

Create Initial User

Since the database is fresh, create an admin user using the API:

curl -X POST https://localhost:7123/api/Auth/register \
  -H "Content-Type: application/json" \
  -d '{
    "nombreUsuario": "admin",
    "password": "YourSecurePassword123!",
    "rol": "Administrador"
  }'

Configure Calendar (Optional)

Set up working days and holidays for accurate deadline calculations.

-- Add manual non-working days
INSERT INTO DiaInhabilManual (Fecha, Descripcion)
VALUES 
  ('2026-01-01', 'Año Nuevo'),
  ('2026-12-25', 'Navidad');

Test the Installation

Login with your admin credentials
Navigate through the main modules
Create a test request
Verify calendar is working
Check API documentation at /scalar/v1

Running with Visual Studio

If you prefer using Visual Studio:

Open Solution

Double-click Sistema de Seguimiento de Solicitudes.sln to open in Visual Studio.

Set Multiple Startup Projects

Right-click on the solution in Solution Explorer
Select Properties
Go to Startup Project
Select Multiple startup projects
Set both SolicitudesAPI and Sistema de Seguimiento de Solicitudes to Start
Click OK

Run the Solution

Press F5 or click the Start button. Visual Studio will launch both the API and frontend simultaneously.

Production Deployment

For production environments, additional steps are required:

Before deploying to production:

Update JWT Secret Key: Generate a strong, unique secret key
Configure CORS: Restrict allowed origins to your domain
Enable HTTPS: Configure proper SSL certificates
Secure Connection Strings: Use Azure Key Vault or environment variables
Update Database: Use a production SQL Server instance
Configure Logging: Set up application insights or logging service
Review Security: Audit authentication and authorization settings

Environment-Specific Configuration

{
  "Logging": {
    "LogLevel": {
      "Default": "Warning",
      "Microsoft.AspNetCore": "Warning"
    }
  },
  "ConnectionStrings": {
    "DefaultConnection": "Server=prod-server; DataBase=SistemaSolicitudes; User Id=prod_user; Password=***; Encrypt=True;"
  },
  "Jwt": {
    "SecretKey": "USE_ENVIRONMENT_VARIABLE",
    "Issuer": "https://yourdomain.com",
    "Audience": "https://yourdomain.com"
  }
}

Publishing the Application

cd SolicitudesAPI
dotnet publish -c Release -o ./publish

Troubleshooting

Database connection failed

Error: Cannot open database "SistemaSolicitudes" requested by the loginSolutions:

Verify database name is exactly SistemaSolicitudes
Check SQL Server instance name in connection string
Ensure SQL Server is running: services.msc → SQL Server service
Test connection in SSMS with the same credentials
Verify firewall allows SQL Server connections (port 1433)

JWT token validation failed

Error: IDX10503: Signature validation failedSolutions:

Ensure Jwt:SecretKey is identical in both projects
Verify Issuer and Audience match exactly
Clear browser localStorage and re-login
Check token hasn’t expired (2 hour default)

CORS errors in browser console

Error: Access to fetch at '...' from origin '...' has been blocked by CORS policySolutions:

Verify CORS is enabled in Program.cs:62
Check frontend URL matches CORS policy
Ensure API is running before starting frontend
Verify UseCors("PermitirBlazor") is called before UseRouting()

QuestPDF license error

Error: QuestPDF license exceptionSolutions:

Verify QuestPDF.Settings.License = LicenseType.Community; in Program.cs:12
For commercial use, obtain proper license from QuestPDF
Ensure line is before any PDF generation code

Port already in use

Error: Unable to bind to https://localhost:7123 on the IPv4 loopback interface: 'Address already in use'Solutions:

Check if another instance is running

Find and kill the process using the port:

# Windows
netstat -ano | findstr :7123
taskkill /PID <process_id> /F

# Linux/Mac
lsof -i :7123
kill -9 <process_id>

Change the port in launchSettings.json

Frontend can't connect to API

Error: TypeError: Failed to fetch or Network errorSolutions:

Verify API is running on https://localhost:7123
Check Program.cs BaseAddress matches API URL
Accept the SSL certificate warning in browser
Check browser console for detailed errors
Verify firewall allows connections to localhost

Next Steps

Now that you have the application installed and running:

Quickstart Guide

Learn how to create your first transparency request

API Reference

Explore all available API endpoints

User Management

Set up roles and permissions

Security Guide

Secure your production deployment

Getting Help

If you encounter issues not covered in this guide:

Check the Troubleshooting section above
Review the application logs in the terminal output
Inspect browser console for frontend errors (F12)
Verify all prerequisites are correctly installed
Ensure database is properly imported and accessible

For development, it’s helpful to set "launchBrowser": true in both launchSettings.json files to automatically open the applications when starting.

Getting Started

Core Features

User Guide

Configuration

Overview

Prerequisites

Required Software

System Requirements

Step 1: Clone the Repository

Step 2: Database Setup

Step 3: Configure the API

Step 4: Configure the Frontend

Step 5: Run the Application

Step 6: Initial Configuration

Running with Visual Studio

Production Deployment

Environment-Specific Configuration

Publishing the Application

Troubleshooting

Next Steps

Quickstart Guide

API Reference

User Management

Security Guide

Getting Help

Build docs developers (and LLMs) love

Getting Started

Core Features

User Guide

Configuration

​Overview

​Prerequisites

​Required Software

​System Requirements

​Step 1: Clone the Repository

​Step 2: Database Setup

​Step 3: Configure the API

​Step 4: Configure the Frontend

​Step 5: Run the Application

​Step 6: Initial Configuration

​Running with Visual Studio

​Production Deployment

​Environment-Specific Configuration

​Publishing the Application

​Troubleshooting

​Next Steps

Quickstart Guide

API Reference

User Management

Security Guide

​Getting Help

Build docs developers (and LLMs) love

Overview

Prerequisites

Required Software

System Requirements

Step 1: Clone the Repository

Step 2: Database Setup

Step 3: Configure the API

Step 4: Configure the Frontend

Step 5: Run the Application

Step 6: Initial Configuration

Running with Visual Studio

Production Deployment

Environment-Specific Configuration

Publishing the Application

Troubleshooting

Next Steps

Getting Help