Category: Uncategorized
Default Gulp File | ASP.NET Monsters | Channel 9 videos
Here comes Episode 3 of The Monsters Weekly, and with it our run down of the default Gulp file in your ASP.NET Core application. Monster Dave walks us through Gulp, some node bits, package management, and how to sort all this out in our new ecosystem.
channel9.msdn.com/Series/aspnetmonsters/Episode-3-Default-Gulp-File
Swashbuckle and Swagger with ASP.NET Core | Cross Cutting Concerns
7 Mac Startup Options Every OS X User Should Know
Find the best NuGet Packages – NuGet Must Haves
Helps you find the best NuGet packages!
Based on popularity, documentation, votes, analytics, etc
nugetmusthaves.com/
Fluent URL builder and testable HTTP client for .NET – Flurl
Flurl is a modern, fluent, asynchronous, testable, portable, buzzword-laden URL builder and HTTP client library.
tmenier.github.io/Flurl/
Generate C# API Documentation with Wyam – CodeOpinion
5 Security Concepts Every Developer Should Understand – Simple Programmer
C# .NET Convert object to dynamic
public dynamic ToDynamic(object value)
{
IDictionary<string, object> expando = new ExpandoObject();
foreach (PropertyDescriptor property in TypeDescriptor.GetProperties(value.GetType()))
expando.Add(property.Name, property.GetValue(value));
return expando as ExpandoObject;
}
GIT – How to ignore local changed file
If you have a config file or something similar you change on your local computer but dont want it to get marked as “modified”.
Use this command:
git update-index --skip-worktree [filename]
If remote repo gets an update on that file you will get notified about this on a pull.
From stackoverflow:
skip-worktree is useful when you instruct git not to touch a specific file ever. That is useful for an already tracked config file.
Upstream main repository hosts some production-ready config but you would like to change some settings in the config to be able to do some local testing. And you don’t want to accidentally check the changes in such file to affect the production config. In that case skip-worktree makes perfect scene.
If you have skip-worktree on a file and the upstream changes, you get “please commit or stash” when you try to pull
More info here:
http://stackoverflow.com/questions/13630849/git-difference-between-assume-unchanged-and-skip-worktree/13631525