Last changes 12 months ago.
I need unity 2021 version.
Unity, can you update?
Last changes 12 months ago.
I need unity 2021 version.
Unity, can you update?
Hi, Iām sorry, I donāt know anything about this repo! It may be worth making a puplic post on the Unity forum in the Scripting section here: Unity Engine - Unity Discussions
Itās possible a Unity dev from the scripting team could see it and give more information.
Possibly, but unlike the posts in that section --this is not a technical question about Scripting. Itās a request to update a reference that we as developers, rely on as a form of documentation similar to and in close conjunction with the Scripting API docs in real world workflows. While itās apparently not managed by the documentation team (or anyone at the moment,) this is a rather special repo that seems to fall in a grey area. Where the Unity Scripting API documentation ends, the Unity C# Reference begins.
The original Unity blog announcement post authored by @Aras in 2018 states āC# reference source code is released under a license which only permits you to read the code, not modify it.ā (unlike other published Unity source repos) and that it was released in part to let us see āthe original comments and variable namesā (self documenting code / internal documentation made external since it is not distributed with the Editor in readable form) and "for the purpose of understanding or improving your projects made with Unity." (aligned with the purpose of the Scripting API documentation.)
Will you or @Aras do us a huge favor and spare a moment to forward this to the appropriate team / product manager, or someone that knows more? Or maybe @ali_mohebali knows who owns this or knows someone that could own this? (as Ali was so kind to spearhead managing similar, possibly related challenges with Unity Graphics repo. ) It would be greatly appreciated.
Not doing so will end up resulting (and likely already has resulted) in the same problem this repo was created to eliminate: people disassembling the Unity .NET assemblies into C# (legally) and redistributing them (illegally) without any of the helpful variable names and comments.
Expectation set in Unity Blog post, March 2018:
If you want to go a step further to enable Unity developers with excellent documentation workflows: integrate or link to the Unity C# reference directly in the Unityās Scripting API documentation. This could also be done for the packages documentation. Hereās an agile / scrum style user story:
"As a developer, when browsing the Unity Scripting API docs, I would like be able to view a particular class or method, and then click on a link that jumps directly to the C# reference code where that class or method is defined, to better understand how it works, how to use it, or reimplement its functionality if needed due to limitations or bugs. It will also help me provide better feedback to Unity about bugs or feature requests, and avoid unnecessary support requests that question limitations or bugs in the Unity C# implementation, requiring a Unity Tech QA specialist to inspect the C# source or consult a Unity Tech developer for clarification."
Example:
The Unity 2019.4 Scripting API documentation page for the Transform class here: Unity - Scripting API: Transform
Would have a link to or otherwise contain the reference code for the Transform class bindings in the 2019.4 branch of the Unity C# Reference here:
UnityCsReference/Runtime/Transform/ScriptBindings/Transform.bindings.cs at 2019.4 Ā· Unity-Technologies/UnityCsReference Ā· GitHub
(This should not remove or replace the functionality available on Github, however. Being able to see the commits and diffs on github is invaluable for us and should be preserved.)
Thank you for your consideration.
I dont have anythin to add that has not been said by landon so Im just putting my +1 here
I donāt disagree, Iād like the C# reference repo to be āliveā again and updated. But it has hit some sort of snag a year ago and has not recovered since then. All the relevant folks are aware of it, hopefully they will resurrect it to be āliveā at some point again.
Is there anything the community can do to provide incentive for the powers that be to resurrect repo? It would be great to have a living, breathing reference again.
We also routinely use the reference source to fix, understand or circumvent many issues locally, we really miss not having an up to date version.
If itās too much trouble to maintain every version, maybe only LTS versions could be updated?
I use the pre-release versionsā source code all the time to keep track and adapt to incoming changes to mainline versions. It has dramatically reduced issues for me when new Unity versions come around.
This situation with the reference source repo being abandoned is very disappointing, especially after Unity themselves asked MattRix to remove the repository with the decompiled source when they put their own repo online.
itās time to put the decompiled C# source back up and cause a nuisance. ĀÆ_(ć)_/ĀÆ
+11
bump:(
Iām actually wondering a bit why Unity Technologies isnāt a bit more straightforward with including the community in engine development. At least the C# part could start accepting pull requests with CLAs signed. Its not like other engines arenāt doing the same thing already. Its probably because they want people to pay extra for the source license, however I wouldnāt even know how much that costs right now (as its not openly stated).
Its interesting that even two years later there still isnāt a way to accept pull requests.
The whole legalese around this makes me wonder whether it would actually be illegal to binary patch the UnityEngine.dll that is shipped with a game or not. If it were illegal that seems a bit weird to me in the first place but then again Unity is a weird beast when it comes to its licensing.
well, thereās one way to find outā¦
@willgoldstone this is causing us some serious pain right now. The reference source hasnāt been updated for 16 months. Whatās happening here? Was the plans for having a reference repo killed off, or is there just some internal problem?
Alright! This took way longer than anyone would have liked (sorry), but the unity C# reference source code github repository should be up and running again, will the missing releases filled in. Itās at 2022.1 a13 on the main branch right now: GitHub - Unity-Technologies/UnityCsReference: Unity C# reference source code. and there are branches for other releases.
Woohoo! Thanks, youāre the best.
Henrik is, Iām just a local social media communicator device
[T]/ Praised be the Sun, you and Henrik then!
Amazing, thank you so much!