Craigory Coppola

It would be nice if `--check` was still available (likely as an alias of --verify-no-changes), this will break CI pipelines for several people.

This was more permanently fixed in: https://github.com/nx-dotnet/nx-dotnet/pull/596 The key thing here is just that your outputs property for the build targets needs to include the path to the obj folder....

@roldengarm As far as I can tell a functions project is just a c# project. Can you try generating them with the azure functions CLI and using the import-projects generator?...

`import-projects` looks under the specified `apps` and `libs` directories from `nx.json`. If they are blank, (including in any preset that may be in the file), then it defaults to `apps`...

See: https://nx.dev/reference/nx-json#workspace-layout

Nx isn't moving away from apps / libs, or away from the `packages` folder, they are each better for certain folks or preferences. You can even spec them as `.`...

You can replace the whole target configuration with something like ``` { targets: { serve: { command: "func" } } } ``` To try that out

That error about the daemon could be a big deal, can you grab the contents of that error for me?

I'm going to close this out. Generators + Executors for azure functions would be better suited for a new plugin.

For reference I settled on a simple generator for now that handles some, but not all of this. Currently the generator: - moves files - renames the nx project -...