2 added 11 characters in body
source | link

As both the normal features and "here be dragons" advanced features need to be publicly accessible, but the latter shouldn't normally be used, then separate them into two assemblies: a "normal usage" one and an "advanced features" one. That way, the advanced features cannot be accidentally used: a developer must explicitly add that assembly as a reference to access those features.

As both the normal features and "here be dragons" advanced features need to be publicly, but the latter shouldn't normally be used, then separate them into two assemblies: a "normal usage" one and an "advanced features" one. That way, the advanced features cannot be accidentally used: a developer must explicitly add that assembly as a reference to access those features.

As both the normal features and "here be dragons" advanced features need to be publicly accessible, but the latter shouldn't normally be used, then separate them into two assemblies: a "normal usage" one and an "advanced features" one. That way, the advanced features cannot be accidentally used: a developer must explicitly add that assembly as a reference to access those features.

1
source | link

As both the normal features and "here be dragons" advanced features need to be publicly, but the latter shouldn't normally be used, then separate them into two assemblies: a "normal usage" one and an "advanced features" one. That way, the advanced features cannot be accidentally used: a developer must explicitly add that assembly as a reference to access those features.