Skip to content

Commit

Permalink
Fixing hookgen csproj file so it works in visual studio builds
Browse files Browse the repository at this point in the history
I was running into errors with building hookgen from visual studio. From what I read, Visual Studio only supports building code analyzers if it is targeting netstandard2.0. It didn't seem to have an effect in builds from command line, so changing it to allow better build workflow when working from VS.
  • Loading branch information
jasminegamedev committed Mar 10, 2024
1 parent 076ee8b commit 8c1d346
Showing 1 changed file with 4 additions and 6 deletions.
10 changes: 4 additions & 6 deletions Celeste64.HookGen/Celeste64.HookGen.csproj
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
<Project Sdk="Microsoft.NET.Sdk">
<Project Sdk="Microsoft.NET.Sdk">
<PropertyGroup>
<TargetFramework>net8.0</TargetFramework>
<TargetFramework>netstandard2.0</TargetFramework>
<IsPackable>false</IsPackable>
<Nullable>enable</Nullable>
<LangVersion>latest</LangVersion>
Expand All @@ -17,9 +17,7 @@
<PrivateAssets>all</PrivateAssets>
<IncludeAssets>runtime; build; native; contentfiles; analyzers; buildtransitive</IncludeAssets>
</PackageReference>
<PackageReference Include="Microsoft.CodeAnalysis.CSharp" Version="4.3.0"/>
<PackageReference Include="Microsoft.CodeAnalysis.CSharp.Workspaces" Version="4.3.0"/>

<PackageReference Include="MonoMod.RuntimeDetour" Version="25.1.0-prerelease.2"/>
<PackageReference Include="Microsoft.CodeAnalysis.CSharp" Version="4.3.0"/>
<PackageReference Include="Microsoft.CodeAnalysis.CSharp.Workspaces" Version="4.3.0"/>
</ItemGroup>
</Project>

0 comments on commit 8c1d346

Please sign in to comment.