In C#, it is possible to compile a netmodule that has InternalsVisibleTo access to a strong named assembly. You just tell the compilation (for the netmodule) that the name of the assembly is the name of the final assembly into which it will be included. But that doesn't work in VB, because the netmodule doesn't have the correct strong name (you can't strong name a netmodule). We should adjust the VB compiler to permit this to work the same way it works in C#.