Phase 1 & 2: Migrate SampleMvcWebApp from .NET Framework 4.5.1 to .NET Core 6

[devin-ai-integration]

Phase 1 & 2: Migrate SampleMvcWebApp from .NET Framework 4.5.1 to .NET Core 6

Summary

This PR completes Phase 1 (project structure migration) and Phase 2 (core framework dependencies) of migrating the SampleMvcWebApp from .NET Framework 4.5.1 to .NET Core 6. All 5 projects have been converted to modern SDK-style format with updated dependencies, but the application is not yet functional due to remaining controller and DI migration work.

Key Changes:

• Project Structure: Converted all projects (.csproj files) to SDK-style format targeting net6.0
• Package Management: Migrated from packages.config to PackageReference format
• Core Dependencies: Updated ASP.NET MVC 5.2.3 → ASP.NET Core 6.0, Entity Framework 6.1.3 → EF Core 6.0, AutoMapper to latest version
• ASP.NET Core Setup: Created Program.cs and appsettings.json files for modern ASP.NET Core configuration
• Cleanup: Removed old AssemblyInfo.cs files and packages.config files (now handled automatically by SDK)
• DI Preparation: Commented out Autofac dependencies in preparation for ASP.NET Core built-in DI migration

Review & Testing Checklist for Human

⚠️ WARNING: Application currently does not compile due to incomplete migration

• Verify Project Structure: Check that all .csproj files correctly reference modern packages and target net6.0
• Package Compatibility Review: Many packages show NU1701 warnings - verify GenericServices, DelegateDecompiler, and other legacy packages are compatible with .NET Core 6
• Build Status: Confirm the current build failures (144+ errors) are expected and related to missing controller/MVC migration
• Database Configuration: Verify the connection string format in appsettings.json matches your LocalDB setup
• Plan Phase 3: Review what still needs to be done - controller migration, DI setup, GenericServices compatibility resolution

Test Plan

1. Do NOT attempt to run the application - it will fail due to incomplete migration
2. Try dotnet build to confirm the expected compilation errors related to missing ASP.NET Core using statements
3. Review compatibility warnings for legacy packages, especially GenericServices framework
4. Verify project references and dependencies are correctly configured

Notes

• GenericServices Compatibility Issue: The GenericServices 1.0.9 framework shows .NET Framework compatibility warnings and may need to be replaced or updated for .NET Core 6 compatibility
• Next Phase Required: Controllers still use System.Web.Mvc types and need migration to Microsoft.AspNetCore.Mvc
• DI Migration Pending: Autofac setup is commented out but ASP.NET Core DI registration is not yet implemented

Link to Devin run: https://app.devin.ai/sessions/8b216f360a444fec8664341a4c6ee0e8
Requested by: @ben-windsurf

[devin-ai-integration]

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

• Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
• Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

• Disable automatic comment and CI monitoring

[ben-windsurf]

@devin add these changes to the ReadMe