You can manually modify a .dmprotocol file generated from Visual Studio using DIS. However, uploading the modified .dmprotocol via the steps below will not automatically set the Visio file as the active one. To include a Visio file manually, follow these steps:

Embedding a Visio File into a .dmprotocol

1. In your Visual Studio Connector solution, open the protocol.xml.
2. Go to File > Save Compiled Protocol As... and save the resulting .dmprotocol file to a desired location.
3. Extract the contents of the .dmprotocol file (it’s a ZIP archive, so tools like 7-Zip can open it).
4. Inside the extracted contents, create a new folder named Visuals.
5. Add your Visio file to the Visuals folder and name it according to how you want it used:
   1. skyline_<connector name>.vsdx — if you want the Visio to be the Protocol default one shown with the protocol.
   2. <connector name>.vsdx — if you want it to be a custom Visio file that users can replace or select manually.
6. Repack the contents into an archive and give it the .dmprotocol extension.

You now have a .dmprotocol file that includes a Visio file.

Making the Visio File the Active Visio

If you need the Visio file to be set as the active one automatically upon deployment, you should create an application package that includes the protocol and Visio:

• Refer to the section Application package builder API in Creating application packages | DataMiner Docs.

• Use the Skyline.AppInstaller.AppPackage API, which provides methods to include a Visio file within a protocol.

• You may also need an install script to activate the Visio file upon installation.

Personally, I don’t have experience with this packaging method or the scripting required, someone else in the community may need to explore this further if more in-depth guidance is required.