...
The default translation process for a VBP creates a .NET version of each code file referenced by the VBP. If multiple VBPs reference the same code file, there will be multiple copies of the shared file translations: one for each VBP. Restructuring the generated code files to remove this duplication is a common upgrade feature that we call Shared Files Consolidation. Many different configurations of code files are feasible. The constraints arise from the external dependencies that are contained within each file that must still be satisfied after conversion consolidation without creating build cycles or other naming conflicts.
For a large-scale VB6 application with shared files, it is possible to reproduce something close to the structure of the legacy app using .NET linked files, but linked files are still not a straight conversion: we would have to make some decisions and also deal with assigning and using namespaces. Code file linking has other disadvantages for builds and deployments so it has a higher cost of ownership. Consequently, there is some value in hosting each shared file in only one assembly and referencing it there. gmStudio can help implement this re-hosting process.
...