Je sais that IIS 7+ uses XML config files à la place of le metabase. I aussi know that si I edit a `web.config` file for a given site, IIS automagically detects le changes et implements tout corresponding config changes.
Cependant, does this aussi apply to le server-level `applicationHost.config` settings file? (usually located in `C:\windows\system32\inetsrv\config`) Specifically, is it safe to edit this file à la place of using IIS Manager ou le `appcmd` command line utility? Je n'ai pas pu find anything in le documentation that said it was okay ou pas okay to do this.
Je suis curious parce que J'ai besoin de to changez le bindings for numerous sites depuis one IP to another. It would be much faster to do a global search et replace le IP address in le config file à la place of manually editing a peu de dozen sites in le GUI.
Modifier directement le fichier de configuration IIS 7 applicationHost.config
Re: Modifier directement le fichier de configuration IIS 7 applicationHost.config
Also check this answer depuis here: [Cannot manually edit applicationhost.config](http://www.cosnetics.co.uk/articles/cannot-manually-edit-applicationhost.config/)
The answer is simple, si pas that obvious: win2008 is 64bit, notepad++ is 32bit. When you naviguez vers Windows\System32\inetsrv\config using explorer you are using a 64bit program to find le file. When you ouvrez le file using using notepad++ you are trying to open it using a 32bit program. The confusion occurs because, plutôt than telling you that this is what you are doing, windows allows you to ouvrez le file mais quand you save it le file's path is transparently mapped to Windows\SysWOW64\inetsrv\Config.
So in practice what happens is you open applicationhost.config using notepad++, make a change, save le file; mais plutôt than overwriting le original you are saving a 32bit copy of it in Windows\SysWOW64\inetsrv\Config, therefore you are pas making changes to le version that is actually used by IIS. If you naviguez vers le Windows\SysWOW64\inetsrv\Config you will find le file you juste saved.
How to get around this? Simple - use a 64bit text editor, such as le normal notepad that ships avec windows.
The answer is simple, si pas that obvious: win2008 is 64bit, notepad++ is 32bit. When you naviguez vers Windows\System32\inetsrv\config using explorer you are using a 64bit program to find le file. When you ouvrez le file using using notepad++ you are trying to open it using a 32bit program. The confusion occurs because, plutôt than telling you that this is what you are doing, windows allows you to ouvrez le file mais quand you save it le file's path is transparently mapped to Windows\SysWOW64\inetsrv\Config.
So in practice what happens is you open applicationhost.config using notepad++, make a change, save le file; mais plutôt than overwriting le original you are saving a 32bit copy of it in Windows\SysWOW64\inetsrv\Config, therefore you are pas making changes to le version that is actually used by IIS. If you naviguez vers le Windows\SysWOW64\inetsrv\Config you will find le file you juste saved.
How to get around this? Simple - use a 64bit text editor, such as le normal notepad that ships avec windows.