The first package management system I learned to use was Bower. It was great for the short love affair we had together, but it stopped being supported and I was weary of learning to use one of its replacements. Fortunately, I haven’t had to with Libman. Libman’s (Library Manager) simple JSON approach to bringing front end dependencies has been the easiest for me quickly implement and it has been a great addition to Visual Studio. I implemented it possibly too quickly, however, and overlooked one powerful configuration setting: provider.…
I had a recent bug that took me much too long to solve and the root of the cause was me. I got a bit too delete happy and deleted a crucial file that allows me to use Razor Tag Helpers to bring a List into a View as a Drop Down (Select).
Here’s how the error presented itself:
- SelectList won’t populate
- Select or DropDown is empty
- value = Microsoft.AspNetCore.Mvc.Rendering.SelectList or
- System.Linq.OrderedEnumerable2 [Microsoft.AspNetCore.Mvc.Rendering.SelectListItem, System.String]
I am a full stack developer. I develop in Visual Studio, code in C# with .NET Core, deploy to Azure and I must admit, I’m a front-end cheater.
Comeon, the .NET Core Web App demo itself loads with Bootstrap and JQuery preinstalled. We’re all cheaters at some point, but I’m trying to diversify my cheating and eliminate my dependencies.
Here’s my latest strategy.…
I created a .Net Core site last month that despite meticulous detail to trying to keep my architecture tight, my database and API interaction and as clear as possible, I felt there was one large portion of my site needing attention: the front-end.
Being full stack often feels like wrestling a hydra. Just when I feel I’ve gotten the gnarly heads of database control, service interaction, dependencies under better control – there’s always at least one head loose, biting away at me. That currently, for me, is JQuery.
Done, so done with this. I need to improve my front-end game!
My Game Plan
I’ve been hearing about this for awhile on dotnet hangouts and loved it’s easy to read naming conventions. It’s documentation is clean and it’s style resembled enough of …