Separate Web.Configs is the way to go for disparate staging / qa / prod
servers. Maintenance is easy, and it's idiot-proof if you have
unknowledgable IT guys doing server updates. It also lets you really
control the environments if you have different db's / backends /
filesystems for these environments.
Where / If you present this information to the user is up to you -- in
general I think it's a bad idea since you're altering the output of your
application. If your users / testers are really getting confused, maybe
you need new ones =) If you absolutely must present it somewhere, I
suggest a login screen, or on the first screen the testers see.
Also, keep in mind that it's useful to have a global constant or enum that
describes the environment the server is in. This is helpful in logging,
errors, etc... If you do that, make sure you're only loading the
environment data once, and keep it in a constant / static variable so you
don't waste time on lookups while your app is running.
--------------------------------------------------------------------
This reply is provided AS IS, without warranty (express or implied).
--------------------
From: "paul reed" <pr****@jacksonreed.com>
Subject: Scrolling Warning on Bottom of Page
Date: Thu, 29 Jan 2004 11:01:03 -0800
Lines: 18
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Message-ID: <eg**************@TK2MSFTNGP09.phx.gbl>
Newsgroups: microsoft.public.dotnet.framework.aspnet
NNTP-Posting-Host: cs68201245-187.houston.rr.com 68.201.245.187
Path:
cpmsftngxa07.phx.gbl!cpmsftngxa06.phx.gbl!TK2MSFTN GXS01.phx.gbl!TK2MSFTNGXA0
5.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP09.phx.gb lXref: cpmsftngxa07.phx.gbl microsoft.public.dotnet.framework.aspnet:206138
X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet
Hello,
I have two environments, QA and Production. When the users are testing, I
want them to know they are in the QA environment versus the Production
enviroment. One solution would be to use the bottom area of the ASPX page
(not sure what it is called) that informs you what page is loading and then
it says Done upon completion. At some websites I see this used to present a
scrolling banner in that area. How does one do this...what is the property
(of the Page I guess).
Any other ideas on how to distinguish the two environments would also be
most welcome.
Regards,
Paul