When you look at unity inside the API, is not sometimes tracked one or two steps to hit the DLL file will not go down? It's very unpleasant.
I often encounter this kind of problem. This is someone else's business engine don't want you to see the underlying code, so worry not.
However, today I finally have a way to solve the problem. That is to use the anti-compile DLL file! Simple, rough. But in order to understand the underlying structure, this is also a way to do oh.
Ok! Long winded, let me take you into today's theme it.
1. First download. NET Reflector 8.3.3.115. (If the link fails, please let me know.) There is also a plugin can export CS file)
2. Double-click Install ReflectorInstaller.exe.
3. Open. NET Reflector 8.3.
4. Click File--Open Assembly
5. Position the location to your Unity installation location, such as E:\software\Unity\Editor\Data\Managed. You can select Unityengine.dll,unityeditor.dll etc DLL file, click Open after your directory
http://blog.csdn.net/zhaoguanghui2012/article/details/47804423
This is the original address.
(go) use. NET Reflector to view DLL files inside the Unity engine