VBAToolKit reference is not activated in new projects
jpimbert opened this issue · 4 comments
jpimbert commented
Incomplete Fix of Issue#5
To take into account at creation and recreation of projects (except for VBAToolKit itself)
To fix in the same time as the project recreation enhancement
lucas-v commented
What is there to fix exactly ?
jpimbert commented
Nothing. Normally taken into account in the xmlConfiguration branch. I have to check.
jpimbert commented
VBAToolKit must be referenced only in DEV configuration. Currently, the DEV configuration is named _DEV. A possible enhancement is to add a boolean property "forDevelopment" to each configuration, and set the VBAToolKit reference accordingly.
This behavior must be implemented :
- in the function which create a new project
- in the configuration management
- in the XML exportation of configurations description
But if there is more than one Dev configuration, there will be copies of the configuration sheet and possible conflicts
jpimbert commented
Not sured when it was fixed, now it's the case.