Welcome to the repository for the Financial Management Tracker Application. This repository is a sample project used for exploring Blazor and, eventually, MAUI. You can find the project description, requirements, and other information below. If you are here while this project is in development, feel free to join us on Twitch where we are streaming the progress. I also post the videos to YouTube channel. Enjoy!

The Financial Management Tracker is an application that allows us to track financial events related to various accounts and services.

1. Clone the repo.

2. Set the FinanMan.Database.Migrations as the startup project
3. (Optional) Set the connection strings in Secrets for the the Migrations to point to your database (the app is currently configured to use SQLServer, and it default to use localdb).

{
  "ConnectionStrings":
  {
    "DefaultConnection": "Server=.;Database=FinancialManagement;Trusted_Connection=True;MultipleActiveResultSets=true;TrustServerCertificate=true"
  }
}

4. Perform the database update using either dotnet CLI or Package. (see Microsoft Docs for information on how to run an update.
5. Choose your application type by setting the project as the startup project a. Blazor WASM: FinanMan.Server project b. Blazor Server: FinanMan.ServerOnly c. Android, iOS, Mac, Tizen, Windows: FinanMan.Maui + Choose the correct run target. This may also require extra configuration d. Windows: FinanMan.Wpf

-- TODO

The Financial Management Tracker application should be able to:

• Allow users to track various financial accounts and the transactions and balances
• Allow users to set up recurring debits/credits
• Display information about financial events
• Provide analysis on spending habits
• Display futures in charts and data table formats

At the moment, we are not planning on giving the application direct access to the financial accounts. Also, the application should have its own user store setup on the machine the application is running on. Eventually, we may add functionality for the user to use a cloud service to store their data.

Below are some choices we made for starting the project. Please note that these are subject to change as we dive into the project.

• Database: SQL (most likely SQLite) using EntityFrameworkCore as the ORM
• Language and SDK: C# and Razor using the latest .NET SDK (.NET 6 at the time of this writing, but I'm sure we will upgrade it to .NET 7 when it comes out)
• Web Technology/Project Type: Blazor Server and Blazor WASM with a Shared UI and Server Services, and separate Client-side service implements
• UI Frameworks: We decided to remove all third-party css libraries and are planning on not using third-party Blazor Component Libraries