Reply To: Shared Preferred Types

[timv]

I see this thread is pretty old (2,5 years), but I would like to bring up this issue once more. (hope you don’t mind me reviving such an old thread for this purpose)

We’re experiencing the same workflow issue described here. I think it makes sense to auto import/export or auto save/load these typePrefs in such a way that they are part of the project. This way no one can forget about exporting and other people don’t need to run import after pulling the latest changes from their repo. Could you reconsider adding something like this?

On top of this I wanted to ask two more things regarding these preferred types:
– Would it be possible to move the generation of AOTClasses.cs and link.xml to an automated build step, so you don’t have to manually trigger this?
– Would it even be possible to automatically detect which types are needed? What would it take to do that?