Skip to content

I have been working in the .Net environment for years, and as everyone knows, you generate a style of how you code. A fingerprint so to speak. I decided to take some of my past concepts and ideas and make them available at my own time. Here I can play and try new things :)

License

Notifications You must be signed in to change notification settings

goofybryan/ZarDevs

Repository files navigation

ZarDevs

Introduction

I have been working in the .Net environment for years, and as everyone knows, you generate a style of how you code. So when it comes to new projects, I always tend to have the same thought patterns. So I decided to take some of the ideas I have been toying with and make them available, without time constraints. I am also using this to play around with new ideas and technologies.

What is there?

So I decided to take one of last projects and completely revamp the backbone libraries I wrote. I decided that I was going to try things differently and all things that annoyed me about it and build something that is useful and flexible and re-usable.

So here is a list of items I am busy with. I also need to split the project into smaller projects instead of having one monolith one.

Dependency Injection (Ready, needs lots of testing)

One of my problems I had was that I developed this backbone using Ninject but as soon as I ran the code on a Xamarin Forms iOS phone, it crashed due to iOS not allowing certain types dynamic code, something along that lines. Now I found a workaround but the issue is that I wrote a lot of code, and to undo this, would take a lot of work.

So I decided that I didn't want to be tied down again. So I developed a standard way for IOC binding and calling, now I can write my libraries and just choose my implementing IOC technology.

Link to the repo

Http Api Security Abstractions (In Progress)

With one of my projects, I wrote a way to handle API calls that included refreshing tokens and logging in if required without having to compromise simplicity. It was this architecture that my friend said made it easy to implement what he needed to do. There was no complex requirements he needed to do, just implement and run.

Link to repo

Model and PropertyChanged Abstractions (To be started)

During my time I was doing some R&D development and what troubled me was the way that models and the changes that occur to them are handled. This came from how I normally saw them implemented. There is normally a base class with a dictionary that maps the property and changes and some complex code that manages this. What if you could take away that need on a model class and just let something else worry about that and let a model just say it's changed something. This one will take some time as I am busy with the others.

Link to repo

Runtime Utilities

This isn't really something I dreamed of doing, this is just a generic project that houses the shared runtime logic I need to make some of the magic happen.

Link to repo

To do

  1. Deploy packages to NuGet server.
  2. Split projects into smaller projects once NuGet deployement is completed.
  3. Examples that makes use of all the things I am building.
  4. Add logging to all projects

Links

  1. Home
  2. Dependency Injection
  3. Http Abstractions
  4. Model Abstractions
  5. Runtime

About

I have been working in the .Net environment for years, and as everyone knows, you generate a style of how you code. A fingerprint so to speak. I decided to take some of my past concepts and ideas and make them available at my own time. Here I can play and try new things :)

Topics

Resources

License

Code of conduct

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages