Hi. I am using the recommended Umbraco Cloud project structure of a .Web project for the CMS and a .Core project for custom code. Until today, I thought that only the ModelsBuilder API mode could generate models in our .Core project, but I just learned from this blog post that AppData mode can do this as well.
I prefer how AppData mode exposes the ability to rebuild models from the CMS, so I'm left wondering, is there any advantage to using ModelsBuilder API mode, over using AppData mode with it set to output to a different project?
I was able to find most of the information I was looking for in this thread. I'm still not sure which ModelsBuilder option is the best for my scenario, but this at least puts me closer to figuring it out.
ModelsBuilder API mode vs AppData mode for model generation in another project
Hi. I am using the recommended Umbraco Cloud project structure of a .Web project for the CMS and a .Core project for custom code. Until today, I thought that only the ModelsBuilder API mode could generate models in our .Core project, but I just learned from this blog post that AppData mode can do this as well.
I prefer how AppData mode exposes the ability to rebuild models from the CMS, so I'm left wondering, is there any advantage to using ModelsBuilder API mode, over using AppData mode with it set to output to a different project?
Thanks,
David
I was able to find most of the information I was looking for in this thread. I'm still not sure which ModelsBuilder option is the best for my scenario, but this at least puts me closer to figuring it out.
is working on a reply...