Note that there are some explanatory texts on larger screens.

plurals
  1. POHow can I access server-level IIS connection settings programatically from within a .NET class?
    primarykey
    data
    text
    <h2>Background</h2> <ul> <li>We are using a reporting tool which is .NET based.</li> <li>The reporting tool uses a settings file which is a pain to update between environments (doesn't do transformations, etc.)</li> <li>The reporting tool allows us to write .NET plugins to be run at certain times so I can modify the settings file on the fly</li> <li>We have access to IIS and can add settings / connection strings at that level</li> </ul> <h2>Goal</h2> <p>I'd like to: </p> <ul> <li>Simplify deployment by moving all connection strings &amp; settings to the IIS server-level settings. <ul> <li>even our developers have IIS available locally so this won't be a problem for them.</li> </ul></li> <li>Use the .NET plugin that I'm writing to connect to the server the app resides on and pull the connection strings and settings files.</li> </ul> <h2>Question</h2> <p>How can I access server-level IIS connection settings programatically from within a .NET class?</p> <h2>Notes / Things to Consider</h2> <ul> <li>This application does not use a web.config. <ul> <li><strong>EDIT:</strong> While apparently the app doesn't use a web.config, one does exist when the app is deployed, so theoretically I could access it via the .NET plugin.</li> </ul></li> <li>These are actually technically 5 different web sites. I'll be implementing the plugin the same way for each web site</li> <li>The IIS servers are only used for this purpose, so I'd like the settings &amp; configuration elements to be global across all of the web applications.</li> </ul>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload