Failed to convert project to SDK Style.

[gulshanmudgal]

EventLog.csproj is an unsupported project type. Not all project type guids are supported.
All supported project type guids:
f184b08f-c81c-45f6-a57f-5abd9991f28f
fae04ec0-301f-11d3-bf4b-00c04f79efbc
60dc8134-eba5-43b8-bcc9-bb4bc16c2548
All given project type guids:
{3AC096D0-A1C2-E12C-1390-A8335801FDAB}
{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}
[15:40:44 WRN] No projects were converted to SDK style
[15:41:00 FTL] Conversion with try-convert failed.

We are migrating our application to .NET 6 from .NET 4.7. Most of the projects got migrated to .NET 6 but, few are failing with the above error.
Upgrade-Assistant version: 0.4.336902+3a2177acaa53d719e5da4ccde275f84ff18f0611
Please provide a workaround. Can we forcefully convert the project to SDK Style or manually? If manually, How?

[brandonh-msft]

What project type is EventLog.csproj?

[gulshanmudgal]

It’s WPF app, and EventLog is a class library.

[gulshanmudgal]

@brandonh-msft require your help.

Thanks.

[Lancelotbronner]

I had the same issue with test projects:

Example.Tests.csproj is an unsupported project type. Not all project type guids are supported.
All supported project type guids:
        f184b08f-c81c-45f6-a57f-5abd9991f28f
        fae04ec0-301f-11d3-bf4b-00c04f79efbc
        60dc8134-eba5-43b8-bcc9-bb4bc16c2548
All given project type guids:
        {3AC096D0-A1C2-E12C-1390-A8335801FDAB}
        {FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}

[GitHubThomas]

I have exactly the same problem with test projects. Trying to upgrade an complex wpf app from 4.7 (Framework) to .Net 7.
Has anyone found a solution?

[icnocop]

A work-around is to remove the unsupported project type GUID.

For example, edit the project file and change:
<ProjectTypeGuids>{3AC096D0-A1C2-E12C-1390-A8335801FDAB};{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}</ProjectTypeGuids>
to
<ProjectTypeGuids>{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}</ProjectTypeGuids>

[icnocop]

For some projects I had to edit the project file and add:
<Import Project="$(MSBuildToolsPath)\Microsoft.CSharp.targets" />

[Obishawn]

I had one unit test project succeed but two fail with this same error. I compared the original project files for differences and subsequently made the following changes. Then the upgrade completed successfully on those two projects.

In the first PropertyGroup element:

1. Removed:

    <ProductVersion></ProductVersion>
    <SchemaVersion>2.0</SchemaVersion>

2. Replaced:

    <PublishUrl>publish\</PublishUrl>
    <Install>true</Install>
    <InstallFrom>Disk</InstallFrom>
    <UpdateEnabled>false</UpdateEnabled>
    <UpdateMode>Foreground</UpdateMode>
    <UpdateInterval>7</UpdateInterval>
    <UpdateIntervalUnits>Days</UpdateIntervalUnits>
    <UpdatePeriodically>false</UpdatePeriodically>
    <UpdateRequired>false</UpdateRequired>
    <MapFileExtensions>true</MapFileExtensions>
    <ApplicationRevision>0</ApplicationRevision>
    <ApplicationVersion>1.0.0.%2a</ApplicationVersion>
    <IsWebBootstrapper>false</IsWebBootstrapper>
    <UseApplicationTrust>false</UseApplicationTrust>
    <BootstrapperEnabled>true</BootstrapperEnabled>
    <TargetFrameworkProfile />
    <NuGetPackageImportStamp>
    </NuGetPackageImportStamp>

With this:

    <VisualStudioVersion Condition="'$(VisualStudioVersion)' == ''">10.0</VisualStudioVersion>
    <VSToolsPath Condition="'$(VSToolsPath)' == ''">$(MSBuildExtensionsPath32)\Microsoft\VisualStudio\v$(VisualStudioVersion)</VSToolsPath>
    <ReferencePath>$(ProgramFiles)\Common Files\microsoft shared\VSTT\$(VisualStudioVersion)\UITestExtensionPackages</ReferencePath>
    <IsCodedUITest>False</IsCodedUITest>
    <TestProjectType>UnitTest</TestProjectType>
    <TargetFrameworkProfile />
    <NuGetPackageImportStamp>
    </NuGetPackageImportStamp>