Home/ Questions/Q 6335037
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-24T18:46:38+00:00

I’m writing a library that has a bunch of classes in it which are

  • 0

I’m writing a library that has a bunch of classes in it which are intended to be used by multiple frontends (some frontends share the same classes). For each frontend, I am keeping a hand edited list of which classes (of a particular namespace) it uses. If the frontend tries to use a class that is not in this list, there will be runtime errors. My goal is to move these errors to compile time.

If any of you are curious, these are ‘mapped’ nhibernate classes. I’m trying to restrict which frontend can use what so that there is less spin up time, and just for my own sanity. There’s going to be hundreds of these things eventually, and it will be really nice if there’s a list somewhere that tells me which frontends use what that I’m forced to maintain. I can’t seem to get away with making subclasses to be used by each frontend and I can’t use any wrapper classes… just take that as a given please!

Ideally, I want visual studio to underline red the offending classes if someone dares to try and use them, with a nice custom error in the errors window. I also want them GONE from the intellisense windows. Is it possible to customize a project to do these things?

I’m also open to using a pre-build program to analyze the code for these sorts of things, although this would not be as nice. Does anyone know of tools that do this?

Thanks

Isaac

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Let’s say that you have a set of classes F. You want these classes to be visible only to a certain assembly A. Then you segregate these classes in F into a separate assembly and mark them as internal and set the InternalsVisibleTo on that assembly to true for this certain assembly A.

    If you try to use these classes from any assembly A' that is not marked as InternalsVisibleTo from the assembly containing F, then you will get a compile-time error if you try to use any class from F in A'.

    I also want them GONE from the intellisense windows. Is it possible to customize a project to do these things?

    That happens with the solution I presented above as well. They are internal to the assembly containing F and not visible from any assembly A' not marked as InternalsVisibleTo in the assembly containing F.

    However, I generally find that InternalsVisibleTo is a code smell (not always, just often).

    • 0