@kagikn I do. If it's just small fixes (aka bumping up the third number in the version), go ahead. It works by merging dev_v2 into master and pushing a new tag with the version number (e.g. "v2.10.3"). The build system will do the rest and create the release on GitHub automatically.
Since some people cannot seem to read the description, let's point this out again:
Community Script Hook V .NET DOES NOT NEED AN UPDATE AFTER A NEW GAME VERSION CAME OUT. You ONLY need to update Alexander Blade's Script Hook V (once he has published an updated build).
@Cyron43 and @ImNotMentaL This slipped into the v2 branch by accident. It's fixed in v2.9.2, sorry for the incovenience.
@MAFINS I have it open in VS2013 without issues. It checks for the latest VS2013 version though, so make sure you have Update 5 installed, or alternatively open the .sln in a text editor and remove the "MinimumVisualStudioVersion" line.
Do NOT put ScriptHookVDotNet.dll into the scripts folder. Just don't.
@whoodini91: You can ignore it. It contains XML documentation for developers.
2.6 is pending approval. Cheers.
@scalliano: The WASTED message staying was a bug in NativeUI, not Scripthook V .NET. Update your NativeUI binary to fix it: https://github.com/Guad/NativeUI/releases.
This project is open source and was driven by the developer community from the start. I merely provided the base to load and execute .NET code inside the game and get access to the native scripting API. Anything else (the entire API exposed to scripts, euphoria, etc.) was implemented by other people from here. I don't have much free time, so I maintain the project and will make sure the base continues to work, but anything from there on has always been the responsibility of the community and so is updating if something in it breaks. Anybody is welcome to contribute after all. That's the beauty of an open source project.
@Assmandu: Correct. The ASI is all you need.