Add project capabilities to C# Dev Kit project loading logs

[Copilot]

Summary

Updated the logging for C# Dev Kit project loading to include project capabilities when available.

Changes Made

• Added ProjectCapabilities field to WorkspaceProjectCreationInfo (backward compatible with default value)
• Updated logging in WorkspaceProjectFactoryService to include capabilities
• Added new resource string with capability placeholder
• Updated all 13 localization (.xlf) files
• Updated test to verify logging output with CapturingLoggerProvider
• Renamed test to LogProjectLoadWithCapabilities to better reflect its purpose
• Fixed IDE0055 formatting errors

Test Updates

The LogProjectLoadWithCapabilities test:

• Uses a custom CapturingLoggerProvider to capture log messages
• Verifies the log message includes "with capabilities: CSharp, Test, Managed" when capabilities are provided
• Verifies the log message does NOT include "with capabilities:" when no capabilities are provided (backward compatibility)
• Confirms both scenarios contain "loaded by C# Dev Kit"

Expected Log Output

With capabilities:

Project /path/to/Project.Tests.csproj loaded by C# Dev Kit with capabilities: CSharp, Test, Managed

Without capabilities (backward compatible):

Project /path/to/Project.csproj loaded by C# Dev Kit

Original prompt

Code exists in this repo to log when a project is loaded by C# Dev Kit. Lines look like this...

[C#] [serviceBroker/connect] [WorkspaceProjectFactoryService] Project /path/to/Project.Tests.csproj loaded by C# Dev Kit

Can you update the logging to report the capabilities on the project when it is loaded as well?

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[jasonmalinowski]

Is the expectation the project capabilities are going to be used for something else down the road, or is this only for logging?

[jasonmalinowski]

(maybe my real question is "the PR description tells me what this does, it doesn't tell me why")

[peterwald]

The Test Explorer uses project capabilities, so we wanted to have logging that shows what their values are when loaded.

[dibarbet]

The Test Explorer uses project capabilities, so we wanted to have logging that shows what their values are when loaded.

How is the C# extension involved here though - we don't utilize project capabilities? Wouldn't it be more appropriate to log on the CDK or test explorer side where they are produced or consumed? Imagine if there was some bug where the capabilities got sent to us, but not to the test explorer.

[peterwald]

That's a fair point. The Test Explorer already does log this info, but since our project query filters projects based on capability we don't know for sure what is happening when a test project doesn't get reported to us. The intent was to log this info further up the line to get more visibility. I saw this log entry in the logs, so that is what I targeted to add additional info. I guess we could target CDK instead.

[dibarbet]

I guess we could target CDK instead.

That would be my preference - similar to the test explorer we're just a consumer of whatever CDK sends us. Logging on the CDK side seems more beneficial as they are the producers of this information. Additionally - I am not sure if anything will get logged here if the project changes after creation - this just logs the initial load.

[peterwald]

@copilot Fix the formatting issues reported in the following build errors.

❌src/LanguageServer/Microsoft.CodeAnalysis.LanguageServer.UnitTests/WorkspaceProjectFactoryServiceTests.cs(82,1): error IDE0055: Fix formatting (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/style-rules/ide0055)
❌src/LanguageServer/Microsoft.CodeAnalysis.LanguageServer.UnitTests/WorkspaceProjectFactoryServiceTests.cs(97,1): error IDE0055: Fix formatting (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/style-rules/ide0055)
❌src/LanguageServer/Microsoft.CodeAnalysis.LanguageServer.UnitTests/WorkspaceProjectFactoryServiceTests.cs(101,1): error IDE0055: Fix formatting (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/style-rules/ide0055)

[Copilot]

@copilot Fix the formatting issues reported in the following build errors.

...

Fixed in commit 63be8f5. Removed trailing whitespace from lines 82, 97, and 101.