I believe a problem exists with the VBAProject name which is similar to the problem with references mentioned in issue #7.
I propose that there be a property in the configuration which specifies the VBAProject name and then on import, that name will be set. I don't think it is necessary to unset the VBAProject name on export.
A possible name for this configuration property: "VBAProject Name".
I believe a problem exists with the VBAProject name which is similar to the problem with references mentioned in issue #7.
I propose that there be a property in the configuration which specifies the VBAProject name and then on import, that name will be set. I don't think it is necessary to unset the VBAProject name on export.
A possible name for this configuration property: "VBAProject Name".