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. component configuration.

component configuration.

Scheduled Pinned Locked Moved C#
xmlquestionworkspace
2 Posts 2 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.
  • D Offline
    D Offline
    Darkmatter
    wrote on last edited by
    #1

    ok the application config xml file is great for applications but what if I create a namespace / class that will be compiled as a dll and used in other application, where would or rather should I stick it configuration "defaults" in the host application config xml file or should it have it's own file? Thanks Rob ;P

    P 1 Reply Last reply
    0
    • D Darkmatter

      ok the application config xml file is great for applications but what if I create a namespace / class that will be compiled as a dll and used in other application, where would or rather should I stick it configuration "defaults" in the host application config xml file or should it have it's own file? Thanks Rob ;P

      P Offline
      P Offline
      perlmunger
      wrote on last edited by
      #2

      Definitely use the 'configuration "defaults" in the host application config xml'. In general, if you are building a separate dll for binary re-use, you probably don't want the library (dll) itself to ever be concerned about application level settings and serializing them. Even if they are settings specific to the dll, they are settings that will be collected from the user in whatever application you are using and then passed into whatever objects you use from the dll upon instatiation. You can also use the registry to store the values from your main app. Then, when you want to use an object from your dll, pass in the values after obtaining them back from the registry (or XML) to the object constructor. Hope that makes sense. -Matt ------------------------------------------ The 3 great virtues of a programmer: Laziness, Impatience, and Hubris. --Larry Wall

      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