Replies: 4 comments
-
Hi @janseris, There are a couple of options listed below
<Project Sdk="Microsoft.NET.Sdk">
<PropertyGroup>
<TargetFrameworks>net6.0;net48</TargetFrameworks>
<Description>Sample project that targets multiple TFMs</Description>
</PropertyGroup>
</Project>
Hope that helps. |
Beta Was this translation helpful? Give feedback.
-
But why is the warning dependent on just having different style of csproj? |
Beta Was this translation helpful? Give feedback.
-
I have no idea. But if you want to have both .net framework and .net core projects, you either multi-target or use .netstandard 2.0. You might have better luck getting a more in-depth answer on https://stackoverflow.com/ |
Beta Was this translation helpful? Give feedback.
-
I am going to convert this issue to a discussion for further conversation, but I agree with @elachlan that your best bet might be another forum. |
Beta Was this translation helpful? Give feedback.
-
.NET version
8.0.1
Did it work in .NET Framework?
Not tested/verified
Did it work in any of the earlier releases of .NET Core or .NET 5+?
No response
Issue description
How is WinForms NET Core -> NET Framework intended to work?
I noticed that when I create old csproj style WinForms, Visual Studio does not report any warnings
When I switch to new csproj and change target framework moniker to .NET Framework 4.8, I start receiving warning which afaik cannot be disabled.
Using new csproj structure allows me to use Sync Namespaces feature in Visual Studio which is very important in large projects.
Why is that? Is it supposed to be there?
Steps to reproduce
https://github.com/janseris/WinFormsCsProjNewOldTest
Beta Was this translation helpful? Give feedback.
All reactions