Our best practice is to use option 2. Separate projects allow you to test your automations apart from the solution. The only time I would ever place multiple unrelated adapters (unrelated meaning that you can run and test one application without the other) within the same project is if I were using a Citrix Context to use Citrix "mixed-mode", as that's the only way to use Contexts (those solutions require a single project). Even then, I would still build my adapters as separate projects and import them into the main project/solution. The reason being is that with a single project, you cannot have multiple developers sharing resources as there's no way to merge those changes together. In addition, creating separate projects allows your adapter projects to focus on the logic for an adapter versus the logic for your solution. An example might be adding a note. You adapter project would have an automation that adds a note and takes in the text of the note to add (or the category to select, etc...). Your solution would have a requirement to add a note with a specific category based on logic and then come up with specific text to add to the note body. Ideally, this logic is done outside of the adapter, so that the "AddNote" automation is wholly reusable.