Web deployment task failed
-
During the publishing of my web application using VS 2010 I get the following message, Web deployment task failed. (There was an error reading IIS configuration schema from 'C:\WINDOWS\system32\inetsrv\config\schema\'.) Can anyone please advice me the resolution? regards Sultan
-
During the publishing of my web application using VS 2010 I get the following message, Web deployment task failed. (There was an error reading IIS configuration schema from 'C:\WINDOWS\system32\inetsrv\config\schema\'.) Can anyone please advice me the resolution? regards Sultan
-
During the publishing of my web application using VS 2010 I get the following message, Web deployment task failed. (There was an error reading IIS configuration schema from 'C:\WINDOWS\system32\inetsrv\config\schema\'.) Can anyone please advice me the resolution? regards Sultan
I've never used the web deployment, well maybe during VS2005 but that was almost 10 years ago. Back in the old days, you use to be able to setup your IIS 5 / IIS 6 web server using software, that can read and write the IIS website metabase config files in the windows operating system. Very easy to read and write too using managed code or c++ on Windows XP. Since IIS 7, the web config is now written to the web.config file in your project folder. So you just copy the project to your server, and just point IIS 7+ folder path to the web site project folder. Now you click on the bind link to test the bind to the server. I'm pretty sure that the feature your speaking about is legacy, and I'm not really sure why it's still there. Some folks still use IIS 5 and IIS 6 to host web sites on, which is not very secure in today's world. The Application pool is not written to the web config, so you have to program that by hand. If your having trouble programming the app pool, or setting permissions for the app pool in the website folder, That's another complex project. I like the new system, because deployment time is much faster now. Sample system.webServer. This sample programs the default page name, sets the maximum upload size, and sets compression for static and dynamic pages to TRUE. You can do much more, but this works for me on my projects. The rest of the settings are default settings.
I don't know of too many people that use the feature in question. But you have to have the IIS 6 metabase compatibility turned on for Windows Vista, 7 and 8 in order for it to work I think. http://www.iis.net/learn/manage/managing-your-configuration-settings/metabase-compatibility-with-iis-7-and-above[