How to deploy MIUS Application

Owned by yiliu
Last updated: Oct 02, 2024 by Peng Li
3 min read

For all builds you must create PBI and task in the DevOps sprint, along with a branch from the task. The version numbers are tracked in the source and need to be merged correctly. Depending on the release type you may be required to merge to both Develop and Master.  Note: that in order to run side by side you must increment the the build number for each package even though code is the same.  


MIUS support three build configurations 

  • Debug - used for general development and to build the Development Click once package. Connects to the Development Oracle Database instance 
  • Acceptance - used to create a package for the acceptance build. This is an optimized package for release testing and does not support local debugging. Connects to the Acceptance Oracle Database instance 
  • Release  - used to create the production build.  This is an optimized package for release testing and does not support local debugging. Connects to the Production Oracle Database instance

Make sure the Publish version - Automatically increment revision with each publish is selected

Steps to deploy onto DEV server

  • Open the MIUS project properties window and click on the Compile tab, make sure the Configuration in both this tab and the toolbar solutions configuration are set. 
  •  In the publish tab set the following 
    • Publishing Folder -  C:\ClickonceDeploy\MIUS-DEV\
    • Installation Folder URL - http://tcappsmssdev/saf-sec-sur/4/mius-suam/
    • In the Install Mode settings - Click on the Options button and change the Product Name to MIUS - SUAM (DEV) 
    • Click the Publish now
      • The files will be placed into the Publishing folder location. 
    • Go to the click once folder defined above and copy the following files to \\ncrws535\e$\TCAPPSROOT\saf-sec-sur\4\mius-suam
      • MIUS.application
      • setup.exe
    • In the Click Once folder open the Application Files folder and copy the MIUS Latest Build folder  (ex. MIUS_1_5_0_16) to \\ncrws535\e$\TCAPPSROOT\saf-sec-sur\4\mius-suam\Application Files

Steps to deploy onto ACC server

  • Open the MIUS project properties window and click on the Compile tab, make sure the Configuration in both this tab and the toolbar solutions configuration are set. 
  •  In the publish tab set the following 
    • Publishing Folder -  C:\ClickonceDeploy\MIUS-ACC\
    • Installation Folder URL - http://tcappstest.tc.gc.ca/saf-sec-sur/4/mius-suam/  
    • In the Install Mode settings - Click on the Options button and change the Product Name to MIUS - SUAM (ACC) 
    • Click the Publish now
      • The files will be placed into the Publishing folder location. 
    • Go to the click once folder defined above and copy the following files to \\tctestmaster\tcappstest\saf-sec-sur\4\mius-suam       (NOTE: As of Oct 24, 2019, the  2016 server location is  \\tctestmasterx,  will probably be removed after migrations are completed)  
      • MIUS.application
      • setup.exe
    • In the Click Once folder open the Application Files folder and copy the MIUS Latest Build folder  (ex. MIUS_1_5_0_16) to \\tctestmasterx\tcappsroot\Saf-Sec-Sur\4\mius-suam\Application Files

Steps to deploy onto Prod server

  • Open the MIUS project properties window and click on the Compile tab, make sure the Configuration in both this tab and the toolbar solutions configuration are set. 
  •  In the publish tab set the following 
    • Publishing Folder -  C:\ClickonceDeploy\MIUS-PROD\
    • Installation Folder URL - http://tcapps.tc.gc.ca/Saf-Sec-Sur/4/mius-suam/    
    • In the Install Mode settings - Click on the Options button and change the Product Name to MIUS - SUAM
    • Click the Publish now
      • The files will be placed into the Publishing folder location. 
    • Go to the click once folder defined above and copy the following files to \\tcinfomaster\tcappstest\saf-sec-sur\4\mius-suam   (NOTE: As of Oct 24, 2019, the  2016 server location is  \\tcinfomasterx,  will probably be removed after migrations are completed)
      • MIUS.application
      • setup.exe
    • In the Click Once folder open the Application Files folder and copy the MIUS Latest Build folder  (ex. MIUS_1_5_0_16) to \\tcinfomaster\tcappsroot\Saf-Sec-Sur\4\mius-suam\Application Files
  • The secret need to be updated every 2 year now, (Next time is Oct. 1, 2026) 
    • update the secureconfig\secrets.config 
      find MIUSWinFormClientSecret, update to latest value
    • need to re-compile after the value changed.
    • release the whole package to server


When done push the application changes to the server and complete your pull request.   When doing a build for ACC or Prod I have been resetting the Publishing Folder and Installation along with the Options Product name back to DEV settings. The only thing I leave is the Publish Version.   


IMPORTANT! If after deploying, you install the application and get this error: "Strong name signature not valid for this assembly stdole.dll", this means that the instance of stdole.dll that the application is pointing to is unsigned. One way to figure out which stdole the application is pointing to when building is to show the detailed build details. In Visual Studio, go to Tools, Options, Project and Solutions, Build and Run. Under MSBuild project build output verbosity, select Detailed. Then build the solution again. Copy the output to your text editor and search for stdole.dll. You should see the path where it is looking for the dll. Go to File Explorer to see that file. It will likely be an unsigned file. Search through File explorer for a signed copy of the DLL. The signed file may be in C:\Program Files (x86)\Microsoft.NET\Primary Interop Assemblies. The signed DLL will be larger than the unsigned one (in my case, 32Mb vs. 16Mb). Copy the signed DLL into the path where the build is looking for it. Build again and follow the Publish procedures as above. The installation should run properly this time.