You're right that the full URL needs to be in the web.config. You have options though You can use a config transform to make the regular expression match the correct environment There doesn't seem to be any harm if you include all three URL rewrite rules in your web.config. It sounds like your environments are isolated so each environment would only ever match one of the rules.
That can clutter your web. Config, but not horribly I'd go with option 1. You can find information on config transforms here: msdn.microsoft.com/en-us/library/dd46532....
You're right that the full URL needs to be in the web.config. You have options though. You can use a config transform to make the regular expression match the correct environment.
There doesn't seem to be any harm if you include all three URL rewrite rules in your web.config. It sounds like your environments are isolated so each environment would only ever match one of the rules. That can clutter your web.
Config, but not horribly. I'd go with option 1. You can find information on config transforms here: msdn.microsoft.com/en-us/library/dd46532....
I would like to make a website always have www in the address, and enforce it via IIS rewrite. For example, test.com would become www. However this requires me to enter the full url of my website.
It will not work for development and staging environments that have URLs like www.test. Dev and www.test.stage. Is it possible to create an IIS Rewrite rule that will handle all of those cases?
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.