I’m always forgetting what they mean and how to use them.
There’s a great answer at: https://unix.stackexchange.com/a/3587/223606
For me, the important parts are:
The standard sections of the manual include:
1 User Commands
2 System Calls
3 C Library Functions
4 Devices and Special Files
5 File Formats and Conventions
6 Games et. al.
8 System Administration tools and Daemons
Distributions customize the manual section to their specifics,
which often include additional sections.
And the syntax:
$ man 1 printf
$ man 3 printf
$ man -a printf
Normally, when you invoke the MSBuild task to build a solution file, you can just add TARGETS=”ProjectName”, where ProjectName is just the name of the project, and don’t include the .csproj extension.
I already knew that if your project name includes a period, you need to replace that with an underscore (so the project “MySite.Web” becomes “MySite_Web”).
But the UnitTests project kept coming up as not a known build target name.
Finally, I found my answer in a comment in the answer to “specify project file of a solution using msbuild” on Stack Overflow.
Turns out that when a project appears in a solution folder (as opposed to just being in a directory), you need to include the name of the solution folder, and a backslash. So since the UnitTests project is in the UnitTests solution folder, the MSBuild invocation ends up looking like this:
Properties="Configuration=Release; Platform=Any CPU; OutDir=$(OutputFolder)Assemblies\; WarningLevel=0;"