pandaGaume
commented
3 years ago @Drigax @thomlucc even if labeled as "futur" milestone, i review some proposal from Drigax.
regarding the Setup Edit and Continue Debugging from VS point of view, the issue here is about unloading and reloading the plugin dynamically, which is not possible into the Autodesk system. One solution should be to build a proxy as plugin, which is in charge of loading the export Babylon dll's only when need, then release the dll's when not needed anymore. This is something we can name a Babylon Bootstrap.
Then we have a %max_location%bin/assemblies/Babylon/ or %userData%Babylon/ which will be the place to hold profiles and setting for the babylon exporter. The manifest will hold the necessary informations to locate the used bin directory to let the plugin load the necessary dll, even remotely with AppDomain...
The current debugging workflow is somewhat cumbersome. currently, one has to restart maya and 3dsMax between iterations, as the binary needs to be replaced and the DCC tool has to be restarted to test even the most trivial of changes.
I propose a few improvements to be made to the development environment including:
[ ] Setup Edit and Continue Debugging for 3dsMax and Maya projects This change should allow one to quickly re-iterate without needing to restart their DCC tool. One topic of concern is "how can we configure the project to update the installed binary when edited live?"
[ ] Change post-build script to no longer replace Max2Babylon/Maya2Babylon binary. This should not be part of the build process. The build process should only create the Max & Maya2Babylon binary for the given version. This should instead be part of Visual Studio's run process:
[ ] Change project debug settings to launch the respective version of Maya/3dsMax, and install the built binaries.