posted on January 19, 2016 by long2know in angular, codepen, plunker
In my previous posts regarding advanced Angular navigation, I showed how to create a menu and use the $state provider(s) to track the current state, which menu option is active, and how to move between states using ui-sref. This particular demo used an in-line service called “menuService.”
This is a pretty solid mechanism for navigation, but I wanted to also take a look at doing something similar with the same navigationService, ui-router, and ui-bootstrap tabs.
posted on January 13, 2016 by long2know in css
While testing a new application that utilizes my multiselect drop-down widget, I noticed some weird behavior with IE11.
posted on January 4, 2016 by long2know in css, Web
Earlier today I was playing around with Google’s Font API. I wanted to pull down OpenSans to host locally, but Google’s Font API is geared more toward utilizing Google’s hosting resources.
posted on December 17, 2015 by long2know in angular, codepen, JavaScript, node, plunker, Web
Continuing the discussion of integrating server-side validation with client-side validation, let’s check out a demo of this in action.
All of the Angular code for this demo has been moved to my general demo Github repository.
posted on December 10, 2015 by long2know in Azure, node
If you recall my previous post on Node.js, I explored developing a Node.js app with Visual Studio. Using this approach makes it very easy to deploy and test with Visual Studio directly to Azure. However, I wanted to work with a more cross-platform approach using Visual Studio Code and continuous deployment with Azure’s Github integration.
More Link
posted on November 23, 2015 by long2know in angular, ASP.NET, SignalR
SignalR is a nice framework for broadcasting messages to all clients connected to your web server. It also provides mechanisms to allow those clients to send messages to other clients. It’s not “Angular friendly” out of the box, though, since it’s designed more for use with (imho) jQuery. Here’s a simple service that I like to use with SignalR and Angular
posted on November 9, 2015 by long2know in Akka, ASP.NET
Over the past few weeks, I’ve been looking at what it takes to create a distributed computing system. The idea of using the Actor model / Actor pattern came up and it is a concept that seems to fit nicely. What is the Actor pattern then?
From Wikipedia, it’s described as such:
https://en.wikipedia.org/wiki/Actor_model
Here’s another concise definition:
An actor object is used when you have a long running task and some code that needs to be executed after it completes. This kind of object is given the information it needs to perform the task and callbacks to execute when that task is done. The actor runs on its own thread without any further input and is destroyed when it is finished.
How does one go about implementing the actor pattern, though?
posted on October 30, 2015 by long2know in angular, ASP.NET, JavaScript, WebApi
Client side validation is pretty handy. However, as we all know, you can’t fully trust any data sent to your server from a web client. As such, we generally duplicate validation in both the client and server side scenarios. This isn’t a big problem, but it does create a disconnect when the client validation passes, but then the server validation fails. Even in duplication, I still want server-side validation to play an integral part of the overall user experience.
posted on October 20, 2015 by long2know in LINQ
I’ve said it before, and it bears repeating. LINQ is one of those features in .NET that keeps me using it. In-line queries that allow you to expressively search lists, with the declarative query syntax, is very appealing. Sure, under the covers, it’s performing the heavy lifting, iteration, and such, but the SQL-like lambda expressions are incredibly powerful.
However, sometimes we need something even more dynamic.
posted on October 4, 2015 by long2know in Database, Entity Framework
Late last week, I ran into an interesting problem. My current web-based project allows users to perform bulk operations on various database records – up to 1000 records at a time. When dealing with a small number of records, performance was adequate. However, when working with 1000 records, performance was completely unacceptable.
