Preserve executable output kind when evaluating generator methods (top-level statements support)

[Copilot]

• Review new PR comment and confirm requested change scope
• Check recent CI workflow runs/logs for this branch
• Add explicit System.Console metadata reference in generator runtime test helper
• Run targeted runtime tests on affected test class
• Run code review and security scan, then reply to PR comment

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Generators fail for project that are not class libraries</issue_title>
<issue_description>e.g.:

MSGH004: Failed to execute generator method 'GetPiDecimal_Generator_Specialized': Compilation failed: Program using top-level statements must be an executable.</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes Generators fail for project that are not class libraries #77

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ All tests successful. No failed tests found.

📢 Thoughts on this report? Let us know!

[Copilot]

Pull request overview

Fixes generator execution failures when the target project is an executable (e.g., uses top-level statements), by ensuring the generator’s “execution compilation” preserves the original project’s output kind instead of forcing a DLL.

Changes:

• Stop overriding the execution compilation to OutputKind.DynamicallyLinkedLibrary, allowing top-level statements to compile.
• Add a regression test that exercises generator-method execution against a ConsoleApplication compilation with top-level statements.
• Extend the test helper compilation factory to accept an OutputKind.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File	Description
EasySourceGenerators.Generators/GeneratesMethodExecutionRuntime.cs	Preserves the original compilation’s output kind when building the execution compilation so executable projects (top-level statements) don’t fail to compile.
EasySourceGenerators.GeneratorTests/GeneratesMethodExecutionRuntimeTests.cs	Adds regression coverage for the top-level statements scenario and updates the test compilation helper to support non-DLL output kinds.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

This new regression test’s top-level statement uses Console.WriteLine, but GetMetadataReferences() doesn’t explicitly reference System.Console (it relies on whatever assemblies happen to already be loaded in the AppDomain). That can make the test environment-dependent/flaky if System.Console isn’t loaded. Consider using a top-level statement that doesn’t require extra references (e.g., int _ = 0;), or explicitly add a System.Console metadata reference for determinism.

Suggested change

	using System;
	Console.WriteLine("warmup");
	int _ = 0;