We've all been there at some point. Your app works great on your machine, all features are ready to be pushed to dev/acc, and when you do, all hell breaks loose.
Specific to Angular apps, the following error gets thrown a lot after you
We've all been there at some point. Your app works great on your machine, all features are ready to be pushed to dev/acc, and when you do, all hell breaks loose.
Specific to Angular apps, the following error gets thrown a lot after you
As a .NET Web developer, I'm always looking for better ways to get Angular and MVC.NET to play nicely together. Writing and rendering templates using the templateCache is a good example of these two world that tend to collide if not implemented correctly.
Say you want to bind a string to an element in Angular. No real problem, you just use expressions or ngBind.
If the string contains HTML that you want to parse, you can use ngSanitize.
But what if your HTML string contains a button that
As a .Net developer Visual Studio is my greatest power. This robust, adaptable and powerful IDE provides everything I could possibly need.
But with upcoming new JavaScript technologies like Node and Single Page Applications, it sometimes falls short. It's not that Visual Studio is bad