Answers
Jan 11, 2008 - 11:36 AM
David,
The short answer is "no", you can't change this behavior...it's part of the CLR, although I can't cite the specific reasons for this, I do remember seeing mention of it in one of the CLR books I started reading.
You say that you need to preserve the actual page name...what's the reasoning behind that? I guess I'm hoping to help you out a bit more, and if I have an understanding of the scenario, I might be able to toss you some ideas that could get you where you need to go.
Let me know if I can help,
Ric
The short answer is "no", you can't change this behavior...it's part of the CLR, although I can't cite the specific reasons for this, I do remember seeing mention of it in one of the CLR books I started reading.
You say that you need to preserve the actual page name...what's the reasoning behind that? I guess I'm hoping to help you out a bit more, and if I have an understanding of the scenario, I might be able to toss you some ideas that could get you where you need to go.
Let me know if I can help,
Ric
Jan 14, 2008 - 12:52 AM
Thanks for the response Ric.
The reasoning for this is a web analytics tool that we use on the site that distinguishes between lower case and upper case and right now it's not measuring the pages correctly, since all the post backs are lowercased.
I can fix it by forcing lowercase on all page name for the analytics, but i thought it was possible to avoid this behaviour in asp.net.
The reasoning for this is a web analytics tool that we use on the site that distinguishes between lower case and upper case and right now it's not measuring the pages correctly, since all the post backs are lowercased.
I can fix it by forcing lowercase on all page name for the analytics, but i thought it was possible to avoid this behaviour in asp.net.
Add New Comment