Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix build #1052

Closed
wants to merge 6 commits into from
Closed

fix build #1052

wants to merge 6 commits into from

Conversation

SimonCropp
Copy link
Member

No description provided.

@@ -1,7 +1,7 @@
<?xml version="1.0" encoding="utf-8"?>
<Project Sdk="Microsoft.NET.Sdk">
<PropertyGroup>
<TargetFrameworks>net48;net6.0</TargetFrameworks>
<TargetFrameworks>net48;net6</TargetFrameworks>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why are you switching to an unusual TFM? I've never seen net6 being used anywhere.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe to test a bad csproj setting?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's not necessarily bad since it builds fine. Also, he made that change in 20 projects 🙂

@SimonCropp
Copy link
Member Author

i stuffed up the main branch with my auto update stuff. so this is just to get a green build going again and gradually re make the changes.

basically nothing to see here for now

@@ -7,7 +7,7 @@
</PropertyGroup>
<ItemGroup>
<PackageReference Include="Microsoft.CodeAnalysis.Analyzers" Version="3.3.4" PrivateAssets="all" />
<PackageReference Include="Microsoft.CodeAnalysis.CSharp" Version="4.3.0" PrivateAssets="All" />
<PackageReference Include="Nullable.Extended.Analyzer" Version="1.15.6169" PrivateAssets="all" />
<PackageReference Include="Microsoft.CodeAnalysis.CSharp" Version="4.8.0" PrivateAssets="All" />
Copy link
Member

@ltrzesniewski ltrzesniewski Apr 15, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh, I didn't notice this earlier, but I think the Microsoft.CodeAnalysis.CSharp package should be rolled back to v4.0.1 and frozen at that version unless there's a good reason to use a newer one, since referencing a newer version requires the user to have a .NET SDK or Visual Studio version which supports it. See here for the version map.

The problem is that it won't play along with tools which always suggest to bump the packages to the latest versions. 😞

@SimonCropp SimonCropp closed this Aug 10, 2024
@SimonCropp SimonCropp deleted the fix-build branch August 11, 2024 00:00
@SimonCropp SimonCropp restored the fix-build branch August 15, 2024 23:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants