Home/ Questions/Q 4021934
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-20T10:24:45+00:00

Generally speaking, a common VB.NET class should look like the following: Public Class MyClassName

  • 0

Generally speaking, a common VB.NET class should look like the following:

Public Class MyClassName

End Class

Besides, I have already seen, if I remember correctly, all of the import statements visible just like in C#:

Imports System
Imports System.Data
Imports System.Linq

Public Class MyClassName

End Class

How to make these default imports visible by default in VB.NET using Visual Studio 2008?

Is there some setting or the like in the options I shall set?

Thanks! =)

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Good question. The VB.NET Language spec only mentions “implicit imports” without giving an authoritative list. I can reverse-engineer it from the command line as shown in the output window, VS2008 and VS2010 uses this /Imports command line option:

    • Microsoft.VisualBasic,
    • System,
    • System.Collections,
    • System.Collections.Generic,
    • System.Data,
    • System.Diagnostics,
    • System.Linq,
    • System.Xml.Linq

    MSBuild sets these in Microsoft.VisualBasic.targets from the Import variable. Which is set in the .vbproj file:

      <ItemGroup>
    <Import Include="Microsoft.VisualBasic" />
    <Import Include="System" />
    <Import Include="System.Collections" />
    <Import Include="System.Collections.Generic" />
    <Import Include="System.Data" />
    <Import Include="System.Diagnostics" />
    <Import Include="System.Linq" />
    <Import Include="System.Xml.Linq" />
  </ItemGroup>

    Altering the Project + Reference setting does alter this list but there’s no obvious one-to-one correspondence since this screen changes assembly references, the <Import> build variable lists name spaces. I’ll have to punt, this ultimately is determined by the project template.

    • 0