@import markup directive fails for namespace with all top-level classes being internal

Hmm,

If I have a namespace (in this case NGM.Code) in which all top-level classes are internal (explicitly or implicitly), then importing this namespace in my master page does not work anymore, failing at runtime:

image

image

But if I change any single one of those top-level classes to become public, while the rest of them remain internal, it starts working again.
image

Am I missing something obvious here?

It’s a bug, thanks for letting us know.

fix: Allow internal-only namespaces in `@import` directive by exyi · Pull Request #1765 · riganti/dotvvm · GitHub

1 Like

It it fixed in version 4.2.5

I can confirm, the bug went away in our project. Thank you!

1 Like