btcpayserver/Build/Common.csproj

<Project>
  <PropertyGroup>
    <TargetFramework>net8.0</TargetFramework>
    <TargetFramework Condition="'$(TargetFrameworkOverride)' != ''">$(TargetFrameworkOverride)</TargetFramework>
	<NoWarn>$(NoWarn),NU1701,CA1816,CA1308,CA1810,CA2208,CA1303,CA2000,CA2016,CA1835,CA2249,CA9998,CA1704;CS8981</NoWarn>
    <LangVersion>12.0</LangVersion>
    <EnableNETAnalyzers>True</EnableNETAnalyzers>
    <AnalysisLevel>6.0</AnalysisLevel>
  </PropertyGroup>

  <PropertyGroup>
    <Configurations>Debug;Release</Configurations>
    <Platforms>AnyCPU</Platforms>
  </PropertyGroup>
</Project>
Extract version in separate csproj to have better dockerfile caching 2019-06-02 17:33:35 +09:00			`<Project>`
			`<PropertyGroup>`
Bump .NET 8.0 (#5479) 2023-11-21 14:11:17 +09:00			`<TargetFramework>net8.0</TargetFramework>`
Prepare BTCPayServer.Common and BTCPayServer.Rating for .netcore 3.0 2019-10-03 16:13:12 +09:00			`<TargetFramework Condition="'$(TargetFrameworkOverride)' != ''">$(TargetFrameworkOverride)</TargetFramework>`
Fix warnings (#5517) Co-authored-by: Dennis Reimann <mail@dennisreimann.de> 2023-11-28 23:20:03 +09:00			`<NoWarn>$(NoWarn),NU1701,CA1816,CA1308,CA1810,CA2208,CA1303,CA2000,CA2016,CA1835,CA2249,CA9998,CA1704;CS8981</NoWarn>`
Use Mempoolspace fees (#5490) * Use Mempoolspace fees Since bitcoind's fee estiomates are horrible, I would use an altenrative, but that adds a third party to the mix. We can either: * Accept the risk (it is only for fee estimation anyway) * Offer a toggle in the server settings * Move this code to a plugin * refactor * Refactor --------- Co-authored-by: nicolas.dorier <nicolas.dorier@gmail.com> 2023-11-28 10:26:35 +01:00			`<LangVersion>12.0</LangVersion>`
Code analysis (#4293) * Enable NETAnalyzers for whole project - remove obsolete analyzers so that the .NET Core SDK NETAnalyzers can be used - enable NETAnalyzers for all projects so that developers can use them by defining the AnalysisMode on individual projects This is because if we set AnalysisMode to minimal, recommended or all it would spam with warning. The idea is to be able to turn them on during development to fix recommended stuff without polluting the build output. Following commits will implement some of the Code Analysis findings * Performance hints for using char overloads for single characters (CA1834 and CA1847) CA1834: Use StringBuilder.Append(char) for single character strings CA1847: Use string.Contains(char) instead of string.Contains(string) with single characters 2022-11-20 09:42:36 +01:00			`<EnableNETAnalyzers>True</EnableNETAnalyzers>`
			`<AnalysisLevel>6.0</AnalysisLevel>`
Extract version in separate csproj to have better dockerfile caching 2019-06-02 17:33:35 +09:00			`</PropertyGroup>`
Add Altcoins-Release and Altcoins-Debug configurations 2020-07-29 18:55:28 +09:00
			`<PropertyGroup>`
Removal of the Altcoins build (#6177) * Remove some useless #if ALTCOINS * Removal of the Altcoins build 2024-08-30 08:34:23 +09:00			`<Configurations>Debug;Release</Configurations>`
Add Altcoins-Release and Altcoins-Debug configurations 2020-07-29 18:55:28 +09:00			`<Platforms>AnyCPU</Platforms>`
			`</PropertyGroup>`
Extract version in separate csproj to have better dockerfile caching 2019-06-02 17:33:35 +09:00			`</Project>`