2.1 KiB
| title | description | type | page_title | slug | res_type |
|---|---|---|---|---|---|
| VB Projects cannot be built due to the usage of the Global Namespace. | VB Projects cannot be built whenf the Global Namespace is being used. | how-to | VB Projects cannot be built when using the Global Namespace. | vb-projects-cannot-be-built-due-to-the-usage-of-the-global-namespace | kb |
Environment
| Product | Progress® Telerik® Reporting |
| Framework | VB.NET |
Description
VB Projects cannot be built due to the usage of the Global Namespace.
Error Messages
Typical errors received on build are:
Type 'Telerik.Reporting.TextBox' is not defined.
Type 'Telerik.Reporting.ReportItemBase' is not defined.
Type 'Telerik.Reporting.Report' is not defined.
Type 'Telerik.Reporting.XXXX' is not defined.
When you open the report's Designer.VB file you will find that lines like:
Me.TextBox1 = New Telerik.Reporting.TextBox()
are underlined as error lines.
Changing the line as follows should resolve the error:
Me.TextBox1 = New Global.Telerik.Reporting.TextBox()
The issue is that changing a setting of the report will cause the Reporting engine to re-serialize the code in the report's Designer.VB file without the custom Global namespace.
Cause
This happens when classes are held in different than the root namespace in Visual Basic projects.
Solution
Open the project's Properties in Visual Studio and remove the Root Namespace, leave it blank. This will let you skip the Global namespace on specifying types.
Notes
If the above changes do not resolve the listed errors, double-check if the required Telerik Reporting assemblies are referenced, and run the [Upgrade Wizard]({% slug telerikreporting/designing-reports/report-designer-tools/desktop-designers/visual-studio-report-designer/upgrade-wizard %}) to update all settings.