About the Author

I’m an IT businesses entrepreneur, a software developer, and a huge technology fan. My company went to market in 1990, focused mainly in custom software development. We started with COBOL as our main programming language, and we’ve evolved along the years up to .NET and Microsoft Office technologies. We recently started to adopt some of Microsoft’s multiplatform technologies, such as .NET Core. Throughout these years, I have been researching cutting-edge technologies and searching for new tools that can help us automate processes for our products’ development lifecycles.

In 2010, electronic invoicing was set as a requirement for business transactions in Mexico. This event forced my company to upgrade all our business-related products within a six-month window. At that time, the effort of our development team was huge. Fortunately, we delivered all our products right on time.

Electronic invoicing has evolved substantially since 2010, and the continuous changes have forced us to enhance our development process. Continuous delivery is very important for us because the Mexican tax authorities have been publishing improvements to electronic invoicing several times per year.

We put LINQPad into action in 2015, as a solution for testing our .NET reusable libraries related to electronic invoicing. These tests were made with small pieces of code that were written and executed directly in LINQPad, making it inefficient to create Visual Studio projects for testing purposes. As a result, testing for those libraries was made in a fraction of the time, compared to our previous effort.

As a huge tech fan, I’ve been exploring the product since we started to use it. Its LINQ support allowed our development team to improve their skills in the language. As a result, the amount of code for our projects was reduced by almost 30 percent. And since LINQPad can be used as a scratchpad, pieces of code can be tested very quickly, and we can gather these pieces to make an entire project.

LINQPad offers awesome features that make it a powerful code-testing tool. The purpose of this book is to explain these features and make it possible for you to apply them in your development process.