Maintain .NET Document Management System
Budget / SalaryHourly project
TypeFreelance project
LocationRemote
Posted2 weeks ago
Our in-house created document control software has been running smoothly on a C#/.NET stack, MS SQL Server, and AWS for several years, but the developer who built and nurtured it is leaving. I need someone who can step in right away, understand the codebase, and keep the software/application stable and performant.
This web application targets .NET Framework 4.8 using ASP.NET MVC 4 (System.Web.Mvc 4.0.20505.0), with Razor 2.0 and WebPages 2.0. Supporting services are also on .NET 4.5 and .NET 4.0.
Key aspects of the application:
1. It’s effectively built on ASP.NET MVC without Web API usage.
2. The system runs on AWS (Sydney): one EC2 instance for IIS/web server handling documents stored locally and managing mail queue services, while another EC2 instance manages self-hosted SQL Server.
3. Deployment is manual (Visual Studio file copy to IIS) with no pipeline, containerization, or CI/CD implementation.
4. Entity Framework used is database-first EDMX model with ObjectContext API targeting SQL Server 2008-level T-SQL.
5. There’s minimal logging or monitoring configured—no external libraries currently integrated for this purpose.
6. Areas needing attention include large controller files with business logic embedded (e.g., a single controller has over 4,700 lines), performance shortfalls (e.g., synchronous actions, N+1 queries), outdated dependencies, improper error handling (e.g., silent exception swallowing in certain functionalities), configuration mismatches like maxRequestLength versus IIS upload cap, plain-text storage of SMTP credentials in Web.config (to be rotated during handover), and security concerns like using sa for database connections.
7. External dependency exists with Muhimbi PDF conversion service integration.
Deliverables include:
• Resolving all immediate stability bugs
• Suggesting prioritized improvements to system maintainability
• Improving performance bottlenecks such as asynchronous patterns or query efficiency where applicable
• Weekly summaries of accomplished tasks, risks spotted, and recommendations moving forward.
The Git repository, SQL scripts, and complete walkthrough by the outgoing developer will be provided during onboarding.
This web application targets .NET Framework 4.8 using ASP.NET MVC 4 (System.Web.Mvc 4.0.20505.0), with Razor 2.0 and WebPages 2.0. Supporting services are also on .NET 4.5 and .NET 4.0.
Key aspects of the application:
1. It’s effectively built on ASP.NET MVC without Web API usage.
2. The system runs on AWS (Sydney): one EC2 instance for IIS/web server handling documents stored locally and managing mail queue services, while another EC2 instance manages self-hosted SQL Server.
3. Deployment is manual (Visual Studio file copy to IIS) with no pipeline, containerization, or CI/CD implementation.
4. Entity Framework used is database-first EDMX model with ObjectContext API targeting SQL Server 2008-level T-SQL.
5. There’s minimal logging or monitoring configured—no external libraries currently integrated for this purpose.
6. Areas needing attention include large controller files with business logic embedded (e.g., a single controller has over 4,700 lines), performance shortfalls (e.g., synchronous actions, N+1 queries), outdated dependencies, improper error handling (e.g., silent exception swallowing in certain functionalities), configuration mismatches like maxRequestLength versus IIS upload cap, plain-text storage of SMTP credentials in Web.config (to be rotated during handover), and security concerns like using sa for database connections.
7. External dependency exists with Muhimbi PDF conversion service integration.
Deliverables include:
• Resolving all immediate stability bugs
• Suggesting prioritized improvements to system maintainability
• Improving performance bottlenecks such as asynchronous patterns or query efficiency where applicable
• Weekly summaries of accomplished tasks, risks spotted, and recommendations moving forward.
The Git repository, SQL scripts, and complete walkthrough by the outgoing developer will be provided during onboarding.
Apply on Freelancer →
Project sourced from Freelancer.com. Applications happen directly on the original platform — we never collect your data.