Aspire 13.2 broke AWS Lambda Integration

[normj]

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

Starting with Aspire 13.2 our AWS Lambda integration broke when launched in debug mode from Visual Studio. For .NET Lambda we have 2 different programming models. The complicated one for Aspire and which broke with 13.2 is where a Lambda function is defined in a class library. Our integration during startup generates a launch profile in the .NET Lambda project's launchSettings.json that sets up the bootstrapping executable and then we specify that launch profile for the project being launched within Aspire.

  "profiles": {
    "Aspire_my-lambda": {
      "commandName": "Executable",
      "executablePath": "dotnet",
      "commandLineArgs": "exec --depsfile ./MyLambdaFunction.deps.json --runtimeconfig ./MyLambdaFunction.runtimeconfig.json %USERPROFILE%\\.dotnet\\tools\\.store\\amazon.lambda.testtool\\0.13.0\\amazon.lambda.testtool\\0.13.0\\content\\Amazon.Lambda.RuntimeSupport\\net10.0\\Amazon.Lambda.RuntimeSupport.TestTool.dll MyLambdaFunction::MyLambdaFunction.Function::FunctionHandler",
      "workingDirectory": "bin\\Debug\\net10.0\\"
    }
   ...
,

In Aspire 9.x up to 13.1 this worked fine but with 13.2 it fails with the log output indicating it doesn't like that we are using a class library even though this technic worked for us before.

Unable to proceed with project 'C:\Temp\AddAWSLambdaFunctionRepro\MyLambdaFunction\MyLambdaFunction.csproj'.
 Ensure you have a runnable project type.
 A runnable project should target a runnable TFM (for instance, net11.0) and have OutputType 'Exe'.
 The current OutputType is 'Library'.

Expected Behavior

.NET Lambda function defined in a class library is executed following the configuration we setup in the launchSettings.json file.

Steps To Reproduce

We have the following repo you can clone and reproduce the issue by opening the solution and launching the AppHost. The Lambda function will show finished right away. The repo does not require an AWS account to use.
https://github.com/dscpinheiro/AddAWSLambdaFunctionRepro

Exceptions (if any)

No response

.NET Version info

No response

Anything else?

No response

[normj]

I have confirmed that I can leave the SDK version at 13.2.0 but revert the Aspire.Hosting.AppHost to version 13.1.3 and the Lambda function launches correctly in the AppHost.

[normj]

For additional context in Lambda we subclass ProjectResource as LambdaProjectResource and add the LambdaProjectResource resource via the AddResource method not AddProject. Here is the code that does this along with setting up the LaunchProfileAnnotation annotation. https://github.com/aws/integrations-on-dotnet-aspire-for-aws/blob/main/src/Aspire.Hosting.AWS/Lambda/LambdaExtensions.cs#L45

This code hasn't changed in quite awhile but maybe something on the Aspire side doesn't like anymore that we aren't calling AddProject for our subclass. We use AddResource because there isn't a way to use subclasses of ProjectResource with AddProject.

[normj]

@davidfowl @adamint @mitchdenny

I put out a PR in our AWS repository that seems to fix the issue but would really appreciate your input confirming I'm doing the right thing. Basically I added a call to WithDebugSupport when I add my Aspire resource for the LambdaProjectResource. That seemed to work but I'm confused why I'm required to do that now and seems odd since WithDebugSupport is marked as experimental.

aws/integrations-on-dotnet-aspire-for-aws#168