I have amassed a lot of code. When I’m creating a new web application, this is handy because it provides me with a good basis. However, I’ve never gone to the trouble of wrapping all of this into a template to eliminate the redundancy.
Creating Visual Studio Templates Part 1
posted on April 24, 2016 by long2know in ASP.NET, Microsoft, Web
Detecting every time NgRepeat is Redrawn
posted on April 21, 2016 by long2know in angular, JavaScript
Quite a while back, I wrote a blog post that detailed how it’s possible to use a directive to determine when an Angular repeater is finished. My solution, like nearly every other solution I looked at has one major flaw. It’s only triggered on first render.
Stored Procedure Progress Messages
posted on April 14, 2016 by long2know in ASP.NET, Database, Entity Framework
Earlier today, I needed to be able to retrieve progress indicators from a long-running stored procedure. The procedure itself executed many different queries, so the idea of sending messages to the client between those queries seemed like a good place to start.
Angular project structure and conventions redeux
posted on April 9, 2016 by long2know in angular, JavaScript
Last year, I provided a brief synopsis of a project structure and conventions that i use with Angular.
Over the course of a year though, this structure has evolved.
Angular root path and IIS Express
posted on April 6, 2016 by long2know in angular, ASP.NET, JavaScript
Often, web applications aren’t deployed to the root path of a web server. Also, often, developers (me included) develop applications with the intent of deploying to the root path.
Overcoming this problem with an Angular app, while also making a local build against IIS Express and a production deploy work, is relatively straight forward.
Angular Locale Settings
posted on April 4, 2016 by long2know in angular, JavaScript
With a current application project in which I’m using Angular’s built-in currency filter, the value, when negative, was properly enclosed in parenthesis.
However, an Angular update (to v1.5) changed this behavior.