Prerequisites
| Requirement | Minimum version | Notes |
|---|---|---|
| Windows | 10 (64-bit) | WPF requires Windows. WSL is not supported. |
| .NET 8 SDK | 8.0 | Included with Visual Studio 2022 17.8+. |
| Visual Studio 2022 | 17.x | Community edition is sufficient. |
| ”.NET desktop development” workload | — | Must be selected in the VS installer. |
You do not need to install SQLite separately. The
SQLitePCLRaw.core and System.Data.SQLite.EF6 NuGet packages bundle the native SQLite library and are restored automatically during the build.Setup steps
Verify the .NET desktop development workload
Open the Visual Studio Installer, select your Visual Studio 2022 installation, and click Modify.Under the Workloads tab, confirm that .NET desktop development is checked. This workload includes WPF tooling and the WPF designer.If it is not checked, select it and click Modify to install it before continuing.
Clone the repository
Open a terminal (PowerShell, Command Prompt, or Git Bash) and run:Replace
<repository-url> with the actual URL of the repository.Open the solution in Visual Studio
Double-click
AppAdministrativa.sln, or open Visual Studio 2022 and use File → Open → Project/Solution to locate and open the .sln file.Visual Studio will load the single-project solution and index the source files.Restore NuGet packages
NuGet packages are restored automatically the first time you build. You can also trigger a manual restore:This downloads
- Right-click the solution node in Solution Explorer and select Restore NuGet Packages, or
- Open a terminal in the solution directory and run:
SQLitePCLRaw.core 3.0.2 and System.Data.SQLite.EF6 2.0.3 from NuGet.Build and run the application
Press F5 to build and launch with the debugger attached, or Ctrl+F5 to launch without the debugger.Visual Studio compiles the project targeting
net8.0-windows and copies horarios.db to the output directory (bin\Debug\net8.0-windows\ or bin\Release\net8.0-windows\) as configured by the PreserveNewest copy rule.The application starts at the login window (MainWindow.xaml).What gets copied to the output directory
The project includeshorarios.db as a content file with the PreserveNewest copy strategy:
horarios.db is copied to the output directory automatically on every build, but only if it is newer than the copy already there. You do not need to manage this file manually.
No external configuration required
- No environment variables are needed.
- No external services or APIs are required.
- No database server is required — SQLite runs in-process.
- The application reads and writes all data locally.