Blog
May 7, 2019 • Smart Resources

Spotlight On: C-Sharp .Net Core with Kevin Ogborne


 

ShareShare on LinkedInTweet about this on TwitterShare on Facebook

At Smart Resources, we’re extremely proud of the innovative advancements in technology that our consultants work towards each and every day. Our skilled IT professionals work in a variety of sectors with a wide range of technologies. Each month, we sit down with a consultant to have an in-depth conversation about their current project to gain insight on the technology and its capabilities. This month, we’ll be discussing C-Sharp .Net Core with Kevin Ogborne!

Name: Kevin Ogborne

Position:  Senior Consultant – API Manager/Developer

Years with Smart Resources: 10+

Professional background (specifically in regard to C-Sharp .Net Core):

During my career, I have had the opportunity to work on lots of different technologies, but currently I am working on REST API – C-Sharp .Net Core Project.

Please tell us about C-Sharp .Net Core and how it’s commonly used:

REST API’s are used almost everywhere these days. These interfaces are used to manage information for specific purposes such as updating contact information or ordering something online. REST is a concept that requests do not need to know anything about the situation in which they are submitting the request, only that they are submitting a request and API responds with a finite action based on HTTP Response Codes. How is this valuable? It places a standard framework upon which services around the globe can operate and it sets expectations.

Now onto C-Sharp .Net Core… This is structured language unlike JavaScript or some other languages. The Core (2.0+) version uses injection as REST framework for creating API’s. On the current project I am involved with, C-Sharp allows you to set the environment across multiple API services, as well as adhere to Micro-Services, which for this project are small singular API services that can be scaled up quickly based on demand.

What originally drew you to working with C-Sharp .Net Core?

Well, a couple of things. Working with C-Sharp itself was for another customer’s needs in writing custom SharePoint solutions and stand-alone websites. The project was using C-Sharp in many capacities and when this new endeavor started, the customer decided to use C-Sharp and REST frameworks for the project. C-Sharp uses NuGet packages for additional functionality that is not straight out of the box. This provides a very versatile solution for accomplishing project goals and fulfilling customer needs.

Why do you enjoy about working with C-Sharp .Net Core?

The technology is very versatile with the use of NuGet packages and it keeps you from writing functionality from scratch, such as validation routines. It makes putting a solution together for a customer pretty quick.

What challenges have you faced while working with C-Sharp .Net Core?

The biggest challenge in working with this technology is determining which C-Sharp framework to use, matching NuGet Packages (there are always a considerable number of packages available), and then integrating packages to provide a solution. It sounds easy on paper, but at times, can be quite difficult. As an example, the other day I was using a new NuGet package called AutoMapper. I used setup documentation to get it integrated, but it was not working properly. It took a little bit a research to learn that, with this version of C-Sharp .Net Core (2.0), I needed to make a one line change for it to work correctly. We find those situations quite often.

What do you see in the future for C-Sharp .Net Core?

C-Sharp .Net has been around for almost two decades and has seemed to do a nice job of changing as the development theories change in order to stay relevant. REST API’s framework is really in its infancy and I expect it to become more refined over time. REST API has already gone through a couple of refinements due to use and practicality.

What is the best piece of advice you have for someone learning about or working with C-Sharp .Net Core?

For my career at least, being willing to take on any challenge has been beneficial. This has allowed me to learn the whole scope of an IT organization, from hardware to software as well as development, security and policy setting. Each project I have worked on provides the opportunity to learn a specific technology at a very intimate level, so be willing and open to new opportunities.

Do you have any additional advice, anecdotes, or information about the tech that you’d like to share?

I tend to say this quote a lot. “I/we can’t be the only project in the world trying to do this.” What does this mean? There’s no reason to re-invent the wheel as long as there is the internet for research. It puts a premium on learning the search terms in order to quickly find the needed solutions.

At Smart Resources, we connect talented IT consultants with innovative Richmond organizations. Learn more about what we can do for your business.

 

Related Spotlights

Getting Smarter with Mark Ludeke

Spotlight On: Cognos Analytics with Joe Cline

Getting Smarter with Henry Thedieck

 

ShareShare on LinkedInTweet about this on TwitterShare on Facebook

 

 

Comments are closed.