ASP.NET Culture Fix & Deployment
Budget: $250 – $750 CAD
I maintain an in-house ASP.NET 9 MVC application called “CeQueJaiLu”, built in Visual Studio 2022 and running happily on Windows with both HTTP and HTTPS. Under WSL 2, however, page titles insist on staying in English while every other element still switches correctly between French and English. The localisation is handled through AliasPPM_Localisation.dll and the usual culture-specific .resx files that sit in dedicated configuration folders, so nothing is hard-coded.
I need two things:
1. A precise fix for that title-only culture glitch in WSL 2. Once solved, titles must render in French or English exactly like the rest of the interface when I switch cultures.
2. Step-by-step coaching on publishing the site to my Linux host. The server has my database and is blank at the moment, so please guide me through choosing and configuring Nginx or Apache, installing the .NET runtime, running dotnet publish, setting up a reverse proxy, and wiring it all so that future deployments are painless.
Key stack details you may want to know while investigating:
• Microsoft.Office.Interop.Excel v16.0.18925.20022 for exports
• GleamTech.Document.Ultimate v7.8.7 for PDF viewing
• Pomelo.EntityFrameworkCore.MySql v9.0.0 for the MySQL layer
• X.PagedList.MVC.Core v10.5.9 for paging
Acceptance criteria
• Page titles respect the chosen culture under WSL 2 and on the final Linux host.
• I can deploy to the Linux box myself, reproduce the process, and understand the web-server setup you recommended.
I need two things:
1. A precise fix for that title-only culture glitch in WSL 2. Once solved, titles must render in French or English exactly like the rest of the interface when I switch cultures.
2. Step-by-step coaching on publishing the site to my Linux host. The server has my database and is blank at the moment, so please guide me through choosing and configuring Nginx or Apache, installing the .NET runtime, running dotnet publish, setting up a reverse proxy, and wiring it all so that future deployments are painless.
Key stack details you may want to know while investigating:
• Microsoft.Office.Interop.Excel v16.0.18925.20022 for exports
• GleamTech.Document.Ultimate v7.8.7 for PDF viewing
• Pomelo.EntityFrameworkCore.MySql v9.0.0 for the MySQL layer
• X.PagedList.MVC.Core v10.5.9 for paging
Acceptance criteria
• Page titles respect the chosen culture under WSL 2 and on the final Linux host.
• I can deploy to the Linux box myself, reproduce the process, and understand the web-server setup you recommended.
Related categories:
.NET
Linux
C# Programming
Apache
Nginx
ASP.NET
Web Development
ASP.NET MVC
Visual Studio