Permanently turn off vb.namespace?

[jmcilhinney]

You can remove the reference to the dll MicrosoftVisualBasic.dll

How exactly can you do that? There is no reference to that assembly listed in the Solution Explorer. I can add a reference to that assembly to a C# project if I want and see it listed, but I cannot remove one from a VB.NET project, or at least not the conventional way.

[wossname]

How exactly can you do that? There is no reference to that assembly listed in the Solution Explorer. I can add a reference to that assembly to a C# project if I want and see it listed, but I cannot remove one from a VB.NET project, or at least not the conventional way.

You're not looking in the right place thats why. Its in the Project Properties dialog. Its under "imports" or something and there is a list of namespaces that are loaded regardless of whats in the solution explorer references list.

[jmcilhinney]

You're not looking in the right place thats why. Its in the Project Properties dialog. Its under "imports" or something and there is a list of namespaces that are loaded regardless of whats in the solution explorer references list.

Like I said before, importing a namespace is not the same as referencing an assembly. Importing a namespace just means that you can use members of that namespace in code without qualifying them. If you remove the project-wide import of the Microsoft.VisualBasic namespace you are not prevented from using Runtime functions. It just means that you would have to use, for example, Microsoft.VisualBasic.Interaction.MsgBox in code instead of just MsgBox. You would have to actually remove the reference to the assembly in with the Interaction module is defined. If you add a reference to the Microsoft.VisualBasic.dll assembly to a C# project then you can use MsgBox in C# code. Remove the reference and you can't again, but I'm saying that there is no reference to that assembly visible in a VB.NET project for you to remove, at least not through the IDE anyway.