Simple app for employer to track employees time cards for payroll use. Supports multiple employees over different projects.
Supports Dark theme.
screenshots | screenshots |
---|---|
![]() |
![]() |
![]() |
![]() |
2.0 Is not compatible with prior exported data. Same as in version 1.8, it is possible but requires edits to the csv files before importing the data.
1.8 Add version check during data Import, Prior exported data will not be allowed to be imported in. (It is possible with some edits to the csv files to make compatible. TimeClockApp/discussions Use the project discussions page and ask me for details if you need to do this)
Built using .NET 9.0.2 and the following nuget packages:
"CommunityToolkit.Maui" Version="11.1.0"
"CommunityToolkit.Mvvm" Version="8.4.0"
"Microsoft.Maui.Controls" Version="9.0.40"
"CsvHelper" Version="33.0.1"
"Microsoft.EntityFrameworkCore.Sqlite" Version="9.0.2"
To change the default items that are added during the database creation, see the file TimeClockApp.Shared\Models\DataBackendContext.cs
To change the name of the database file for creation, see the property 'sQLiteDbFileName' in file TimeClockApp\TimeClockApp.Shared\SQLiteSetting.cs
2.0
- Add invoice and Invoice detail pages
- bug fixes
- Removed unused code
- Fixed NumericValidationBehavior and TextValidationBehavior not working
- Better exception error logging with for async methods
1.8
- Moved ExpenseType from a Enum into a database table.
- Added EditExpenseTypePage.
- Auto add Expense entry for the amount paid out for payroll along with a entry for WorkersComp amount.
- Reorder the Shell Flyout menu.
- Add version check during data Import, Prior exported data will not be allowed to be imported in. (It is possible but the Expense.csv and Config.csv files would need edit to make compatible)
1.7
- minor bug fixes. Code cleanup.
- Fixed issue when deploying in Release mode to physical device, app would crash upon startup.
1.6
- Add ReportPage to view the total cost for a project, date range, per employee, etc.
- Fixed issue with PayrollDetail grouping.
- Moved FileService and SQLiteSetting class to TimeClockApp.Shared
- Removed the project TimeClockApp.FileHelper
1.4
- Fix issue with multiple timecards on the same day, that would not correctly add up the hours for overtime.
- Fix issue with double overtime (As per overtime in USA any work over 8 hours in a single day is overtime. After the 12th hour it is double overtime)
- Redesigned the payroll detail page.
- Fixed issue with the backup of the entire sqlite database file. Can only make a copy of current database. Still can not import that file. Only import via CVS files is supported
- Removed unnecessary Wages table from database
- Fixed issue of a timecard from a prior date that was not clocked out of.
- Now uses EF migrations to create and update the database. See migrations section below
- Database has been changed between v1 to v1.4. If you have any data you want to keep, before upgrading to version 1.4, backup your current data by using
Tools
->Backup
->Export Data
This will create a ZIP file containing all the SQLite table data in CSV files. Then after upgrading, useTools
->Backup
->Import Data
to restore your data.
1.0
- Initial Release
To create the initial migration files needed for the database. Requires the Entity Framework Core tools to be installed. .NET Core CLI tool was used during development, but either tool set will work.
- Test if Package Manager Console tools by open a PowerShell console and enter the command
Get-Help about_EntityFrameworkCore
- If you get a error message, test if .NET Core CLI tools in the same console, enter the following command
dotnet ef
- If that also gives a error, follow instructions at https://learn.microsoft.com/en-us/ef/core/cli/dotnet#installing-the-tools
- In Visual Studio 2022, Set the 'Solution Configuration' to
DebugMigrator
- Set the
EFMigrator
project as the 'Start up project' - Build the solution.
- Right click on the EFMigrator project and select
Open in Terminal
. - In the Console window (PowerShell or Command Prompt), enter the command
dotnet ef migrations add InitialCreate -c TimeClockApp.Shared.Models.DataBackendContext -p ..\TimeClockApp.Shared --configuration DebugMigrator --no-build --verbose
- After the command completes. Set the 'Solution Configuration' to
Debug
orRelease
- Set the
TimeClockApp
project as the 'Start up project'
- In Visual Studio 2022, Set the 'Solution Configuration' to
DebugMigrator
- Set the
EFMigrator
project as the 'Start up project' - View->Other Windows->Package Manager Console
- In the Package Manager Console window, set the 'Default project' to
TimeClockApp.Shared
- In the Package Manager Console, enter the command
add-migration Initial -Context TimeClockApp.Shared.Models.DataBackendContext -Verbose
- After the command completes. Set the 'Solution Configuration' to
Debug
orRelease
- Set the
TimeClockApp
project as the 'Start up project'
Thank you to @taublast for his guide on getting migrations to work with maui android projects. github.com/taublast/MauiEF