Professional Case Study
Purchasing Management Application
Modernizing a legacy Microsoft Access purchasing application as a Blazor Server business system for manufacturing operations.
Back to Professional WorkOverview
The application supports purchasing work including purchase requests, purchase orders, vendors, quote attachments, status tracking, printable documents and reporting.
Business Problem
The established purchasing workflow depended on a legacy Microsoft Access application. The required purchasing functions needed to be carried into a maintainable web application while continuing to support day-to-day operations.
My Role
My personal contribution as a .NET Developer included migrating the legacy purchasing application to Blazor Server, implementing and maintaining application functionality, supporting its shared ERP integration and helping with production release and ongoing support. This case study does not attribute broader organizational decisions or work by other contributors to me.
Solution
The purchasing workflow was rebuilt as an ASP.NET Core and Blazor Server application backed by SQL Server. The solution brought related purchasing functions into one web application while retaining the operational coverage identified for the legacy system.
Technology
- C#
- ASP.NET Core
- Blazor Server
- SQL Server
- Entity Framework Core
- Syncfusion
Architecture / Approach
At a public-safe level, the system uses a Blazor Server user interface hosted through ASP.NET Core, Entity Framework Core for application data access and SQL Server for persistence. It also works with shared ERP functionality used by internal manufacturing applications.
Important Challenges
The work required translating established Access workflows into a web application, coordinating connected purchasing areas such as vendors, quotations, documents and reporting, and supporting the transition without publishing proprietary rules or internal data.
Production / Operations
I supported the production release and continue to maintain the application. That work includes investigating functional, performance and production issues and coordinating application changes, deployments and SQL execution when required.
Outcome
The legacy purchasing application was migrated to Blazor Server and released to production, where it continues to support the approved purchasing workflows. No numerical performance, savings or usage outcome is claimed publicly.
Confidentiality
This is a private internal business system. Real screenshots, source code, schemas, company data, documents, identifiers, server details and proprietary business rules are not published. Any visual used publicly is synthetic and contains invented data.