Regular expressions enable people to locate data inside of strings based on pattern matching. Regardless of the programming language, regular expressions (RegEx), are quite useful and powerful, though often disliked. That’s because they have a reputation for being difficult to work with.
If you’re using Rider to code regular expressions, it’s not difficult at all! In this post we’ll take a look at how you can effortlessly write regular expressions with Rider.
Readability is key for producing quality code. Rider displays metadata about the arguments for many types of methods, and that includes methods on objects that compute regular expressions.
As you can see in the following example, Rider lets you know which argument is the pattern, options, and matchTimeout. Otherwise, it’s difficult to remember which arguments of a method are which, making Rider’s parameter hints quite helpful.
On April 6th, 1992, Microsoft released Windows 3.1 to the world! Meanwhile, in 2020, the world is struggling and trying to deal with a global pandemic. I hope everyone is able to stay at home, safe and healthy. Please take care of yourselves. Hopefully this newsletter helps alleviate some stress by providing fun & exciting tech info.
With today’s technologies and tools, building software is no longer the complex craft of the past. Anyone with access to a computer can now write code in their favorite programming language or IDE. Furthermore, combining multiple different technologies in the codebase is the norm when designing software.
However, as the complexity of the code increases over time, so does the importance of keeping an eye on the overall quality of the code. But what exactly do we mean when talking about code quality? Which quality attributes should we keep an eye on? How can we automate the process of static code analysis so that we can quickly understand where we stand in terms of quality and technical debt?
In this presentation, we’ll discuss the science and technology related to static code analysis, so that you may use sound metrics to decide how to tackle technical debt. Whether you’re building software alone or collaboratively, this presentation will provide strategies to keep your code quality where it should be so that you may quickly implement features in your application.
It seems that a common problem among profiling tools (including ours) is that they require too much effort from a developer. Profiling currently is seen as some kind of a last resort for when something has gone horribly wrong. The use of profilers is very episodic and chaotic, and it’s quite often ineffective because you simply can’t be an expert in a tool you use only once every six months. We find this kind of sad because we strongly believe that regular profiling is essential for product quality.
That being said, is there any solution? Well, our answer is “yes,” but with some caution. Since we can’t force people to use profilers all the time, the only possible solution is to make issue analysis automatic and move it as close to the user as possible. So, without further ado, we’re pleased to introduce Dynamic Program Analysis (DPA)! Continue reading →
There are quite a number of build systems for the .NET ecosystem. All of them have proven to improve lives of many developers working in build infrastructure. However, many of them follow a scripting approach, which inevitably requires lots of efforts to bring back common IDE features like code completion, refactorings, or debugging. NUKE is different in that it doesn’t step out of boundaries of conventional frameworks, and thus leaving all the essential tooling intact.
In this talk, we will provide a short introduction to build automation, how NUKE works, and look at some of the design decisions along the way of building it. We will also briefly discuss extension points in Rider that allowed the delivery of an even more integrated experience, for instance by adding custom run configurations, executing targets via Alt-Enter, viewing a live graph of target dependencies, and more ideas yet to implement.
Join this presentation if you’re interested in build automation, enhancing frameworks with more IDE integration, or just if you’re a fan of Rider, ReSharper (or TeamCity)!
The Rider team has been hard at work, and we are happy to announce that Xamarin.Forms XAML Hot Reload is coming in Rider 2020.1!
In this post, we’ll see how this makes developing our Xamarin apps more enjoyable. We’ll also walk through some of the limitations of XAML Hot Reload, as well as list some of the XAML fixes and improvements in Rider 2020.1.
Shipping is a feature! At JetBrains, we love to ship software. We like it so much we release EAP versions of software in addition to stable releases. Whether it’s to the cloud, on an in-house networked server, or elsewhere, your software has to live somewhere. Rider’s excellent publishing features can help you get it there.
Regardless of the type of app, Rider can get it published! Here are the options available for publishing software:
IIS: Microsoft’s Internet Information Server (and compatible, like Azure WebApps when not using the Azure Toolkit for Rider). This web server is still quite popular and serves millions of websites and software on the web.
Custom Server: You can deploy Rider projects to servers like Apache, Nginx, or others.
Custom folder: Sometimes you need to deploy to a folder where users can run the app or copy it locally.
Azure and AWS: Put that software in the cloud!
The type of software you build often dictates how and where you publish. For example, a desktop app isn’t a good candidate for publishing on IIS or the cloud (exceptions for deploying a downloadable package only). Desktop apps and apps that aren’t web apps work well in folder deployments. Most web apps need a web server, though nowadays ASP.NET core is deployable through self containing modules.
We’re always excited to ship Rider test runner updates to our early adopters. Developers running the latest Rider 2020.1 EAP may have noticed some positive changes to the unit testing window and the test runner.
Let’s walk through some of the more notable enhancements: reworked toolbars that make working with sessions and individual tests easier, a grouping of various test statuses that help spot which tests need some more attention, and various other updates. Here we go!
All of our IDE’s are built on the same core IntelliJ IDEA Community Edition. This means that when we improve one IDE, our other IDE’s usually also benefit from our improvements. Rider is no exception! I recently reached for DataGrip, our amazing database administration tool, only to remember that Rider has many of the same features.