As many of you know, I use the C# programming language a lot for my Software Development work. With that being said, I often use some third party libraries in order to speed up development time and perhaps add some new features. However, the libraries I have listed here are used in every one of my C# projects. If your favorite C# Library is not listed. Please leave a link to it in the comments section so I can try it out. Let’s get started.
I specialize in making web and mobile applications and being able to parse and create JSON data is extremely important to me. Json.Net is a really useful tool for parsing and creating JSON data in your applications. It requires no setup, just add it to your project using Nuget and your now your ready to start working with JSON Data. I recommend that you spend some time reading the documentation so you know how to use the library effectively. Especially when dealing with nested elements in JSON Data. There is also a very active community around this framework in case you get stuck or get confused on the functionality. I cant recommend this library enough.
Recently, I wrote a blog post called The Gear I Use To Get Things Done. In that post, I outlined all of the computers and other gear I use to get my work done. Out of the list of products listed was a 2015 13″ MacBook Pro with Retina Display. It was a great computer for the time and it served me very well, until two weeks ago. During this time, I was browsing my Twitter Feed and saw numerous posts about discounts on the 2017 and 2016 MacBook Pro 15″ with Touch Bar at B & H Photo. Since I was in the market anyway for a more powerful laptop, I decided to check it out. However, the specs of the machines that had the discount were not going to be enough for my workload. With this in mind, I would look out for a good deal until Apple decides to update the MacBook Pro for 2018.
Over the last couple of weeks, I have made great progress on two apps that I’m writing. Working on these two projects every week has been a personal goal of mine since I started this blog, and I’m excited to see what the future holds. However, this progress means that the development process starts to slow down and the testing phase begins. This past weekend, I spent most of my time getting ready to move my apps into testing mode. During this time, I developed some tips in order to help newer developers get ready for testing.
For those who know me personally you might be aware that I’m learning VB.Net for use at my day job. Up until a month ago, I was using my C# skills to create applications and API’s for my employer. However, this caused a problem and management told me I had to learn VB.Net ASAP. To be honest I had no problem with this because, I could probably find some good online resources that could teach me the language rather quickly, since I already knew the .Net Framework. However, things went down hill really fast. Most if not all the resources for learning VB.Net are either very out dated or very poor. With not having any luck, I decided to find a Microsoft Virtual Academy course on VB. However all the offerings Microsoft had were considered retired, and recommended that I learn C# instead or try this VB for Absolute Beginners course.
That course didn’t satisfy me. I didn’t need to learn how to use Visual Studio or how to use certain data structures. I knew all that from C#. Since VB and C# use the same .Net Framework and CLR. I can easily move my existing coding skills to the older language. I eventually found this course on Udemy. I took the course shortly before Christmas and found it to be very helpful. But still didn’t have the content I was looking for but, it seemed to teach what I wanted to know. Soon I began to practice my VB skills. I made a handful of small apps but nothing major. After feeling pretty good about myself, I decided to try some common CRUD actions using Entity Framework (EF), a popular ORM for .Net, and one of my favorite tools. I ran into the same issue with the initial VB learning. All example code was in C# not VB. I eventually figured it out but getting EF to work in VB is not straight forward and its very ugly with the syntax. For those that are curious here is a sample incase your wondering how it looks:
Comparing it to the C# syntax its very messy and verbose. In addition if your using Pogo classes in a MVC project You need to import them one at at time instead of importing the models namespace. Even though I’m sill learning VB its very clear that it is a afterthought at Microsoft and all development efforts are still focused on C#, as it should be. However, if your just starting out do not learn VB. You are more likely to see a C based language like C# rather than a language based on BASIC. Its only a matter of time before VB is retired. Please feel free to comment or reach out to me on Twitter with your thoughts.