Visual Studio View Designer on .vb file.

Michael P. Reeder 0 Reputation points
2026-08-22T19:21:51.63+00:00

In Visual Studio Insiders i have NRODReports vb project with report IDCCSLoop.vb. in solution explorer i right click the file and select "View Designer". a tab appears that looks like this
User's image

Developer technologies | Visual Studio | Other
Developer technologies | Visual Studio | Other

A family of Microsoft suites of integrated development tools for building applications for Windows, the web, mobile devices and many other platforms. Miscellaneous topics that do not fit into specific categories.

0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Bruno Caetano de Brito 245 Reputation points
    2026-10-18T00:34:06.4033333+00:00

    Hi Michael,

    The page in your screenshot isn't your report - it's the WinForms designer host telling you it couldn't create the root component. "Value cannot be null. Parameter name: instance" is a generic error: the designer got a null object back while trying to instantiate/describe your report class. With report files this almost always means the design-time support of the reporting library isn't loaded in that Visual Studio instance.

    First, check what IDCCSLoop inherits from (the "Inherits" line in IDCCSLoop.vb or IDCCSLoop.Designer.vb). The fix depends on the library:

    1. ActiveReports (Inherits GrapeCity.ActiveReports.SectionReport or similar)
      • MESCIUS documents this exact error: install the GrapeCity.ActiveReports.Serializer NuGet package in the project, then close and reopen the report.
      • Make sure the versions in licenses.licx match the referenced ActiveReports assemblies.
      • If the project targets .NET (not .NET Framework), the code-based Section Report designer only works with ActiveReports 20+, on .NET 8 or later. AR 20 is also the version that added Visual Studio 2026 support.
    2. Telerik Reporting (Inherits Telerik.Reporting.Report)
      • Telerik documents this exact error. It usually means the Telerik VS integration isn't registered for that Visual Studio install. Note that VS Insiders is a separate installation, so the extension must be installed/repaired for it too (Telerik's KB shows how to run the MSI with PRODUCTDIR pointing to the VS folder).

    General steps that help in either case:

    • Close all designer tabs, close VS, delete the .vs, bin and obj folders, reopen and Rebuild before opening the designer (it needs the compiled types).
    • Click "Show Call Stack" on that error page. The top frames will show which assembly is failing — please post it here if the steps above don't help.
    • Try opening the same solution in a stable Visual Studio release. If it works there, the problem is specific to the Insiders build/extension compatibility, not your project.

    If you reply with the base class of the report and the call stack, we can narrow it down.

    Sources:

    Was this answer helpful?

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.