ASP.NET Application upgrade to newer version of Visual Studio

Sourabh Agrawal 41 Reputation points

Hi Folks,
I have an application that was built using Visual Studio 2010 around 10 years back, now I am trying to upgrade the application so that I can use Visual Studio 2019, but when I try to open the application it won't load, it says that it is incompatible.

When I try and look into the error the error does not point me in any good direction to determine what the real issue is.
I am assuming this might be because the application was built using MVC 1 (But that is just an assumption)

Below is the error:

CMS.Web\CMS.Web.csproj: The application which this project type is based on was not found. Please try this link for further information:

I would really appreciate any kind of help.
Please advise.

A set of technologies in the .NET Framework for building web applications and XML web services.
3,364 questions
An object-oriented and type-safe programming language that has its roots in the C family of languages and includes support for component-oriented programming.
10,483 questions
0 comments No comments
{count} votes

Accepted answer
  1. Lan Huang-MSFT 27,796 Reputation points Microsoft Vendor

    Hi @Sourabh Agrawal ,
    You can refer to the documentation for Visual Studio Project Migration and Upgrade Reference.
    Upgrading MVC versions:
    For information about how to automatically upgrade from MVC 2 to MVC 3, see ASP.NET MVC 3 Application Upgrader.
    For information about how to manually upgrade from MVC 2 to MVC 3, see Upgrading an ASP.NET MVC 2 Project to ASP.NET MVC 3 Tools Update.
    For information about how to manually upgrade from MVC3 to MVC 4, see Upgrading an ASP.NET MVC 3 Project to ASP.NET MVC 4. If your project targets .NET Framework 3.5 SP1, you must retarget it to use .NET Framework 4.
    For information about how to manually upgrade from MVC 4 to MVC 5, see How to Upgrade an ASP.NET MVC 4 and Web API Project to ASP.NET MVC 5 and Web API 2.

    I suggest you create a new MVC5 application, reference MVC via Nuget etc and extract the code as needed. This will give you a chance to rebuild things and learn newer methods that you might otherwise struggle with MVC configuration and references.

    Best regards,
    Lan Huang

    If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments No comments

1 additional answer

Sort by: Most helpful
  1. Bruce ( 59,051 Reputation points

    you are correct, MVC 1 project types are no longer supported. You probably want to upgrade to .net 4.8, MVC 5

    there was a vs2010 utility to upgrade MVC 1 (vs 2008) to MVC 2 (vs 2010). manual:

    then then MVC 2 to MVC 3. From 3 to 4. from 4 to 5 is only minor edits.

    most of the changes are in the project file and nuget package versions. MVC went from gac install, to a library in the bin, to a nuget package.

    it may be easier to create a new empty MVC 5 (.net 48) project and add the old files and work thru the compile issues.