Is your feature request related to a problem? Please describe.
There are 9 projects in the solution including test projects, we have to keep MCCL and MCPP in the solution because they change regularly but projects like Vts.Scripting are used infrequently by the core team and it would be beneficial to have it in its own repo so it can be downloaded independently of the VTS library.
Describe the solution you'd like
A separate repo called Vts.Scripting that references the VTS and the VTS repository no longer containing the Scripting project.
Describe alternatives you've considered
To take away the burden of increased compile times and test times, I can unload the project in the solution but in a previous change, I forgot to reload it and broke the build.
Additional context
When we do a release, we bring in these auxiliary applications and make sure they work with the new library changes, we have been doing this for several years with the WPF GUI. If a user would like to develop the Scripting project alongside the library we have detailed instructions on how to bring the WPF into the solution and we could add the Scripting project to these instructions, they will be almost identical.
Is your feature request related to a problem? Please describe. There are 9 projects in the solution including test projects, we have to keep MCCL and MCPP in the solution because they change regularly but projects like Vts.Scripting are used infrequently by the core team and it would be beneficial to have it in its own repo so it can be downloaded independently of the VTS library.
Describe the solution you'd like A separate repo called Vts.Scripting that references the VTS and the VTS repository no longer containing the Scripting project.
Describe alternatives you've considered To take away the burden of increased compile times and test times, I can unload the project in the solution but in a previous change, I forgot to reload it and broke the build.
Additional context When we do a release, we bring in these auxiliary applications and make sure they work with the new library changes, we have been doing this for several years with the WPF GUI. If a user would like to develop the Scripting project alongside the library we have detailed instructions on how to bring the WPF into the solution and we could add the Scripting project to these instructions, they will be almost identical.