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.
Rafał Hryniewski | użytkownik
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...
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.
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...
I’m building my Get Noticed project from the scratch. And since 3 months is actually a very short span of time, I need compromise between doing some things fast (boring ones) and doing other things in a way that will allow me to write about it and not be ashamed to show some code afterwards. That means I’ll need to incur a technical debt in few areas of project. And I must watch it closely to not allow it to grow without control or interests will probably kill me.
Since my project will be hosted on Azure App Services I want to ensure that every pushed commit will land in cloud environment and will be available outside of my local, dev machine. As close to it’s intended, production-like environment as possible. And with Azure App Services you can achieve basic continuous delivery without taking a sweat.
Exactly one year ago I’ve published first post on this blog. It was simple “Hello world” that were followed by some posts related to 2016 edition of Get Noticed contest and after that by some more or less technical related stuff. Since it’s first anniversary of this first, lame “Hello world” post I can’t just write simple “Hi there” again. And because I’m taking a little breath before 2017 edition of said contest I don’t want to write any hard, technical stuff. So let me tell you about some things that I...
As you may already know I really, really like LINQ. One day I'll probably join together all my posts about this incredible featureand release pretty neat compendium/one-oh-one about this great feature. But while I'm not sitting and joining every post from this blog that have word "LINQ" in it into one, big pile, let's talk a bit about joining and grouping collections in LINQ.
So I've got two big, uppercase acronyms in title. Kind of double catchprase and if you're reading this, I've probably got your attention. And I hope to keep it so please, just don't stop reading, at least for a while. But why would you even consider stopping reading post about REST and some kind of API? Well, it's because I have lied and this post is not about this kind of REST that you've expected. Instead, it's about our human, common rest and recharging our batteries... and writing great REST APIs or ...
Aggregate is one of the most fun and powerful methods in LINQ. Sadly it's also of of the most underused and "scary" ones. I hope that after reading this post you will understand Aggregate a bit more, know when to use it and won't be afraid of doing so.
Some people can say 2016 was terrible year, for me it was one of the best, one of the most productive years as far as I remember. It was sort of game changer to me. So if you believe in balance in the universe, and last 12 month weren't so good for you, you must think there is a guy somehere, who stole your good fortune. Yup, it's me. I'm terribly sorry for that and ... I intend to make 2017 even better, at least for me ;).
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)