8e557b0b9d
bump AnalysisModeGlobalization to Recommended
...
fixes CA1304, CA1309, CA1310, CA1311
temporarily silences CA1305
reduce severity of CA2101
2023-08-14 14:18:45 -07:00
4c00ec54e7
Bump AnalysisLevel, remove legacy rules
2023-08-14 14:18:45 -07:00
65ffa3fc2e
Blindly update NuGet deps
...
temporarily disabled MA0020
2023-04-16 09:02:40 +10:00
eb6f2864ff
Only set `<PathMap/>` for Release builds
...
fixes 5dc385e22; also skip `SolutionDir` override if building projects
individually
2023-03-17 06:37:38 +10:00
5dc385e228
Set `<PathMap/>` so per-machine paths don't leak into build output
2023-03-16 12:39:26 +10:00
389fd5015f
s/ProjectDir/MSBuildProjectDirectory/ in MSBuild include files
...
I don't think anything was broken, this is just a precaution
2023-03-16 12:39:26 +10:00
38b5f16ccc
Refactor enable Roslyn Analyzers flag
...
kept the old name, but turns out `-p:RunAnalyzersDuringBuild=true` also works
...good thing the old name wasn't documented
2023-03-16 12:39:25 +10:00
c816400e54
Update schema in `.stylecop.json` to match package version
2023-03-16 12:39:21 +10:00
697c10e3e6
Enable MA0015 and fix noncompliance
...
"Specify the parameter name in ArgumentException"
needed to update package because this rule was broken until now
2022-07-22 03:51:46 +10:00
6b4e526a44
Actually run all the Analyzers for ext. tools, update Analyzers
...
fixes 6f372820a
2022-07-15 22:22:19 +10:00
6f372820a7
Allow C# 10 in satellite projects, enable Analyzers on ext. tools
2022-07-14 04:26:27 +10:00
6077bcf5af
Enable "strict" compiler flag and fix noncompliance
...
couldn't find official docs for this, but I got it from:
https://www.meziantou.net/csharp-compiler-strict-mode.htm
and it definitely does SOMETHING
2022-07-14 04:26:27 +10:00
a5fb4caad0
change languageversion back to 9.0 so we can use vs2019 and fix one related build error
2022-03-06 01:15:46 -05:00
1655c191e0
Bump LangVersion, move key name overrides to separate file
2022-02-14 01:51:42 +10:00
2d9651fa89
Revert "sayonara appveyor"
...
This reverts commit 3b9cfc7c50
2022-01-29 21:56:08 -08:00
3b9cfc7c50
sayonara appveyor
2022-01-29 18:55:51 -08:00
908d4519c5
Use <ContinuousIntegrationBuild/> prop
2021-11-15 18:19:15 +10:00
d04724b0d2
Allow non-string resources again
2021-07-01 11:04:32 +10:00
1f0e058ef5
Blindly update <PackageReference/>s
2021-06-21 12:13:42 +10:00
26eaa22be2
Update StyleCop, migrate FxCop to NetAnalyzers (built-in)
2021-04-04 14:15:22 +10:00
ef76d8510e
Cleanup project files
2021-01-18 09:26:51 +10:00
0093c16d79
Bump .NET SDK to 5.0.100, bump C# to 9.0
...
BizHawk.Tests executable needs to run in CI, but the 5.0 SDK image can't run
Core 3.1 apps somehow, so I bumped that too
2020-11-23 21:48:10 +10:00
f8e624befe
Create common property IsTargetingNetFramework
...
* if true, will add reference assemblies <PackageReference/>
* slightly less dumb <Move/>
2020-09-22 22:11:00 +10:00
17ff66c61b
Opt-in to .NET 5 SDK's extra static analysis, update Analyzer packages
...
the extra CSxxxx rules should be available for Framework too if using the new
SDK, I haven't tried
2020-08-29 00:51:34 +10:00
ebd9645c1e
Cleanup assembly attributes
...
We're not using this metadata for anything, except one [InternalsVisibleTo] for
unit tests, and a half-assed version check in EmuHawk.Program.
2020-08-01 11:56:30 +10:00
318c6a7994
Add an easy way to #define symbols when building
...
-p:MachineExtraCompilationFlag=SYMBOL_NAME
2020-06-30 14:44:39 +10:00
12227f4836
fix debugging on omnisharp
2020-05-28 06:50:54 -04:00
2b8c0edcc2
Reorganise *.props
2020-02-23 06:17:35 +10:00
46a4d8ffa9
Retargetting non-executable projects to .NET Standard ( #1801 )
...
* Retarget BizHawk.Emulation.* to .NET Standard 2.0
* Retarget BizHawk.Bizware.BizwareGL to .NET Standard 2.0
In practice this mostly involves moving classes to BizHawk.Client.EmuHawk.
2020-02-18 10:31:49 -06:00
ae795e1f96
we have to use AnyCpu in order for winforms designer to work
2020-01-27 21:44:40 -05:00
215de3c0c0
Make Roslyn Analyzers opt-in at compile-time ( resolves #1813 )
...
They are still run by the IDE at design-time. To opt-in, set the MSBuild
property MachineRunAnalyzersDuringBuild. From the command-line, you can do this
by adding `/p:MachineRunAnalyzersDuringBuild=true`.
2020-01-26 10:34:07 +10:00
14d088f907
Migrate remaining StyleCop config and enable StyleCop analyzer
2020-01-25 07:21:49 +10:00
3ae58fd9d6
Use SolutionDir to make relative paths absolute
...
No need for warning of relative paths in filename anymore
2020-01-24 04:59:27 +10:00
Morilli