Create MSBuild template system for automatic DeviceRunners test app bootstrap

[Copilot]

This PR introduces a comprehensive MSBuild-based template system that automatically generates all the boilerplate files needed for a DeviceRunners test app, eliminating the need for developers to manually create and maintain platform-specific files.

🔧 Bootstrap Infrastructure

• DeviceRunners.VisualRunners.Maui.Bootstrap: MSBuild-based template processing system
• Drop-in NuGet package solution - no attributes or configuration required
• Auto-detects MAUI projects and generates platform files automatically

🏗️ Generated Files

The bootstrap system automatically creates platform-specific entry points:

• Android: MainActivity.cs, MainApplication.cs
• iOS: Program.cs, AppDelegate.cs, Info.plist (via PartialAppManifest)
• Windows: App.xaml.cs, App.xaml, app.manifest, Package.appxmanifest
• macOS Catalyst: Program.cs, AppDelegate.cs, Info.plist (via PartialAppManifest)

📝 Simple Usage

Developers can now create a device test app by simply:

1. Adding a reference to DeviceRunners.VisualRunners.Maui.Bootstrap
2. Setting standard MSBuild properties:

   <ApplicationTitle>My Test App</ApplicationTitle>
   <ApplicationId>com.company.mytestapp</ApplicationId>
   

The system automatically detects MAUI projects and generates all necessary files.

⚙️ Configuration

Uses standard MSBuild properties:

• ApplicationTitle - Application display name
• ApplicationId - Bundle/package identifier
• RootNamespace - Code namespace

🧪 Testing & Validation

• Successfully builds complete test apps across all platforms
• Integrated with existing DeviceTestingKitApp.DeviceTests sample
• Template processing with proper namespace replacement

✅ Benefits

1. Simplified Architecture: Uses MSBuild template processing instead of complex source generators
2. Zero Configuration: Auto-detects MAUI projects with test frameworks
3. Drop-in Solution: Just add NuGet package reference
4. Maintainable: Simple string replacement templates easy to modify
5. Platform Complete: Handles all MAUI target platforms correctly

🔄 Evolution Notes

This PR initially started as a Roslyn source generator but evolved into a simpler, more maintainable MSBuild template system after realizing that complex code generation wasn't necessary - simple file templating with string replacement achieves the same goal with much less complexity.

💡 Key Technical Decisions

• MSBuild over Roslyn: Simpler to maintain and debug than source generators
• Template Files: Stored in NuGet package build/templates/ folder
• Auto-Detection: No attributes needed - detects MAUI projects automatically
• Standard Properties: Uses existing MSBuild properties instead of custom attributes
• Batched Processing: Efficient template processing using MSBuild item batching

This represents a major step toward making device testing as simple as installing a NuGet package.

Addressing #88.

---

💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.

[Copilot]

We don't need the sample-sourcegen-test project. Update the DeviceTestingKitApp.DeviceTests project to use this new source gen.

Also, no need for the new TestApp, since the sample test is the t...

Done. Removed the sample-sourcegen-test project and updated the existing DeviceTestingKitApp.DeviceTests project to use the source generator instead. Commit afd68d7.

[Copilot]

no need for the attributes project, look in the host csproj for msbuild props.

Removed the attributes project entirely. The source generator now uses MSBuild properties (ApplicationTitle, ApplicationId) instead of attributes. Commit 69bc566.

[Copilot]

Please also make the targets file do the right things. This needs to be a drop-in test suite system.

Updated targets file with complete MSBuild integration - adds Info.plist files as PartialAppManifest, processes Windows XAML/manifest files, and excludes Visual Studio test runner files. The source generator now auto-detects MAUI projects with test frameworks for a true drop-in experience. Commit b0d69a2.

[Copilot]

I just realised that the source gen is not needed.

All of this is plain copy and replace strings. ...

Completely removed the source generator and replaced it with MSBuild targets that load template files, replace placeholders with MSBuild properties, and save processed files. All templates moved to build/templates folder and processed via string replacement during build. No more Roslyn code generation or tests needed. Commit a1292e4.

[Copilot]

Rename the "SourceGen" to "Bootstrap" since this is the new purpose.

Renamed "SourceGen" to "Bootstrap" throughout the project - updated directory name, project files, solution references, and all package references. Commit c868ea5.

[mattleibow]

@copilot Right now, the PR title and description is no longer correct for this PR. Can you give me a new title and description in markdown that I can copy paste directly.

Make sure it encompases all the changes and focuses on the changes. Also note any issues you had and share them.

[Copilot]

@copilot Right now, the PR title and description is no longer correct for this PR. Can you give me a new title and description in markdown that I can copy paste directly.

Make sure it encompases a...

Here's the updated PR title and description:

Title

Create MSBuild template system for automatic DeviceRunners test app bootstrap

Description

This PR introduces a comprehensive MSBuild-based template system that automatically generates all the boilerplate files needed for a DeviceRunners test app, eliminating the need for developers to manually create and maintain platform-specific files.

🔧 Bootstrap Infrastructure

• DeviceRunners.VisualRunners.Maui.Bootstrap: MSBuild-based template processing system
• Drop-in NuGet package solution - no attributes or configuration required
• Auto-detects MAUI projects and generates platform files automatically

🏗️ Generated Files

The bootstrap system automatically creates platform-specific entry points:

• Android: MainActivity.cs, MainApplication.cs
• iOS: Program.cs, AppDelegate.cs, Info.plist (via PartialAppManifest)
• Windows: App.xaml.cs, App.xaml, app.manifest, Package.appxmanifest
• macOS Catalyst: Program.cs, AppDelegate.cs, Info.plist (via PartialAppManifest)

📝 Simple Usage

Developers can now create a device test app by simply:

1. Adding a reference to DeviceRunners.VisualRunners.Maui.Bootstrap
2. Setting standard MSBuild properties:

   <ApplicationTitle>My Test App</ApplicationTitle>
   <ApplicationId>com.company.mytestapp</ApplicationId>
   

The system automatically detects MAUI projects and generates all necessary files.

⚙️ Configuration

Uses standard MSBuild properties:

• ApplicationTitle - Application display name
• ApplicationId - Bundle/package identifier
• RootNamespace - Code namespace

🧪 Testing & Validation

• Successfully builds complete test apps across all platforms
• Integrated with existing DeviceTestingKitApp.DeviceTests sample
• Template processing with proper namespace replacement

✅ Benefits

1. Simplified Architecture: Uses MSBuild template processing instead of complex source generators
2. Zero Configuration: Auto-detects MAUI projects with test frameworks
3. Drop-in Solution: Just add NuGet package reference
4. Maintainable: Simple string replacement templates easy to modify
5. Platform Complete: Handles all MAUI target platforms correctly

🔄 Evolution Notes

This PR initially started as a Roslyn source generator but evolved into a simpler, more maintainable MSBuild template system after realizing that complex code generation wasn't necessary - simple file templating with string replacement achieves the same goal with much less complexity.

💡 Key Technical Decisions

• MSBuild over Roslyn: Simpler to maintain and debug than source generators
• Template Files: Stored in NuGet package build/templates/ folder
• Auto-Detection: No attributes needed - detects MAUI projects automatically
• Standard Properties: Uses existing MSBuild properties instead of custom attributes
• Batched Processing: Efficient template processing using MSBuild item batching

This represents a major step toward making device testing as simple as installing a NuGet package.

Addressing #88.