Forums before death by AOL, social media and spammers... "We can't have nice things"
|    comp.databases.paradox    |    To crash or not to crash, asks Borland    |    9,834 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 8,302 of 9,834    |
|    Larry DiGiovanni to All    |
|    Re: isolated testing environment    |
|    19 Mar 07 19:56:10    |
      From: nospam@nospam.com              My preference has always been to make the switch for DEV/TEST/PROD occur       outside of the application. If the application is responsible for       explicitly selecting it's own environment, there's the potential for stuff       to slip through testing and only rear it's head in production. I use a       directory structure like what Anders posted.              I make sure the .net files are different between environments. Someone       working in DEV should not be able to see PROD data whatsoever.              I do try to make it obvious when pointed to the non-production environments,       so folks will know what they're looking at.              --       Larry DiGiovanni              --- SoupGate-Win32 v1.05        * Origin: you cannot sedate... all the things you hate (1:229/2)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca