Permission Sets, Attributes

M

Mythran

I have 3 projects in a solution; Project1, Project2, and Project3. All 3
projects are given a strong-name using the same snk file.

What I need is to have Project3 not be callable from any assembly exception
Project2. I can use StrongNameIdentityPermissionAttribute to keep
assemblies that don't have the same public key from calling it, but Project1
can still call this assembly...so, are there any attributes I can use to
prevent any other assemblies from calling Project3?

Thanks in advance,
Mythran
 
G

Guest

Hi,

Why dont you make project 3 a private assembly in project 2. That would
be the easiest way to make project 3 only callable from project 2

Ken
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

using duplicated class 3
Where to place app.config file 4
Serialization and inheritance 3
Shared .cs files, and file locations 2
MissingManifestResourceException 1
Best Practices for MultiProject Solutions 1
Use of Assembly Attributes 1
GUIDs, snks, reflection and ILMerge 3

Top