No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

I've been using 2022 and haven't had that problem.

Although, this codebase uses the automation-api and I'm not running the cli.

Ditto, although targeting dotnet 6.0 has issues with single file executables.

i have seen the same thing you are talking about <@U014JNRGADD>. haven't really dug too deep into it because similarly on my end it is more of a small annoyance than a show stopper. i have also seen something similar when mounting a `<http://mcr.microsoft.com/dotnet/sdk|mcr.microsoft.com/dotnet/sdk>` container to the same source directory that VS is looking at. when i restore/build from the container VS will do the same thing and not recognize any classes. all i can think of is maybe there is a difference between how VS/dotnet and docker and pulumi do the restore? like if pulumi does a restore during build and moves things around in the obj folder differently than VS expects it or something, or restores to some other directory etc