Open imukai opened 4 years ago
Are any plans of supporting the followings:
/// <summary>
/// Guids that cannot be converted
/// </summary>
/// <remarks>
/// Types of projects that are not supported:
/// https://github.com/dotnet/project-system/blob/master/docs/feature-comparison.md
/// The GUIDs taken from
/// https://www.codeproject.com/Reference/720512/List-of-Visual-Studio-Project-Type-GUIDs
/// Note that the list here is in upper case but project file guids are normally lower case
/// This list does not include Windows Forms apps, these have no type guid
/// </remarks>
private static readonly Guid[] unsupportedGuids =
{
Guid.ParseExact("8BB2217D-0F2D-49D1-97BC-3654ED321F3B", "D"), // ASP.NET 5
Guid.ParseExact("603C0E0B-DB56-11DC-BE95-000D561079B0", "D"), // ASP.NET MVC 1
Guid.ParseExact("F85E285D-A4E0-4152-9332-AB1D724D3325", "D"), // ASP.NET MVC 2
Guid.ParseExact("E53F8FEA-EAE0-44A6-8774-FFD645390401", "D"), // ASP.NET MVC 3
Guid.ParseExact("E3E379DF-F4C6-4180-9B81-6769533ABE47", "D"), // ASP.NET MVC 4
Guid.ParseExact("349C5851-65DF-11DA-9384-00065B846F21", "D"), // ASP.NET MVC 5
};
No plans, I don't think there's a need to keep adding to this since Microsoft has now released their conversion tool.
On Tue, Oct 19, 2021, 06:03 Orel Eraki @.***> wrote:
Are any plans of supporting the followings:
/// <summary> /// Guids that cannot be converted /// </summary> /// <remarks> /// Types of projects that are not supported: /// https://github.com/dotnet/project-system/blob/master/docs/feature-comparison.md /// The GUIDs taken from /// https://www.codeproject.com/Reference/720512/List-of-Visual-Studio-Project-Type-GUIDs /// Note that the list here is in upper case but project file guids are normally lower case /// This list does not include Windows Forms apps, these have no type guid /// </remarks> private static readonly Guid[] unsupportedGuids = { Guid.ParseExact("8BB2217D-0F2D-49D1-97BC-3654ED321F3B", "D"), // ASP.NET 5 Guid.ParseExact("603C0E0B-DB56-11DC-BE95-000D561079B0", "D"), // ASP.NET MVC 1 Guid.ParseExact("F85E285D-A4E0-4152-9332-AB1D724D3325", "D"), // ASP.NET MVC 2 Guid.ParseExact("E53F8FEA-EAE0-44A6-8774-FFD645390401", "D"), // ASP.NET MVC 3 Guid.ParseExact("E3E379DF-F4C6-4180-9B81-6769533ABE47", "D"), // ASP.NET MVC 4 Guid.ParseExact("349C5851-65DF-11DA-9384-00065B846F21", "D"), // ASP.NET MVC 5 };
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/hvanbakel/CsprojToVs2017/issues/274#issuecomment-946701212, or unsubscribe https://github.com/notifications/unsubscribe-auth/AA7QKPCY46D2AMT2L3YDELDUHVUB3ANCNFSM4KINGGHA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
Hi guys, just want to let you know that using the great CsprojToVs2017 tool it's easy to migrate your MVC projects to the great great MSBuild.SDK.SystemWeb Sdk style.
Just remove the
Just want to thank @CZEMacLeod for your great job on this one! It just works!
Then just replace the Sdk attribute with and voilà!
Replace the Sdk attribute with what?
Then just replace the Sdk attribute with and voilà!
Replace the Sdk attribute with what?
@zythra It says how to use the SDK in the project - https://github.com/CZEMacLeod/MSBuild.SDK.SystemWeb#how-can-i-use-these-sdks
<Project Sdk="MSBuild.SDK.SystemWeb/4.0.88">
I have an older vs 2015 project that I'm trying to get up to 2017 or 2019 and running into all sorts of problems in the migration process. I found this tool and was hopeful, but both the 2017 and 2019 versions are giving me the same message, that the project is unsupported.
[14:19:19 WRN] Unsupported project[XXXXX] type {8BB2217D-0F2D-49D1-97BC-3654ED321F3B} [14:19:19 INF] No projects have been found to match your criteria.
It is an older .NET Core 1.1 ASP.NET project. Is there a particular reason it is not supported? Can you think of any other options? VS2017 itself fails to migrate it because dotnet-migrate is no longer around.
Kind of at a loss right now.