Prevent it from trying to upgrade .NET 4+ MVC projects

[nazjunaid]

The tools upgrades .NET MVC projects which are not compatible from what I understand with the 2017 csproj format. Maybe it shouldn't let you do this?

[hvanbakel]

Can you give an example of a project file and the specific section that it should look for?

…

On Thu, Aug 24, 2017 at 8:21 AM, Nazmul Junaid ***@***.***> wrote: The tools upgrades .NET MVC projects which are not compatible from what I understand with the 2017 csproj format. Maybe it shouldn't let you do this? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#21>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AD8FPNyRsn1zr7-QOxkA8t9Lp4UE4cNcks5sbZUFgaJpZM4PBiK1> .

[nazjunaid]

I believe it's related to

dotnet/aspnetcore#1978 and dotnet/sdk#491

It messes up on nested types liek Gobal.asax and Webconfig transforms you can detect them for looking for the DependentUpon attribute

[hvanbakel]

@nazjunaid if you can give me something to work/test with, that would be extremely helpful

[morindo]

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 {349c5851-65df-11da-9384-00065b846f21};{fae04ec0-301f-11d3-bf4b-00c04f79efbc} from your csproj, it will then act as default project type (Class Library), you will then be able to migrate your project to using the command dotnet migrate-2019 wizard "D:\Path\To\My\TestProject.csproj". Then just replace the Sdk attribute with and voilà!

Just want to thank @CZEMacLeod for your great job on this one! It just works!