Errors while creating custom VB.NET subassemblies

[denes.nagy]

Hi,

I'm trying to generate a proper VB.NET project in Visual Studio for making custom subassemblies but I can't find the reason regarding the following anomaly (I'm just testing the method with the sample files):

I made a copy of the "...\Sample\Civil 3D API\C3DstockSubAssemblies" folder and opened the "C3DStockSubassemblies" project file. The .vb files there have no issues (0 errors, 0 warnings).

But when I made a brand new project with the same options and same references and same .vb files I got a bunch of errors and some warnings.

Do you have any idea what is the reason of that?

The Visual Studio helped me out that for example the "Imports Autodesk.Civil.Runtime" line fixes the "'CorridorState' is not defined" error but I'm still curious what is the difference between the sample project file and the created one. The vb scripts of the sample project file don't include the "Imports Autodesk.Civil.Runtime" line and work well...

[Jeff_M · Accepted solution]

I don't use VB so not sure how these would be added in Visual Studio...looking at the vbproj file for the stock subassemblies there are  number of Imports that are defined there:

<ItemGroup>
<Import Include="Autodesk.AutoCAD.DatabaseServices" />
<Import Include="Autodesk.Civil" />
<Import Include="Autodesk.Civil.ApplicationServices" />
<Import Include="Autodesk.Civil.DatabaseServices" />
<Import Include="Autodesk.Civil.Runtime" />
<Import Include="Autodesk.Civil.Settings" />
<Import Include="Microsoft.VisualBasic" />
<Import Include="System" />
<Import Include="System.Collections" />
<Import Include="System.Collections.Generic" />
<Import Include="System.Diagnostics" />
</ItemGroup>

Replacing the Import Include ItemGroup in the vsproj file with the above removes all those errors.

[denes.nagy]

Many thanks! Good to know that these files can be read in XML Notepad as well...

Since then I noticed that where can I customize these general imports in Visual Studio: