dynamodb: breaking change in .NET, resource renamed `Table` -> `Table_`

[johan-lindqvist]

Describe the bug

Table has been renamed to Table_ in .NET in v2.222.0 which is a breaking change and I assume an error since it is still named Table in other languages like TypeScript.

Regression Issue

• Select this option if this issue appears to be a regression.

Last Known Working CDK Library Version

2.221.1

Expected Behavior

Table class should be named Table and not Table_ even in .NET

Current Behavior

Table class was renamed to Table_ in 2.222.0 for .NET

Reproduction Steps

Download NuGet package, check DynamoDB namespace for Table_

Possible Solution

Rename it to what it was before the regression. Might have something to do with the code generation since when I check the typescript or golang reference pages they still have Table and not Table_

Additional Information/Context

Reference for .NET: https://docs.aws.amazon.com/cdk/api/v2/dotnet/api/Amazon.CDK.AWS.DynamoDB.Table_.html
Compare with
Reference for TypeScript: https://docs.aws.amazon.com/cdk/api/v2/docs/aws-cdk-lib.aws_dynamodb.Table.html

AWS CDK Library version (aws-cdk-lib)

2.223.0

AWS CDK CLI version

2.1031.2 (build 779352d)

Node.js Version

v22.14.0

OS

Windows 11

Language

.NET

Language Version

.NET 9.0.306

Other information

No response

[pahud]

https://docs.aws.amazon.com/cdk/api/v2/dotnet/api/Amazon.CDK.AWS.DynamoDB.Table_.html

The NuGet documentation confirms that Table_ is the current class name in the .NET API documentation. The documentation shows:

1. Class name: Table_ (with underscore)
2. Namespace: Amazon.CDK.AWS.DynamoDB
3. Example code in the documentation still uses new Table(...) without the underscore, which is confusing

This confirms the issue reporter's observation. The .NET bindings have indeed renamed Table to Table_ in v2.222.0+, while:
• The documentation examples still show new Table(...)
• Other languages (TypeScript, Python, Java, Go) still use Table
• There's no actual naming conflict in the source code

This seems to be a JSII .NET code generation issue that occurred in v2.222.0, likely as an unintended side effect of JSII changes rather than an intentional rename.

Reaching out to the team for immediate review.

[pahud]

We believe the root cause is at https://github.com/aws/aws-cdk/pull/35554/files#diff-6872128dc5c21c15d95d08e33ae84a0945b70918a6c4cec26f7746eef988455fR1209

We'll submit an immediate fix today.

[github-actions]

Comments on closed issues and PRs are hard for our team to see.
If you need help, please open a new issue that references this one.