About
Hello and welcome to my blog on various topics from the world of .NET. My name is Andras Nemes and I’m a software developer. I primarily work with .NET and Java. I mostly blog about .NET but you’ll see posts from other technologies as well. I hope you’ll find a lot of interesting topics here that you can use in your own projects.
A bit of orientation:
- The actual blog page is found here
- Short and concise code examples with little theory: The Shorts
- Lengthy discussions providing deeper analysis and insight: The Longs
- For technologies other than .NET check out the Other technologies section
- For more personal questions and comments you can contact me here
- You can find me on LinkedIn here
Planned topics for 2016 for the ‘longs’ section, in no particular order:
- SQLite in .NET
- Even more DDD
- EntityFramework
- MongoDb in .NET
- Various messaging frameworks in .NET
Planned topics for the “Other technologies” section for 2016:
- Amazon CodePipeline with the AWS Java library
- Python language course cont’d
Exercises in .NET with Andras Nemes 
I recently found your blog and have really enjoyed your posts, especially the series about claims and security. It seems about half the times the code samples end up HTML encoded which sometimes makes them hard to follow, especially with a lot of angle brackets and lambdas. Any chance that can be fixed?
Thanks for your comments. I’ll try to look into the issue as soon as possible.
I’ve gone through the code snippets and replaced the HTML codes. I hope it’s not some automatic process that encodes certain elements…
Hello Andras,It is really so usefull web site which is important to me to improve my skill.I have a question.My question is micro Orm and generic repository implimentation.do u think it is unnecessary to wrap.I am just about to start a project which planing use both dapper and generic repo.if u share your experiance,it would be great.thank u again.
Hi Ada, I have no experience whatsoever with micro ORM so it’s difficult to say. If it has a unit of work implementation which is as good as that of EntityFramework then it might be overkill to hide it entirely behind abstractions. You can check out the revised DDD series for an example how a solution could look like in EF. //Andras
Hello from Belgium,
Hello Andras, I have considerably improved my knowledge of .Net programming thanks to your blogs. In particular with regard to the DDD architecture.
Thank you !
(Excuse me for my english)