Comparison of the advantages and disadvantages of Rider and Visual Studio 2019

This article mainly summarizes some VS usage skills and comparison with Rider.
Now there are too many Riders. In fact, VS is not bad. Only the best for you is the best.
The difference between the two

vs advantage

1. The most obvious difference:

VS has Chinese, Rider has no Chinese. For novices, VS is definitely better than rider in this respect. It will be very slow to learn without Chinese. So if you are a novice, it is recommended to use VS instead of Rider, otherwise you will sometimes be blinded and find that you are so versatile. .
Insert picture description here
Excellent plug-in (to bridge the gap in ease of use)

Rider advantage

1. The power of quick search (VS has been implemented)

VS search is difficult to use, especially the search in the resource management window. It cannot filter useless information, and it cannot quickly jump to the next one, nor can it be classified according to class, method, etc. (Rider search can be done)
Insert picture description here
Rider
twice Shift can call up the search, which is also my favorite function. I personally think that there is a huge gap between the search of VS and the search of VS. Rider's search is really easy to use.
Filter useless conditions, and can also be classified.
Insert picture description here
I hope VS can quickly improve the search, or produce a search plug-in similar to Rider (Resharper can, but VS is very stuck. If the computer is good, you can consider)
Update : VS Ctrl T can realize Rider Category search function

2. Small size

Rider is much smaller than VS. For those who don't have enough C drive space, uninstalling VS can free up a lot of space.

3. Better compatibility with Unity

You can directly see in the code which objects use this script, or reference this field and attribute.
And the compatibility of the shader is proved. If you are a Unity developer and choose Rider to develop, the efficiency will be greatly improved (provided that you are familiar with Rider)
Insert picture description here

4. Quickly build a variety of interfaces, classes, templates and easy to use

Directly
Insert picture description here

Insert picture description here

to sum up

VS is suitable for novices, and many functions of Rider also have VS, but they are not powerful enough. Rider is suitable for senior and experienced Unity developers, and can greatly improve the development efficiency of Unity (provided that you are familiar with Rider),

After my test, Rider and VS are familiar with the speed. The former can reach the level of normal use in about a month, and the latter can be used on the touch. It is recommended to summarize the functions first and then slowly get familiar with Rider.
If you are a novice, it is recommended to use VS first. After you are familiar with the basic functions, you can consider transferring Rider and map your functions in VS to Rider, such as finding all references, viewing definitions, viewing error windows, Git, etc.

Using Rider does not mean giving up VS, and using VS does not hinder the use of Rider. It is best to use the two in rotation. The main functions are the same. If you want to have the efficiency of Rider, you have to bear the threshold of use. VS is very convenient and efficient. It's not low, Rider can do all VS, it depends on personal preference.
I like VS because the Chinese is very direct. When Rider releases Chinese, I will return to Rider to see

Guess you like

Origin blog.csdn.net/euphorias/article/details/105230439