Upgrading OpenRose in a Standalone Installation to v0.1.2-243

 


OpenRose is a FREE and Open Source Requirements Management Application / Tool. 

Download it from:

https://www.github.com/OpenRose

Upgrading OpenRose in a Standalone Installation 

Hello, welcome to OpenRose, a free and open-source requirements management application. Today, I’m going to talk about upgrading OpenRose on a standalone Windows installation.


The previous version, or the first version that was made available, was release v0.1.0.0. Now, we have the new version available, which is v0.1.2-243. This version includes some exciting feature enhancements, and I’m thrilled about the new capability that allows me to copy an entire project, item type, or item type with its hierarchical data included. Before we can use these capabilities, we need to upgrade to the latest version. In this video, I’m going to show you the simple steps to complete this upgrade.


Understanding the Installation


Let me start by opening the architectural diagram. This diagram shows that OpenRose has three components:  
  1. The Web UI, which allows users to connect through the browser.  
  2. The API interface, which communicates between the Web UI and the SQL Server database.  
  3. The SQL Server database itself.  

All three components are installed on a standalone computer. For this upgrade, we’re going to focus on the Web UI and API versions.

Now, let’s take a look at my current installation. My application is located on the C drive. The application is not running at the moment, but I can see the installation files. The zip files I downloaded in the past from the release page are no longer needed, so I’ll delete them.

In the current setup, I have:
  • API Version: v0.1.0.0  
  • Web UI Version: v0.1.0.0  

I’ve also downloaded the latest version of OpenRose into a temporary location on my C drive. The zip files are uncompressed into two subfolders: one for the API and one for the Web UI.


Migrating Configuration Files


One key step in the upgrade process is copying over the `appsettings.json` file from the previous version. This file is crucial for the following reasons:  
  • In the Web UI version, it defines the location of the API.  
  • In the API version, it defines the location of the SQL Server.  

This ensures smooth communication between the three components. To do this:
  1. Navigate to the API folder in the previous version and copy the "appsettings.json" file. Paste it into the latest API folder, replacing the existing file if prompted.
  2. Repeat the process for the Web UI folder, ensuring the new version has the correct "appsettings.json" file.


Finalizing the Upgrade


After migrating the configuration files, I’ll delete the old API and Web UI folders, as they are no longer needed. Then, I’ll copy the new API and Web UI folders into the application installation directory.

To start the upgraded application:
  1. Open the new API folder and run `OpenRose.API.exe`. This will launch the API service. Because it’s a local standalone installation, there’s no need to allow internet access. The API will also automatically upgrade the database schema if required.
  2. Open the new Web UI folder and run `OpenRose.WebUI.exe`. This will start the Web UI service, again without requiring internet access.

Verification


Now that both the API and Web UI are running, I can open the browser and connect to OpenRose via localhost. From the settings, I can verify that I’m on the latest version. Note: There’s a minor bug that causes the version display to exclude the build details. It would be nice to include this information in a future release.

All existing projects and data are accessible. I can explore the tree view to confirm that the upgrade didn’t affect any of the previous data.


Conclusion


These are the simple steps to upgrade your standalone installation of OpenRose. Thank you for your time, and I hope you enjoy the exciting new features in this version!




Comments

Popular posts from this blog

Introduction to OpenRose - Requirements Management

What is Requirement?

Details View - OpenRose - Requirements Management