MonoGame 3.8 Release

Update master

Fix Missing Android Package

3.8.1

Fix cake script for 3.8.1 auto release

3.8.1 HOTFIX

* Point to that Patreon page.

* Use Patreon tag

I needed to take some extra steps for this documentation to work.

Documenting for future users' benefit.

… prevent large quantities of Warning CA1416 when targeting an API earlier than 31 on Android

…ion nomenclature

Accounts for new sdl nomenclature in sdl version checks

* The [ that was inside the url was removed.
* In minimal installations of Ubuntu curl is not installed, which is used internally in the script.

… height of the property grid. (MonoGame#8015)

…eader.

After reading the docs, it appears that the default value on the actual `EnvironmentMapEffect` side is intended to be 1. Making the writer default to the same value seems like a good choice. I also tweaked the comment because the way it is written, something in the documentation is interpreting that as a numbered list when it is just the end of a sentence.

…Game#8019)

… point. (MonoGame#8007)

* Fixes a bug in the `CalculateNormals` method that chooses the wrong normals for each point.

* Removes a stray using directive that shouldn't have gotten in there.

…loading and project reference adding to other solutions. (MonoGame#7963)

…ity (MonoGame#7966)

[MGCB Task] Fix tabs instead of spaces

The same thing as MonoGame#7856 is carried over to INDEX.md

MonoGame#7856

Minor spelling correction for INDEX.md and README.md - Change "succesfully" to "successfully"

Co-authored-by: NylonLogic1355 <114670430+NylonLogic1355@users.noreply.github.com>

…onoGame#7974)

Based on MonoGame#7089 and MonoGame#6144 I made changes to use SharpDX and NVorbis with Nuget

…8022)

This reverts commit 155e8ea.

…y ensuring a null terminator is appended to the end of `title`. (MonoGame#8051)

* Correct spelling of word contains in the source code comment summary of the GamePadTriggers class

* Correct more typos in source code comments related to input

* Correct spelling typo in log message related to a GL Exception in AndroidGameView

…n NuGets When Packed (MonoGame#8049)

* Added `GenerateDocumentationFile` so XML file is generated for NuGets when packed

* Restore whitespaces to reduce deletion count in file diff

Restored whitespace from original file as requested so the changes of adding GenerateDocumentationFile are the only changes that should show

* Corrected Whitespace To Reduce Deletion Count In Diff

Corrected the the additional final line extra whitespace so that the deletion count in diff is correct and the diff only shows the addition of the `GeneratedDocumentationFile` element.

…or message is shown. Resolves issue MonoGame#8054 (MonoGame#8055)

…tomatically (MonoGame#8046)

It occurs when the namespace of the entry point class is not the same as
the name of the entry assembly.
This is also the case for the top-level statements, which generates an
entry point class with no namespace.

Changed to use the name of the entry assembly for the resource name of
Icon.bmp.

Also changed to use Type.Assembly for the fall back case, which is the
recommended way when available instead of
Assembly.GetExecutingAssembly().

…bar (MonoGame#8036)

* Added `<LogicalName>` tag to `<EmbeddedResource>` tags so icons would display properly in game window title bar and task bar

* Empty commit to test github actions

Dotnet new --install is now deprecated.

…Game#8071)

* Updated image to show current workloads where mobile now shows MAUI instead of Xamarian

* Moved prior version information into a more visial Alert box

* Adjusted paragraph to be more verbose and include Note alert about visual studio editions

* Changed WHen to When

* Adjusted workload list to use nested bullets and group by mandatory vs optional

* Information about needing DirectX runtime moved inside an Important alert box to visually draw attention.

* Updated Extension Manager image to reflect the current 3.8.1.303 version

* Specify MonoGame projects

* Specify the full name of the extension and put it in bold

* Updated steps to install extension to be more verbose for new users not familar with installing Visual Studio
extensions

* `any` changed to `either`

* Removed redundent information concerning Visual Studio versions

* Removed alert about Visual Studio 2022 requirement. Tempaltes are not avaialble on prior versions and not supported so 2022 version is implied.

* Added Issue templates

* Fixed small grammer mistakes

* Added example of using codeblocks in placeholder text

* Grammer and spelling mistakes

* Add puncuation

* Remove old issue template

* Removed libraries from platform choices, added N/A option

* Removed "Feature Request:" from title and moved to auto-apply `Feature Request` label

* Removed Content Pipeline from platforms, moved N/A to bottom

recieve -> receive

Files makes more sense as users can upload .zip project files an other files needed to reproduce issue.

* Empty commit to start draft PR

* TargetFramework net6.0 to net8.0

* Use .NET 8 in workflow

* Update to newest cake version

* Ensure third party libs are in lib\net8.0

* Update packages with vulnerabilities
Test projects had transient package references with high security vulnerabiltiy warnings.  Top level pacakges `Microsoft.NET.Test.Sdk` and `NUnit3TestAdapter` were updated to resolve issue

* Updated packages for security vulnerabilities
- Transient packages from `SharpDX`, `SharpDXDirect2D1`, `SharpDX.Direct3D11`, `SharpDX.DXGI`, `SharpDX.MediaFoundation`, `SharpDX.XAudio2`, and `SharpDX.XInput` are marked as high risk security vulnerability.  Tried updating SharpDX directly, but new version (4.2.0) has breaking changes to the `IAsyncCallback` interface.  Opted to instead update the transient dependencies directly as top-level pacakges:
    - `Microsoft.NETCore.App` updated to 2.1.30
    - `Microsoft.NETCore.Jit` updated to 2.0.8
    - `System.Net.Http` updated to 4.3.4
    - `System.Security.Cryptography.X509Certificates` updated to 4.3.2

* Updated packages for security vulnerabilities
MonoGame.Framwork.Content.Pipeline` transient packages contain high risk security vulnerabilities.  Updated the following to top-level packages to resolve issue:
    - `Microsoft.NETCore.App` updated to 2.1.30

* Updated packages for security vulnerabilities
MonoGame.Effect.Compiler` transient packages contain high risk security vulnerabilities.  Updated the following to top-level packages to resolve issue:
    - `Microsoft.NETCore.App` updated to 2.1.30

* Removed unused `System.Drawing.Common` package
`System.Drawing.Common` package version presented a high risk security vulnerability.  After further checking, this NuGet isn't actually used for this project, so it was removed all together.

* Changed Project SDK
Updated from `Microsoft.NET.Sdk.WindowsDesktop` to `Microsoft.NET.Sdk`

---------

Co-authored-by: Christopher Whitley <whitleych17@ecu.edu>

Prevent the timing of audio tests from overrunning

…at converts "BlendIndices0" VectorChannel to Vector4

…xture (some platforms require them to be in the same order)

MGCB files may contain references to custom content processors libraries
that needs to be built before running the MGCB command.

Changed RunContentBuilder target so it runs after dlls are built,
so /reference: can be resolved.

…e#7895)

* Fix iOS GamePlatform to run pending background tasks MonoGame#7520

In other `Platform` classes (such as `SDLGamePlatform` and `AndroidGamePlatform`, `Threading.Run()` is called during `Tick()` or `RunLoop()` (inconsistently, it may be called before or after `Game.Tick()` unfortunately).

Fixing this for `iOSGamePlatform`. `WinForms` and perhaps other platforms (Switch?) may suffer from the same issue.

Note that texture loading from background thread is discouraged however a lot of computationally intensive operations (reading/decoding the image file streams, allocating CPU buffers) could be done in the background thread and hence is a good practice to move such work alone into the bgthread until we request the actual texture from the main thread.

* Update docs for sync/test code

* Fix typo in comment

* Add coalesced touch events to iOS GameView

* Add coalesced touch API to TouchPanel*

* Fix UTF-8 copyright mistake

* Ensure we process coalesced touches only if the client asked for it

* Avoid using C#5.0+ features (expression-bodied properties)

* Suggested changes

* Remove Coalesced API (new) and update existing touch event with a flag for `isHighFrequency`.
 - Also consistently use `high-frequency` instead of `coalesced` when referring to this new behavior.

* Remove `out int` C# 7.0 / use C# 5.0 feature instead

* Update based on @harry-cpp comments

* Rename to `origin` instead of `upstream`

* Remove git stuff

* Address PR comments

* Change (c) UTF-8 due to codepage issues, my bad.

---------

Co-authored-by: Tom Spilman <tom@sickheadgames.com>
Co-authored-by: Thao D <thao.mindfulplay@gmail.com>
Co-authored-by: Simon (Darkside) Jackson <darkside@zenithmoon.com>
Co-authored-by: mindfulplay.build <mindfulplay@appu.app>

Co-authored-by: Jake Kirkbride <jakelegendxiii@rjtechnologies.com>

* Added vector rotation helper functions

* Moved Vector rotation function to Vector2 & added non static versions

…Helper.CalculateTangentFrames (MonoGame#8139)

*Note
FIx currently skips geometry with empty normals as the CalculateNormals function is not working (failing tests)

* Update Copyright to MonoGame Foundation, Inc

* Update all code to use LICENSE.txt

* Fix up weird character encoding

* Switch driver device type from REF to WARP

* Add comment identifying Adapter Assert that has onboard graphic issues

Implements GetHashCode to resolve build warnings.  Related to issue https://github.com/MonoGame/monogame.github.io/issues/92

This renames the `uif` struct to `UIF` to resolve the CS8981 warning on build.

Resolves the invalid cref warning that appears in BoundingBox when building the project or building for documentation in the documentation repo by changing the `<see cref=""/>` tags to the appropriate `<paramref name=""/>` tags

* Supress CS3021 warning on public members

* Remove `[CLSCompliant(false)]` attribute and `#pragma`'s

Per disscussion in MonoGame#8158, the `CLSCompliant` attribute has now been removed so the `#pramga warnning disable` statements are no longer needed for this resolution.

The base `GetObjectData` has been marked obsolete.  The override implementation here does nothing itself except call the base.  This can be removed which also resolves the warning message shown during build and documentation build.