An extension for Visual Studio that makes the workflow with Entitas-CSharp alot smoother.
Recent update to Visual Studio Tools for Unity
Thanks to everyone trying out the extension. After a new update Unity the Visual Studio Tools for Unity automatically add new items to Visual Studio that is added inside the Assets directory without showing the "Reload Solution" dialog (The Unity Tools also adds the items significantly faster than Entitas-vs).
Therefore I recommend updating to the latest Visual Studio Tools for Unity and bind the code generation inside Visual Studio as described here and not use Entitas-vs as it will not be maintained anymore.
The paid Roslyn Generator is strongly recommand when using this extension because it is able to generate with compiler errors. The Normal Generator from Entitas will also work, but because the Normal Generator is reflection-based, compiler errors will block it from generating (which makes it very cumbersome to work with).
To use Entitas VS you need to:
Setup Entitas as you normally would (follow one of these guides by the author of Entitas: video guide, text guide)
Make sure that the commandline generator works correctly. Try generating some files before using Entitas VS.
Fill out the generator path and the trigger paths.
Open Tools -> Entitas VS
Set the generator path.
Select the Generator folder by pressing the "..." button. If the Generator folder is in the solution directory the path will automatically be converted to a relative path (which is recommended).
Click the drop down-menu to add a project.
Note: For each project you want to generate files for, the Entitas.properties and User.properties has to be placed in the project directory (beside the .csproj file). This allows for multiple project generation (though only one generator is supported for now).
Add the folders that trigger the code generation when files in the folder are saved. Here the code generator is triggered when changes occur in the Sources\Assets\Components folder. Like the Generator folder, if the Trigger folder is in the project directory, the path will be converted to a relative path.
That is all. Create a new component, save the file, and the generation will run automatically. All these settings are saved in entitas-vs.cfg, in the solution directory.