/
Changing Environments in NORMS Locally

Changing Environments in NORMS Locally

Changing Environments in NORMS is typically very simple to do, you simply go to the web.config file and comment out the current environment and uncomment out the environment you’d like to access. Each environment has a comment above it saying which environment it is. They may look different than the screenshots below if additional databases have been added to them

From here, you should be able to just build and run NORMS.

There does exist an issue for some developers where NORMS does not update what userId it is looking for when you change environments, resulting in the following error in Dashboard.aspx.cs

If that is the case for you, open your browse, right-click button and Inspect. When the inspector is opened, go to Application > Cookies > Select the localhost URL > Select the cookie and delete it. After that, restart your application.



 

Related content

How to get NORMS running locally if there are Oracle issues
How to get NORMS running locally if there are Oracle issues
More like this
How to Fix NORMS When It Displays Nothing When Running Locally
How to Fix NORMS When It Displays Nothing When Running Locally
More like this
How to run the Dev-EIG branch of NORMS locally
How to run the Dev-EIG branch of NORMS locally
More like this
How to Create a NORMS User for Development Purposes
How to Create a NORMS User for Development Purposes
More like this
NORMS - SNGI
Read with this
Where NORMS receives data from
Where NORMS receives data from
More like this