I saw a conversation in Slack that included Kelly about linking the API documents that we have on our local drive to Visual Studio. It would help the newer script writers if someone would document this as an aid to scripters. - And, if the Sansar team feels this is beyond their scope, perhaps a user-created document would be appropriate. Maybe even a video tutorial.
Date
Votes
6 comments
-
Gindipple Click Add Reference in your solution, select Browse, go to <your_sansar_install_path>\Sansar\Client\ScriptApi\Assemblies
Add the 2 .dll files there.
For the help on them right click on one of them and select View in Object Browser, then just follow the paths to what you want just like you would in an HTML viewer
-
Ethos Erlanger For the record, one out of two of the DLL became corrupted after a recent update. So, the lack of documentation is now a moot point.
-
Ethos Erlanger Let me clarify the need for this documentation. I have VS 2017 installed and would appreciate having the Script API linked to this most current version of Visual Studio. Is a repair of the API on the roadmap?
-
Gindipple The documentation is trivial for this process. See my first reply.
Fixing the assemblies that were broke about a month ago is the outstanding issue.
And I can't even get a soon(TM) on that lol
I think they like them broke so that only elite coders can still code.
-
Ethos Erlanger @Gindipple, I could not put my finger on the feeling I was getting from this issue, but now I know what to call it. I must be one of the "un-elete". :-)
-
cara Hi Ethos, thanks for the request. We are adding a guide for VS 2013 and 2015 on the roadmap, right after the next release's documentation lineup.
We are looking into the issues related to VS 2017.
Please sign in to leave a comment.