codingsoul

Tag: dotnet

multi-schema with EF Core 6.0 and default interface method stack overflow exception magic

Introduction Since I went to be a freelancer some months before, I am lucky enough to participate in a lot of interesting projects. The most recent one is about creating surveys. What’s the topic? A catalog of questions shall be configured. Questions can be hierarchical, rely on parent. Just one level. Questions are defined with […]

Read More

Logging with log4net and Windsor Castle in c#

Quite a while ago I had a good talk with an colleague about “to log or not to log – that is the question”. 😉 That was a longer discussion, and a lot of questions had been raised: Shall we do logging? What shall be logged out? Should we create a log library by ourselves to […]

Read More

How to do sensible logging in c#

In last post about Are Extensions the beauty or the beast? I added a screenshot that showed a class implementing the repository pattern. This actually also showed the implementation of our log strategy. I did get some questions why we do it like this and what are the benefits. Let’s have a look onto how we do it: […]

Read More

Coding principles: Are extensions the beauty or the beast?

The other day a collegue of mine came to me, being pretty enthusiastic. He was amazed about his latest changes to the code. As I am the responsible architect, it is my turn to have a look onto the changes. So we sat together and did so. Usually we create our code via straight rules and best practices. As […]

Read More

Coding principles: These assembly/ folder structures… suck.

We need to move people from time to  time between products. It can be tough when you move from SSIS/ Sql/ SAP stuff to job-based Excel automation. How can we make a hard task easy? The very first things that developer see are the assemblies and the folder structures. Let me first put some bad examples for assembly […]

Read More

Coding principles: The difference between defensive and offensive programming

I put together a list of strategies, rules and best practices for our team. This is not any unusual stuff, but (IMHO) a sensible and smart set of rules to follow to be able to write extensible, maintainable, understandable, testable, robust,… *TooManyAdjectivesException* …code. To follow the evolution of methodic and what are the coding principles we do […]

Read More

Evolution of methodic: Melting the metal

Let me take you to a short journey how I started with programming, where it went to, and how the actual methodic, thinking and doing evoled. This will have the following posts: It all started with i=i+1 Melting the metal Going to Windows 3.11, I need (MS) access Why is there any system without a database? Going to VB6 […]

Read More

Evolution of methodic

Let me take you to a short journey how I started with programming, where it went to, and how the actual methodic, thinking and doing evoled. This will have the following posts: It all started with i=i+1 Melting the metal Going to Windows 3.11, I need (MS) access Why is there any system without a database? Going to VB6 […]

Read More