Hello,

Thank you for reaching out. We understand the frustration, and I appreciate you bringing this up. There have indeed been changes to the DevOps environment for creating non-connector items like automation scripts.

A full release post on the DataMiner Dojo is coming soon with more details. Additionally, new documentation and tutorials will be released shortly, and next month's Empower sessions will provide an in-depth walkthrough of these new features.

Key Changes
Previously, automation scripts were created as part of a full Visual Studio solution. Now, each automation script is represented as a single project. This change makes it easier to manage different DataMiner items within the same solution. In a single solution, you can now add multiple projects, including:

• DataMiner Ad Hoc Data Source Projects
• DataMiner Automation Script Library Projects
• DataMiner Automation Script Projects
• DataMiner User-Defined API Projects

…and more project types will be supported in the future.

For existing AutomationScript solutions, everything should continue working as before. The DIS Extension should still allows you to add new automation scripts to your existing solution, ensuring compatibility with your current workflow.

Getting Started
When creating a new Visual Studio project, look for the DataMiner Automation Script Project template. This will generate a new project in a new solution. The environment should automatically open a GettingStarted.md file, which provides guidance on how to use it—be sure to check that out.

For development, the biggest change is that you no longer need to work with the .xml file directly. Instead, you can focus entirely on .cs files, similar to standard .NET development. Any additional .cs files you create within the project will be compiled into a single automation script.

You can then add as many new projects as needed to the solution, each representing one of the supported DataMiner item types mentioned above.

Building & Publishing

• If you enabled DataMiner Package creation during the initial setup, simply compiling the project will generate a .dmapp file in the project’s bin folder.
• You can now upload items directly to the DataMiner Catalog from within Visual Studio by using the standard .NET 'Publish' action:
  • Via UI: Right-click the project and select Publish.
  • Via CLI: Run dotnet publish.
• If you're using GitHub for source control, the setup wizard allows you to add pre-configured CI/CD workflows (optional).

Important Note
'DIS Publish' is currently not working, but this should be resolved with a new DIS version expected today or early next week. Apologies for the inconvenience—we’re pushing this update as fast as possible!

Troubleshooting: Missing Skyline.DataMiner.Sdk
If you encounter errors stating that Skyline.DataMiner.Sdk cannot be found, the issue is likely related to NuGet source configuration. The new Skyline.DataMiner.Sdk (now the Visual Studio project type) relies on NuGet packages hosted on nuget.org.

To check if you have nuget.org enabled:

1. Open a command prompt and run:

   dotnet nuget list source
   

   Ensure the output includes:

   nuget.org [Enabled]
   

   Note: If this is the first time running a dotnet command, you'll see a welcome message first. Scroll down to check the actual command output.

2. If nuget.org is missing, add it using:

   dotnet nuget add source https://api.nuget.org/v3/index.json -n "nuget.org"
   
   

I hope this helps clarify the changes! Let me know if you run into any further issues.