This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
Hello again, I'm sure this has been answered somewhere in the past , or atleast there is a known GOOD solution for this... In our environement, we have two different Oracle servers, one for testing and one for production... So my question is... What's the easiest way to switch the models/solution from the testing phase over to production in terms of the connection properties of the Context??? Fortunately I build the Context in code so I was thinking that i could easiely switch the connection string over based on a Like I said , this should be a quick and easy one, as i'm sure that someone has had the same problem and come up with a good solution... :-) Thanks in advance, Kevin Orcutt GIS Developer/Consultant City of Cincinnati - Cincinnati Area GIS (CAGIS) (513) 850-1335 (cell) Kevin.Orcutt@cincinnati-oh.gov www.cagis.org |
|
|
Normally you would solve this using a config transform (see: http://blogs.msdn.com/b/webdev/archive/2009/05/04/web-deployment-web-config-transformation.aspx) and just maintain the associated test/release connection strings in the transform files to be subbed in depending on the environment. Alternatively you could always go old school Windows and maintain the connection string in the registry although I feel dirty even suggesting such a thing :) If you want to strictly maintain this in code I would just use the standard #if DEBUG #else approach and compile in debug for testing builds and release for production builds.
|
|