beingfaisal/car-showroom-management-system

Purpose and Runtime

This is a Windows desktop Car Showroom Management System. It is a C# WinForms application targeting .NET Framework 4.7.2, built from CSM Project.sln and CSM Project/CSM Project.csproj. The deployed executable is CSM Project/bin/Release/CSM Project.exe.

Application Entry and Shell

Startup is defined by CSM Project/Program.cs, which launches the WinForms UI. CSM Project/Form1.cs is likely the initial sign-in form, based on compiled resource naming (LogInForm) and the README. Navigation is form-to-form rather than through a web/API layer.

Role-Based Workflow Boundary

The application distinguishes manager and salesman experiences. Compiled resource names identify manager, salesman, and login screens; the corresponding source is represented by the numbered WinForms forms:

• CSM Project/Form1.cs

• CSM Project/Form2.cs

• CSM Project/Form3.cs

• CSM Project/Form4.cs

Authentication determines which menu/control flow the user enters. The database must contain an initial manager account; managers subsequently administer employees.

Showroom Operations UI

Business operations are implemented directly in WinForms code-behind plus generated layout/resource files. The form set provides the primary functional modules for employee management, car management, and vehicle sales:

• CSM Project/Form5.cs

• CSM Project/Form6.cs

• CSM Project/Form7.cs

• CSM Project/Form8.cs

• CSM Project/Form9.cs

• CSM Project/Form10.cs

The absence of separate domain/service/data-access directories indicates that UI event handlers likely own validation, navigation, and SQL interaction.

Data Layer and Database Contract

SQL Server is the external persistence service. CSM Schema.sql is the authoritative database bootstrap contract and must be run before the application is connected. A typed ADO.NET dataset is included:

• CSM Project/CSMDataSet.xsd

• CSM Project/CSMDataSet.Designer.cs

Connection configuration is expected at the application boundary in CSM Project/App.config; local generated settings are under CSM Project/Properties/Settings.settings. Core flow is: user action in a form → direct database read/write via the connected application → refreshed UI/state.

Presentation and Shared UI Elements

Each form follows WinForms partial-class separation: behavior in .cs, generated controls/layout in .Designer.cs, and localized/embedded assets in .resx, for example CSM Project/Form1.Designer.cs and CSM Project/Form1.resx. Shared dialog and visual components include:

• CSM Project/CustomMsgBox.cs

• CSM Project/CustomSuccessBox.cs

• CSM Project/CircularPictureBox.cs

• CSM Project/LockBitmap.cs

These form the common feedback and image-rendering boundary used by operational screens.

Build Artifacts and Infrastructure

The application runs locally on Windows with the .NET Framework runtime and a reachable SQL Server instance. Build outputs are committed under CSM Project/bin/Debug and CSM Project/bin/Release; intermediate output is under CSM Project/obj. No server-side application, HTTP interface, cloud infrastructure, or test project is represented in the repository tree.