Updating web.config file who is jason lewis dating 2016

For example, with the blob cache, the resource would need to only test that the changes required for blob cache are present, and not fail if another part of the web.config has been modified since the last update.

Currently IIS users get a web.config in the root of Drupal that tries to make Drupal behave well on IIS, but the files directory doesn't get the same treatment.

The reasons behind this was first consistency, I have seen many environments where server1 would have different settings then server2, etc.

Second, preventing manual changes (which may lead to the first issue).

Can you think of a specific scenario here that would warrant taking a different approach or doing something different with it?

The way the Web Config Modifications class works is it only pushes changes to the web.config file once.

and both seem to have created the same resulting file..

Is there a specific type of modification you want to make?

The problem with SPWeb Config Modification is that you will find that it won't enforce a desired state as well as DSC would when someone makes manual changes to a web.config file after the SPWeb Config Modification class applies its changes.

Just had a chat about this with my core architecture/planning guys for this, and they both tend to agree that we should avoid SPWeb Config Modification because it wont enforce the desired state in the config file themselves and it has a history of being unreliable.

As @ykuijs stated above the DSC resource will ensure the XML files always match the desired state and automates the changes for consistency, so if the only concern is making sure we tell everyone that you need to apply the settings to every server, then lets make sure we put that in the doco (in our doco so it hits the Power Shell module and the wiki doco) and make sure the example for the small farm matches how it should be done as well.

Leave a Reply