Hi Steve Rehling,
I'm glad that you were able to resolve your issue and thank you for posting your solution so that others experiencing the same thing can easily reference this! Since the Microsoft Q&A community has a policy that "The question author cannot accept their own answer. They can only accept answers by others ", I'll repost your solution in case you'd like to accept the answer.
Ask: Blazor WASM JS Calls with an Object Argument Work in VS Debug But Not a Published Release
Solution: The problem has been fixed as a result of installing (or re-installing) the wasm-tools workload by running dotnet workload install wasm-tools from the command line as recommended here and here (see the AOT section). The 1st "here" says that installing wasm-tools is optional, while the 2nd one says it's required for AOT. I need to use AOT for a production publish, but have not been using it as part of this testing sequence. After running the install, removing the DynamicDependency attributes, and setting PublishTrimmed to true in the project file, the published app runs as it does in the VS debugger (with and without AOT).
When I ran the install, I watched a bunch of packages being installed and a few being removed, the latter making me wonder if I already had it installed and this corrected some problem. Anyway, installing wasm-tools added 32 packages in my Nuget package manager, none of which can be uninstalled by the Nuget manager. It looks like I don't need many of them and will be looking at how to get rid of them (maybe they will just be trimmed!). But for now, this is the solution to my problem.
If you have any other questions, please let me know.
Please don’t forget to Accept Answer and Yes for "was this answer helpful" wherever the information provided helps you, this can be beneficial to other community members.