Continuous Developer

5 years ago on c#, dotnet, .net

Why do you have an implementation in your interface?

Interfaces in C# An INTERFACE in C# is a type definition similar to a class, except that it purely represents a contract between an object and its user. It can neither be directly instantiated as an object, nor can data members be defined. So, an interface is nothing but a… Read more →

8 years ago on typescript, c#, csharp, typewriter, models, autogenerate

Keeping your C# and TypeScript models in sync

I've been working on a new Angular (v4) application that talks to a C# (asp.net core) backend. One of the things I love about Angular is TypeScript, and one of the things I love about TypeScript is the ability to define the models you'll send and receive. I love… Read more →

  • Why do you have an implementation in your interface? →
  • Keeping your C# and TypeScript models in sync →

About Continuous Developer

Follow my journey into the world of Continuous Integration / Continuous Deployment / Continuous *. I'll also cover random dev topics that I come across in my day to day work.

Proudly powered by GHOST.
Theme based on ghostentista