Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. General Programming
  3. C#
  4. Class library assembly permissions, best practice

Class library assembly permissions, best practice

Scheduled Pinned Locked Moved C#
csharpsecurityquestiondiscussion
1 Posts 1 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • H Offline
    H Offline
    harleydk
    wrote on last edited by
    #1

    Hello, I wish to incorporate some assembly security attributes to my class library. So I add something like this to my class library namespace: [assembly:System.Net.SocketPermission(SecurityAction.RequestMinimum)] namespace olapWeb_Controls { So on and so forth. Yet I have many classes in my class library - all of them reference the namespace. Apparently I can add permission by simple adding the directives to just one of the classes - but I would rather I added them one central place, rather than in just one class (which might get changed by someone else than me). Adding the same permissions to every single class seems like overkill. What should my best practice be? Many thanks, Morten, Denmark

    1 Reply Last reply
    0
    Reply
    • Reply as topic
    Log in to reply
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes


    • Login

    • Don't have an account? Register

    • Login or register to search.
    • First post
      Last post
    0
    • Categories
    • Recent
    • Tags
    • Popular
    • World
    • Users
    • Groups