Description
Have a fantastic idea for a new skill in ARC to publish in the Technology Store? This is the tutorial which explains how to create a skill for ARC. This tutorial will help you create an example skill with two buttons which move a servo to get you started.
Overview
Summary
In this tutorial, we will cover the following steps...
1) Download and install the latest ARC
2) Download and install Visual Studio
3) Create a new skill plugin Visual Studio project in ARC
4) Make your skill do amazing stuff
5) Upload the skill package to Technology Store and share with the community!
Skill Design Tip
Skills can communicate with each other. This allows your skill to receive commands from other skills, programmatically. The way skills interact with each other is with scripting ControlCommand() script functions. To respond to ControlCommand() requests, your skill will most likely contain SendCommand() and GetControlCommands() override listeners. These will allow other skills to send instructions to your skill. Keep this in mind when designing your skill, as it's discussed in this tutorial.
Sorry but can I ask you something why I didn't see the ARC library when I added visual studio even though I set up the C ++. DLL library and there's another way to execute it and send / receive console in out but I don't know how to do it with EZ_builder?
Hello, I am trying the tutorial to get the robot to speak. I am using Visual studio. Currently, the sound is output from the pc instead of the robot. Is there a code I can attach so that the sound comes from the robot speakers instead of the pc?
for either playing audio (ie mp3) or text to speech.
Joinny, you have to add the referencing by following the instructions in this tutorial. They are outlined with step by step to easily follow. Click add references, and browse to the appropriate files as directed in the tutorial. I can’t write anything clearer in response. The step to add references is incredibly clear but you’re skipping it.
.
Are you planning on making a skill control to do this? You wrote the question in the skill control thread in a comment - I'd like to make sure your question is in the right place to help you out.
To begin, I would recommend starting with servo Script control so you can make the serial bus protocol work - then consider making a skill control only if you're planning on distributing the effort to others: https://synthiam.com/Products/Controls/Scripting/Servo-Script-19068
OS is Windows 10, .NET 4.8 or newer, Visual Studio Community 2019.
ill look into it a bit further and see if we can find a better way of detecting
It's easy to find the Visual Studio 2017 and up:
Microsoft:
https://github.com/Microsoft/vswhere/wiki/Find-MSBuild
Some quick c# code to use with .NET:
https://github.com/ppedro74/Utils/blob/master/FindVisualStudio/Program.cs
Code:
https://devblogs.microsoft.com/setup/vswhere-now-searches-older-versions-of-visual-studio/
apparently with the above individual, the registry didn’t work either. I’ll have to combine a few methods.
everything looks simple from the outside - until you have a hundred thousand+ installations of your software. That’s when you run into things like this lol
I agree sometimes the things go out of script easily.
I avoid going through the registry keys, unless is recommended by the vendor.
A lot of people blame the changes (keys, entries are renamed etc), but, that is normal if I own my product is my business and is part of the software evolution. Some products you can break the support contract agreement if you query directly the database, or if you look elsewhere outside of the public API.
Is true story some years ago a "rogue" developer on my team released a Sharepoint integration using a mix of APIs and database queries, everything worked well with multiple clients, until one day the Microsoft Black suits visit one of the customers to follow up on an unrelated support ticket, and they basically used "unsupported" card and left the client hanging, and we had problems too, unfortunately the Rogue developer went to another galaxy ... and the team suffered the consequences.
That does not mean I'm not tempted to do it...
I used the vswhere before and I would say is almost 99% bulletproof, is used with Xamarin, NVIDIA, Intel setups. If you add vswhere.exe to your project (nuget package) you cover scenarios where the tool is not present or have been deleted (broken uninstalls).
The other fallback could be ask the user the visual studio version.
The other reason to avoid registry is due to Visual Studio uses a private exclusive registry keys to store more stuff:
http://www.visualstudioextensibility.com/2017/07/15/about-the-new-privateregistry-bin-file-of-visual-studio-2017/
So the things are getting more complex.
The above post is only part of the "Full solution" for example I have one setup with visual studio 2017 c# installed and Visual studio 2019 with Python and C++, vswhere will return 2019 version, but my c# is done with VS2017.
If you are generating customized vs version project files, maybe a fallback (ask the VS version) will cover more bases.