Hello,
When we install Web Deployment Projects ( WDP ), we also have an option to use it inside VS 2008. By selecting Property Pages we are presented with several options for configuring compilation options.
The Use IIS Metabase Path for Source Input option on the Compilation tab of the Property Pages dialog box is important if you want to use a web deployment project for an IIS-based website containing subsites. Basically, when using aspnet_compiler.exe, it compiles the complete directory structure, including all the subdirectories of the source directory. If a website in IIS contains subsites with separate web.config files and global.asax files, this will result in compilation errors. Using the Use IIS Metabase Path for Source Input option, you can specify the exact IIS metabase path for compilation (such as /LM/W3SVC/1/ROOT/ProAspNetWeb, where ProAspNetWeb is the name of the virtual directory), excluding any subapplication configured in IIS.
I don’t quite understand the point the above quote is trying to make!
Before I can ask my main question ( C and D ), I need to understand the following facts:
A)
…is important if you want to use a web deployment project for an IIS-based website containing subsites.
Is the IIS-based website containing subsites already present when we want to deploy to IIS our project?
B) Is by “subsites” the quote referring to virtual directories functioning as applications ( we created these virtual directories by right clicking a web site and selecting Add Application ( in IIS 7 ))?
C)
If a website in IIS contains subsites with separate web.config files and global.asax files, this will result in compilation errors.
Assume web site has a subsite named A ( this subsite has its own web.config file and we access it via http://localhost/A), but project we want to deploy is contained inside folder named B ( http://localhost/B ).
Now why would deploying B to web server cause compilation error?
D) And even more confusing is how exactly does IIS Metabase Path for Source Input option help us with this?!
BTW – what is IIS Metabase Path?
thanx