Hello! The seminars are very close and we are happy to take on board yet another excellent speaker: Mikhail Shcherbakov
And for those who do not know, I repeat: April 15 in St. Petersburg , April 22 - in Moscow , April 29 - in Omsk , May 13 - in Yekaterinburg and on May 20 - a series of CLRium # 3 seminars will take place in Novosibirsk .

Last year we talked about okakohakerkih things - parsing .NET memory of heaps, casting between which casting is impossible ... They divided the current stream into two ... Talked about the core of the new .NET Core and tried to understand what we need (and whether?) Roslyn
')
In the same year we will talk about something else. About purely practical useful things that you probably didn’t know before, but in which there is tremendous strength and power. About changeable programming languages, performance and cross-platform GUI development. What does “about changeable” mean? This means that the language can change its own syntax.

As before, we will have:

• The deepest, selective reports on rarely disclosed issues
• We will only talk about what you probably didn’t know before
• Maximum useful reports that will strengthen you as a specialist
• Almost all reports - from 1.5 hours. What will allow speakers not to save and tell all that they know

Note to Nitra and Nemerle: these two opensource projects are now being developed within the walls of JetBrains.
Reports:

• Mikhail Shcherbakov (IntelliEgg) What vulnerabilities are found in the .NET Framework
• Andrey Akinshin (JetBrains) Iron Timers
• Vlad Chistyakov (JetBrains) Nemerle is the most powerful alternative to C # on .NET
• Vlad Chistyakov (JetBrains) Nitra - a tool for developing programming languages ​​and DSL
• Stanislav Sidristy (Luxoft) JetBrains Rider IDE: Java IDE for cross-platform .NET
• Stanislav Sidristy (Luxoft) Automation of testing WPF / WinForms applications through integration into the process
• Andrei Karpov (Program Verification) What does a static analyzer know that you don’t know
• Sergey Vasiliev (CoPro Ver) Experience of using 'Roslyn' in the development of a static code analyzer
• Nikita Tsukanov Cross-Platform UI Application Development (Perspex UI, Eto.Forms, Xamarin Forms)

We have an excellent site where you can read about all the speakers, and about all the reports. Come, study, take tickets: http://clrium.ru/

And under the cut, we made video invitations for you =)

Andrei Karpov - What does a static analyzer know that you don’t know
Technical director of the company “Program Verification LLC”, developing the PVS-Studio static code analyzer. Since no one except programmers is able to explain what the company does and what PVS-Studio is, Andrei is also part-time head of the marketing department. He was at the beginning of the creation of the PVS-Studio analyzer and made a great contribution to its development and promotion. He is also the author of a huge number of articles related to C ++ programming and the subject of static code analysis. At the moment, Andrey's main activity is to popularize the static analysis methodology among C ++ and C # programmers.

Static analysis is in vain underestimated by programmers. It is also important, such as version control system. A static analyzer often sees what the programmer does not see. What the programmer does not see can be divided into 2 groups: imperceptible typos and problems that the programmer does not even know. Consider them in more detail and with examples. What is the difference between static analysis tools and other tools. What does a static analyzer know, which, for example, does not know the dynamic one. Static analyzer is the only one who knows about test errors. About the importance of regular use of code analyzers



Sergey Vasiliev - Experience using Roslyn in the development of a static code analyzer
Programmer of the company “Program Verification”. Participates in the development of the PVS-Studio code analyzer. He stood at the origins of creating a new kernel of the PVS-Studio analyzer, capable of checking C # code. Now he is developing the analyzer and creating new C # -diagnostics

What is Roslyn? Use 'Roslyn' to parse code written in C #. A little bit about static analysis, how we used 'Roslyn' when developing PVS-Studio and what came of it

Contacts

• sunex.development@gmail.com
• +7 (921) 948-16-08