How to migrate an sfproj (Service Fabric Project) to .netcore project (.csproj)? Can you provide some guidance for the migration path?

Jose Nelson Falavinha Junior 0 Reputation points Microsoft Employee
2025-09-19T19:15:40.9733333+00:00

How to migrate an sfproj (Service Fabric Project) to .netcore project (.csproj)? Can you provide some guidance for the migration path?

Developer technologies | Visual Studio | Other
Developer technologies | Visual Studio | Other
A family of Microsoft suites of integrated development tools for building applications for Windows, the web, mobile devices and many other platforms. Miscellaneous topics that do not fit into specific categories.
{count} votes

1 answer

Sort by: Most helpful
  1. Sina Salam 24,816 Reputation points Volunteer Moderator
    2025-09-20T15:03:42.74+00:00

    Hello Jose Nelson Falavinha Junior,

    Welcome to the Microsoft Q&A and thank you for posting your questions here.

    I understand that you would like to migrate an sfproj (Service Fabric Project) to .netcore project (.csproj) and need some guides.

    The high level steps as a best advice are:

    • Step 1: Migrate Service Projects to SDK-style .csproj
      • You must use Visual Studio or msbuild for building and packaging the application.
      • Repeat for each service project.
      • Update code for .NET Core compatibility (e.g., config files, deprecated APIs).
    • Step 2: Recreate the Application Project
      • The .sfproj is Deprecated
      • Create a New Application Project
    • Step 3: Update Deployment and Build
    • Step 4: Test Everything

    Possibly rewrite your code, don't use .net upgrade assistance, it messes up my apps without reverse.

    Also, as a Microsoft Employee use your Copilot at every stage to validate the code. So, in a nutshell note the following:

    1. You cannot migrate the .sfproj to SDK-style .csproj; only service projects can be migrated.
    2. .NET 8 LTSC is not fully supported for Service Fabric.
    3. Build and deployment must use Visual Studio or MSBuild, not dotnet build.
    4. Update manifests and test thoroughly.

    I hope this is helpful! Do not hesitate to let me know if you have any other questions or clarifications.


    Please don't forget to close up the thread here by upvoting and accept it as an answer if it is helpful.

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.