Laws of UX
5 favorite CSS tricks I learned this year – DEV Community
Make Visual Studio opening XSDs in XML editor mode
Right click on an XSD file, choose “Open with…” and select the appropriate option – then click on “Set as Default” before you actually open it.
Source: Stop Visual Studio 2010 opening XSDs in design mode – Stack Overflow
The 9-Step Plan For Becoming Good In Any Programming Language
Git Concepts I Wish I Knew Years Ago – DEV Community
GitHub – rcbyr/keen-slider: The HTML touch slider carousel with the most native feeling
GitHub – rcbyr/keen-slider: The HTML touch slider carousel with the most native feeling
github.com/rcbyr/keen-slider
Responsively App | A Web developer’s responsive browser
Develop responsive web apps 5x faster! A must-have DevTool for all Front-End developers that will make your job easier.
responsively.app/
Solution for .NET error: The type ‘HttpResponseMessage’ exists in both ‘System.Net.Http, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a’ and ‘System.Net.Http, Version=4.2.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a’
Got this error when building a .NET framework (version 4.6.1) solution containing multiple projects:
The type 'HttpResponseMessage' exists in both 'System.Net.Http, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' and 'System.Net.Http, Version=4.2.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'
My solution:
Install System.Net.Http version 4.0.0 as nuget package to the “failing project”.
Added this to the “failing” project app.config file:
<assemblyBinding> <!-- other dependentAssembly bindings here --> <dependentAssembly> <assemblyIdentity name="System.Net.Http" publicKeyToken="b03f5f7f11d50a3a" culture="neutral" /> <bindingRedirect oldVersion="0.0.0.0-4.2.0.0" newVersion="4.0.0.0" /> </dependentAssembly> </assemblyBinding>
Updated the “failing” projects .csproj file like this:
Removed this line or similar for System.Net.Http:
<!--<Reference Include="System.Net.Http, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a, processorArchitecture=MSIL" />-->
Added “hintpath” with projects relative path to the nuget packages.
In my example its 3 level up and then down (..\..\..) you might need to adjust to your projects folderstructure.
<Reference Include="System.Net.Http, Version=4.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a, processorArchitecture=MSIL"> <HintPath>..\..\..\packages\System.Net.Http.4.0.0\ref\dotnet\System.Net.Http.dll</HintPath> </Reference>
Voila.
Most Complete MSTest Unit Testing Framework Cheat Sheet
using Microsoft.VisualStudio.TestTools.UnitTesting; namespace MSTestUnitTests { // A class that contains MSTest unit tests. (Required) [TestClass] public class YourUnitTests { [AssemblyInitialize] public static void AssemblyInit(TestContext context) { // Executes once before the test run. (Optional) } [ClassInitialize] public static void TestFixtureSetup(TestContext context) { // Executes once for the test class. (Optional) } [TestInitialize] public void Setup() { // Runs before each test. (Optional) } [AssemblyCleanup] public static void AssemblyCleanup() { // Executes once after the test run. (Optional) } [ClassCleanup] public static void TestFixtureTearDown() { // Runs once after all tests in this class are executed. (Optional) // Not guaranteed that it executes instantly after all tests from the class. } [TestCleanup] public void TearDown() { // Runs after each test. (Optional) } // Mark that this is a unit test method. (Required) [TestMethod] public void YouTestMethod() { // Your test code goes here. } } }
Source: Most Complete MSTest Unit Testing Framework Cheat Sheet