Installing Aligned Elements Web Server
  • Elements SPA Installation
  • Preparing the Windows Server
    • Before you get started
    • Install and Configure SQL Server for Aligned Elements
    • Install .NET 4.8
    • Install/Activate the IIS
    • Enable ASP.NET 4.5/4.6/4.7
    • Optional: IIS Always running part 1
    • Installing Web Platform Installer and Web deploy
    • Install URL Rewrite Module
    • Install IIS Crypto to disable Weak Ciphers and Protocols
  • Deploying the Aligned Elements Web Solution
    • Install the Aligned Elements Web Server Package
    • Setting HTTP Strict Transport Security (HSTS)
    • Optional: Open Ports in the Network on Azure hosted Virtual Machines
    • Optional: Get a SSL certificate from Let’s Encrypt
    • Binding your SSL certificate to the Aligned Elements web site
    • Creating the „Temp“ and „Files“ directories
    • Remove stdole.dll from bin directory
    • Move ElementsSPA.xml from the "App_Data" folder to the "bin" folder
    • Add the Aligned Elements License Files
    • Set the necessary security permissions for directories
    • Optional: IIS Always running part 2
    • Install necessary Unicode Font
    • Install and Configure File Server Resource Manager
  • Configure Application Options in web.config
    • Configure Application Options in web.config
    • Set the Server and connection string
    • Always Require SSL
    • Referring to the Project Templates
    • Email Configuration
    • Word Add-in Configuration and deployment
      • Distribute an Add-in using the Office 365 admin center
      • Distribute the Add-in using sideloading for Windows
      • Distribute the Add-in using sideloading for Mac
    • Optional: Integration of the Aligned Elements Automation Tool
      • Importing Dashboards with Rename using the Automation Script
    • Optional: Enabling Active Directory Integration
  • Optional: Configuration of AI Features
  • Optional: Enable editing of Configuration Sections from the UI
  • Create an Initial User
    • Option 1: Aligned Elements Projects already exist
    • Option 2: New Web server, no Aligned Elements Projects exist
  • Upgrading the Aligned Elements Web Server
    • Upgrading a Server
  • Troubleshooting
    • Generic Server Error
    • Missing version of stdole.dll
    • Missing Dependencies for Txic.dll
    • Error shown: Could not load file or assembly “System.Net.Http”
    • 500 Internal Server Error
    • Error when trying to start application
    • The server is not starting after upgrading to v2.5 SP 4 Part 1
    • The server is not starting after upgrading to v2.5 SP 4 Part II
    • Load a project works but when clicking on a design Item, you are re-directed to the login
    • The application cannot connect to the license server
    • The urls in email notifications are incorrect/missing port information
    • Missing Font
    • Mismatch of server name between Windows-client and Web.
  • Cannot upload Templates
  • Running 'ElementsSPAPackage.deploy.cmd' closes the Command-Prompt window
  • Web.config Settings
    • Settings of the Web.config
  • Configuring Aligned Elements
    • Introduction to rvt templates
    • Type Info Element
    • Compulsory Trace Holders Element
  • Attributes Element
    • String Attribute
    • Enum Attribute
    • Rich Text Attribute
    • Dynamic List Attribute
    • Multiselect Attribute
    • Enum User Attribute
    • Date Time Attribute
    • Boolean Attribute (Checkbox)
    • Int Attribute
    • Double Attribute
    • Int Range Attribute
    • File Attribute
    • Table Attribute
    • Traced Objects Attribute
    • Approval Attribute
  • Trace Holders Element
  • Positive Cues Element
  • Validation Rules Element
    • Traced To Rule
    • Traced From Rule
    • Illegal Trace To Rule
    • Illegal Trace From Rule
    • Obsolete Linked Trace Rule
    • Suspect Trace Rule
    • Missing Execution In TestRun Rule
    • Incoming Suspect Trace Rule
    • Object In File Rule
    • Objects In File Up To Date Rule
    • Not Reviewed Rule
    • Object In Completed Signature Rule
    • Has Open Issue Rule
    • Related Attribute Value Rule
    • Date Overdue Rule
    • Executed From Last Revision Rule
    • Signature Missing Rule
    • Linked Attribute Value Rule
    • Objects In File Not Reviewed Rule
  • Attribute Workflows
    • Sign Action
    • Email Action
    • Set Attribute Action
    • Copy File Action
    • Lock Action
    • Unlock Action
    • Generate Object Action
    • Add PDF Footer
Powered by GitBook
On this page
  • Before you Start
  • Create a location for the manifest file
  • Perform the Deployment
  • How to create a shared network location
  • Windows 10 file sharing using basic settings

Was this helpful?

  1. Configure Application Options in web.config
  2. Word Add-in Configuration and deployment

Distribute the Add-in using sideloading for Windows

PreviousDistribute an Add-in using the Office 365 admin centerNextDistribute the Add-in using sideloading for Mac

Last updated 1 year ago

Was this helpful?

The preferred way of distribution is using the admin center see "". If this is not possible, use this approach of sideloading.

Before you Start

Make sure that you have received the Aligned Elements Word Add-In Manifest xml file from your Aligned representative.

Also make sure that all Word instances are closed on the machine before you start.

Create a location for the manifest file

Create a common file location on your network i.e. a shared network location that can be reached by a UNC path starting with \\.

Note! This means a network location in your network or on your computer. Not a location in the cloud, or Dropbox, or on Sharepoint etc.

If you are unsure about how to create a shared network location,

For more information: see reference:

Copy the xml-manifest to a common file location on your network.

Perform the Deployment

1. Open Ms Word, File=>Options=>Trust Center, click on Trust Center Settings…

2. Add the manifest file location/path to the trusted Add-in Catalogs by adding the path to the manifest location as an UCN path (starting with \\) to the Catalog URL text box and click Add catalog.

Note that you shall enter the path to the folder in which the manifest resides, not the part of the manifest file itself.

4. Open the developer Tab (or search for add-in)

5. Go to Shared Folder, select the Add-in and click Add:

How to create a shared network location

In this example we will create a shared network location on a personal computer using Windows.

Windows 10 file sharing using basic settings

To share files on a local network using the express settings, use these steps:

1) Open File Explorer in Windows.

2) Navigate to the folder you want to share.

3) Right-click on the folder, and select the Properties option in the context menu.

4) Select the Sharing tab and click the Share… button

5) Use the drop-down menu to select the user or group to share a file or folder. (In this example the Everyone group was selected.)

6) Click the Add button.

7) Under the “Permission Level” section, select the sharing permissions Read.

8) Click the Share button.

9) Confirm the folder’s network path that other users need to access the network’s content and click the Done button. Then click the Close button.

The path to the shared location is displayed under the folder name and starts with “\\....”

Distribute an Add-in using the Office 365 admin center
https://learn.microsoft.com/en-us/office/dev/add-ins/testing/create-a-network-shared-folder-catalog-for-task-pane-and-content-add-ins
see the end of this document for instructions.