How to make sure constructors aren't used in separate project

[schMarXman]

I am currently designing domain models for a new project. The resulting models library will also be used in another existing project. How do I make sure that the model constructors aren't used (or throw) in the consuming project? If I replicate the basic ID example from the wiki, build the library, then reference the library in the other project the default constructors pass without errors e.g. new ID(). Thanks!

[SteveDunn]

Hi @schMarXman - are you saying that your [ValueObject<>] types are in My.ClassLib, and you're referencing My.ClassLib as a project reference my My.Exe?

[SteveDunn]

For the library, the source generator generates the other side of the partial class (or struct).
The the exe, you can reference the library without Vogen, but you won't get the functionality from the analyzers.

[SteveDunn]

Actually, this looks like a bug! Thanks for spotting! I'll fix this soon.

[SteveDunn]

Actually, I'm not so sure now. Are your model libraries part of the same solution as the consumers of those libraries? If not, how are they referenced (NuGet/dlls)?

[SteveDunn]

@schMarXman - I'm guessing you're referencing these as a library/nuget package. If so, Vogen should be added to the consuming project so that the analyzers can analyzer your code to ensure it doesn't violate any of the rules.

#778 (comment)