Skip to content

Managed vs unmanaged code sample: move to .NET 11 - #2384

Open
vladimir-pecanac-main wants to merge 1 commit into
CodeMazeBlog:mainfrom
vladimir-pecanac-main:seo/90107-csharp-managed-vs-unmanaged-code-garbage-collection
Open

vladimir-pecanac-main wants to merge 1 commit into
CodeMazeBlog:mainfrom
vladimir-pecanac-main:seo/90107-csharp-managed-vs-unmanaged-code-garbage-collection

Conversation

@vladimir-pecanac-main

Copy link
Copy Markdown
Collaborator

Moves the ManagedVsUnmanagedCodeInCSharp sample to net11.0 with current test packages. The MessageBox declaration becomes a LibraryImport with the MessageBoxW entry point, Windows-only and called behind a platform check, Program.cs uses top-level statements, both AllocHGlobal uses free their memory in a finally block, and new code shows GC generations, a SafeHandle wrapper over unmanaged memory and an allocation measurement of string concatenation against StringBuilder, with six new tests.

Target net11.0 and update the test packages (xunit 2.9.3, xunit.runner.visualstudio 4.0.1,
Microsoft.NET.Test.Sdk 18.12.0, coverlet.collector 10.1.0). Program.cs uses top-level
statements; the MessageBox declaration moves to NativeMethods.cs as a LibraryImport with
EntryPoint MessageBoxW, Windows-only and called behind OperatingSystem.IsWindows(). The
unsafe loop reads numbers.Length, and both AllocHGlobal uses free their memory in a finally
block. New GenerationInspector, UnmanagedBuffer (SafeHandle) and StringBuildingAllocations
(GC.GetAllocatedBytesForCurrentThread, 10,000 iterations), ToyCarInfo is public, the test
name typo is fixed, and six tests cover the new code.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant