2. ASPRunner.NET General questions
  3. [SOLVED]  Test Environment to Production
This topic is locked
[SOLVED]

 Test Environment to Production

 		9/27/2019 2:29:04 PM
ASPRunner.NET General questions
I
 i.NoLim author

Hello,
Whenever we start developing a new application we do it using a copy of the original DB. This TestDB will either be in the same server or in a different one. Once we complete testing, and know that everything works as it should, we create a new project or add a new connection and copy-paste events, custom CSS code, custom HTML code, field settings, etc. Essentially creating the same application twice. Is there a way to make the process of going from Test to Production easier?
Thank you!
T
 		Tim 9/27/2019

We create a new project, set up our main data connection to a test DB, and then publish it to a test web server. Then when we're ready to move to production, on the "Output" page of ASPR we create new data connections that point to the production DB. When then create a new FTP location to publish to the production web server and we select the secondary data connections (which you do as you FTP). ASPR remembers the FTP/data connection relationship. This allows us to use the same project and publish to 2 locations that point to 2 different DBs. We can easily switch back and forth from test and production within the same project.
Hope this makes sense and maybe helps. Redoing the entire project can be time consuming (I have done that as well) and it seems like things can be missed.
Tim
I
 		i.NoLim author 9/27/2019



We create a new project, set up our main data connection to a test DB, and then publish it to a test web server. Then when we're ready to move to production, on the "Output" page of ASPR we create new data connections that point to the production DB. When then create a new FTP location to publish to the production web server and we select the secondary data connections (which you do as you FTP). ASPR remembers the FTP/data connection relationship. This allows us to use the same project and publish to 2 locations that point to 2 different DBs. We can easily switch back and forth from test and production within the same project.
Hope this makes sense and maybe helps. Redoing the entire project can be time consuming (I have done that as well) and it seems like things can be missed.
Tim



Yeah, but you will still need to work on each of the tables from the new connection individually. You still have to go into designer and modify the add/edit/view/etc pages, copy-paste events, etc. I wish there was a way to "rename" the tables by pointing to the new tables and inherit all the settings, specially since they will have the exact same columns/fields.
T
 		Tim 9/27/2019

I'm not sure I follow. I do not have to do all of that. Maybe the difference for me is that I have 2 instances of SQL server and my test DB is on the it's own instance.
Just to be clear, I'm not talking about adding a new connection on the "Tables" page of ASPR, rather on the "Output" page. It's not really a "new" connection, it just points to a different location for the same connection. Of course, all tables and columns need to be the same between the 2 locations.
Anyway, I'd be curious to hear what others do as well.
Have a great weekend!

Tim
I
 		i.NoLim author 9/27/2019

Oh! I think I understand now. Yeah, let me try that. Thank you!
Related question, so when you are making updates to the application and you don't want affect the one that's on production you simply delete the BD connection from the output page right?
jadachDevClub member 9/27/2019

If your test db is identical to your prod db, simply change the connection when testing. Once it is good to go, reconnect to prod and upload your files.
I
 		i.NoLim author 9/27/2019

Thank you so much for your prompt response.