Easily supporting multiple target frameworks (TFMs) with VS2017 and Nuget

Wednesday, April 5, 2017

In VS2017 it much easier now to support multiple frameworks inside a single .csproj file. When you create a new project VS2017 (that target .NET Core or .NET Standard) this is what you'll get inside your *.csproj <Project Sdk="Microsoft.NET.Sdk"> <PropertyGroup> <TargetFramework>netstandard1.4</TargetFramework> </PropertyGroup> </Project> Cool right? A lot of the boilerplate configuration was removed in order to make the MSBuild format clean and readable. By default, all the files inside your project folder will be added. If you want to make adjustment you can always add (or remove some of the files). For example, this is how it will look if...
2 comments

Using extension SDKs in without installing it

Monday, September 29, 2014

In my Windows 8.1 project I wanted to use the SQLite PCL library. I Installed it from nuget and everything worked great so I committed the changes to the source control and moved on. When my colleague pulled the changes, it didn't compiled. The nuget package installed an extension SDK for me but apparently it doesn't install it when you restore the package (very bad for CI). So it seems that the only solution is putting the SDK inside our 3rdParty folder and putting it as part of our source control, but unfortunately this wasn't an easy task – so im writing about...
no comments