A couple of weeks ago, I wrote about deploying multiple applications to Azure virtual directories from a single Git repository to Azure. That method works well. However, it by default only supports building and deploying a single .NET project. This was fine in my previously example in which only one of the deployment projects I had was .NET based. Using a custom KUDU script, it’s possible to deploy multiple .NET applications to the virtual directories from a single git repository.
Ninject is one of the better dependency injection frameworks, IMHO. However, within the context of .NET Threads and thread pooling, scoping of objects doesn’t work quite as expected.
Angular provides some handy mechanisms for dealing with browser history. With these mechanisms it’s straight-forward to handle URL changes through direct user interaction or the browser back/forward buttons.
Typically, when entering an Angular app, you’ll have an abstract route defined and then use the $urlRouterProvider to define a default route. Well, when I say “you,” I should qualify that to say that this is how I typically define states with ui-router.
I’ve made quite a few posts detailing the use of ui-router. These posts include general menus, tabs, and other “knowledge” of state mechanisms. The one thing missing though is maintaining state, or route, data.
Continuing our examination of building LINQ expressions, let’s dive further into generic methods that can build expressions for any enumerable list of objects. In part one, I showed how to build a simple string expression, but we can make this much more robust.
A while back, I needed a simple way to create a table with parent/child details in Angular. ng-repeat has some handy little known features to make creating this type of table easy.
Earlier today a colleague asked me how one would go about grouping data within an ng-repeat. I had never actually had to do this before, which made it an interesting problem to solve.
Azure added support for Virtual Directories a while back. It’s easy to add a virtual directory. One issue, though, is deploying to those directories since Azure only supports a single Git (or other) source control repository for the web application.
For services that I write that repeat a task over a set interval, I generally use a simple repeater loop. For the cases where I needed a bit more granular control of how/when Tasks repeat, I created a simple scheduler with a Fluent API.