116 reputation
2
bio website nerdfurio.us
location Minneapolis, MN
age 35
visits member for 5 years, 5 months
seen Jul 1 at 19:42

Jun
2
awarded  Student
Mar
17
awarded  Teacher
Jun
30
answered IIS7 URL Rewrite Rule not being applied at Website Level
Jun
29
asked IIS7 URL Rewrite Rule not being applied at Website Level
Jan
19
comment Setting up IIS7 to mimic a GoDaddy shared hosting plan
Sure, but I don't think they are seperate 'websites' in IIS terminology. As I'm sure you know, you can create an application or a virtual directory under a website. I'm not sure if you are using website in terms of IIS 7 nomenclature, or just a general term. There are differences between applications and Virtual Directories, but I guess I just may never know. I did find the specific problem I was having (root app had a config setting that was not overridden in the sub app, and the parent value was not valid), but it would be nice to setup my dev environment like my prod env. Thanks for trying.
Jan
19
comment Setting up IIS 7 to match a Godaddy shared hosting plan
Also, www.domain1.com will take me to the /www.domain1.com folder on godaddy, but Action Links created with asp.net mvc append the folder name in the urls generated making them www.domain1.com/www.domain1.com/hom which is not desirable, but I may not have an option there, other than to write my own link generator.
Jan
19
comment Setting up IIS 7 to match a Godaddy shared hosting plan
Your #2 option seems somewhat likely. If I have a website pointing at the folder /webRoot, and then I create an application inside that website pointing at /webRoot/www.domain1.com then I get some of the same behavior as godaddy. One big difference is in my configuration, the sub application doesn't get web.config values from the root application (website), but on godaddy, it does get those values. However, I'm sure it is not a virtual directory because it allows application level settings in the web.config.
Jan
19
comment Setting up IIS7 to mimic a GoDaddy shared hosting plan
If I was hosting this, that is what I would do, but it is not what GoDaddy seems to be doing. My sub folders do appear to be application roots, so I can have application level settings in my web.config, but it still seems to be aware of settings in the root containing folder. So I have /webRoot/www.domain1.com and when I navigate to www.domain1.com in my browser, it gets to the right spot, then Asp.Net MVC Action links will put the folder into the url giving me domain1.com/www.domain1.com/home. The thing that stumps me is the app root web.config seeing the web.config in the parent.
Jan
4
asked Setting up IIS7 to mimic a GoDaddy shared hosting plan
Jan
4
asked Setting up IIS 7 to match a Godaddy shared hosting plan