My last 2 posts were about problems with using Roslyn. Nonetheless, even if I sometime hate it, I'm still using it so the time has come to show some practical example of using Roslyn. Recently, I've been working on the task that can be summed up as: Take this ugly code and do something with it. i.e. more or less the refactoring task...
Rafał Hryniewski | użytkownik
A few days ago I showed you how to combine Nancy with Autofac and ASP.NET Core IoC. Today’s post will be related to the security and more precisely JWT authentication. Before moving further, I’d like to mention that below text is going to be the last Nancy-related one (at least for now). In a next couple weeks, we’ll explore the world of graph databases with Neo4j and .NET Core, so I hope you’re as excited as I do 😉 How does JWT authe...
Kontynuujemy temat serverless. Tym razem krótko o dwóch typach usług as a Service które są w jakimś stopniu bardziej lub mniej połączone z pojęciem serverless. Czy coś powinienem dodać do tych opisów? czegoś Ci brakuje? czujesz niedosyt?
Tworzenie puli obiektów to częsta praktyka stosowana w bibliotekach serializujących. We wpisie sprawdzam, czy używanie takiego podejścia dla małego bloku pamięci jest efektywne i czy nie lepiej użyć niskopoziomowego słowa kluczowego stackalloc.
We’ve recently released our newest application – Elastic Forms. While it’s easy to work with and powerful solution as a standalone application, you can expand its functionalities by order of magnitude using our API with other services. In this post, we’ll follow the example of using Elastic Forms with Microsoft Flow.
Lately I’ve seen some posts about authentication made easy and simple with various packages and how it’s great we doesn’t haven’t to store logins and passwords in our databases anymore due to global availability of social identity providers. It’s true that making simple authentication with of of those providers is simple today. And in Azure App Services it’s even simpler, it really can be done in 5 minutes.
As you’ve probably seen in previous posts about Akka.NET, actor model is no rocket science and is really easy and fun to start with. However entire actor model may seem like closed and hermetic ecosystem, today I’ll show you how to poke actors in way that’ll make them poke back.
Entity Framework (and other ORMs) are in general great pieces of software that makes developers lives so much easier by letting us thinking about objects when we’re working with data persisted in some underlying database. This makes development much easier than writing raw SQL queries. But some of us tend to get too comfy and forgetting about things that lies beneath our beautiful, object oriented code. After all we have Entity Framework, we shouldn’t wrap our heads around SQL stuff. But how about actual...
Hey everyone, I haven’t been asking anyone for help with developing the software for quite some time now, but well, the time is the crucial part here. I wish that the day lasted much longer than it currently is, yet, since I can’t do much about it, I want to ask you for help with contributing to the open source projects that I’ve been working on. It could be anything, like a feedback or an actual contribution (e.g. via Pull Request) and maybe you will find some of the projects interesting as there is a f...
One of the concepts of actor model that could be hard to grasp at the begining is fact that we will not operate on direct reference to actor instance. This can be a bit confusing before you’ll get used to it but by not using any direct references you’re sure to achieve very good level of encapsulation.
Yesterday I’ve writen about dynamic data masking in Azure SQL (works with SQL Server 2016 too). It is very interesting and simple feature. But can we use it with our beloved Entity Framework? Scenario Lets start with our scenario. We’ll have very simple console demo application (you can clone code from this repo) with one entity class and two DbContext derived classes using two different connection strings that will simulate two separate client applications fetching data from shared database.
Last week, I finally started working on my „Get noticed” project called gifty. If you have absolutely no idea what I’m writing about you can go read my introduction to the project which I link here😉 Anyway, one of the first things I wanted to do was to create some kind of ServiceBuilder for every microservice, since all of them (or at least majority) will have to go through some steps before the actually run. The steps are:Initialize Kestrel wi...
Along with Get Noticed contest I’m a bit preoccupied with other activities. One of them is preparing to take 70-473 Exam (cloud and data related stuff). Since I’m reading and using cert related stuff I could as well write about it – I’ll probably remember everything I’ll write about for rest of my life (writing about things works magic with memory) and maybe someone will have any use for that. Let’s start with simple things – dynamic data masking.
Let’s take a closer look at our actors, how their life looks like, what exactly they’ve been doing and what they can do. As they are basic building block of applications built on actor model it’s crucial to understand and being able to communicate with them.
In previous post I’ve explained briefly what actor model is and why it’s so fun. Today we’ll create our ActorSystem instance, learn what it is and send first messages to them. I hope it will be nice and easy start.
Actor model concept fascinated me since I’ve heard about it for the first time. It’s been on my todo list ever since and Get Noticed 2017 is great opportunity to give it a try. That’s why there is an actor responsible for almost anything in Me2.0. But, what is an actor, actor model and are benefits of using it in our projects? You’ll find out in a minute.
Until recently I was into ASP.NET MVC because of it’s possibility to extending, modifying and doing pretty much whatever you want with it. And while I’ve got rather proficient in plugging stuff in it’s pipeline and/or doing custom stuff like routing, binding or results, it never changed one fact about MVC – it’s big, really big. And the truth is, some times we don’t want so much. That’s why I wanted to give Nancy a go for some time, below you’ll find some of my first thoughts. And i must tell you now, it...
macko (32 816,53)
http://pawlos.blo... (31 603,45)
pzielinski (27 178,29)
gordon_shumway (21 178,87)
paduda (20 336,33)
psz750 (13 018,14)
rroszczyk (10 383,88)
Damian (9 041,08)
danielplawgo (7 235,99)
arek (6 807,91)
burczu (6 214,22)
PaSkol (5 393,84)
lukaszgasior (4 097,38)
jj09 (3 578,06)
jedmac (3 318,39)
http://jakub-flor... (3 224,66)
CaMeL (2 954,87)
spetz (2 783,22)
mnikolajuk (2 596,93)
lkurzyniec (2 590,69)