Nuget package handling – Using package.config instead of new PackageReference in csproj Visual Studio 2017

In Visual Studio 2017 and with .NET Core projects a new way of referencing nuget packages was introduced. Somehow during a .NET project upgrade one of the nuget packages were converted into a PackageReference (referenced in the csproj file and not from package.config). Below are the steps to convert such package reference back into plain old package.config behaviour:

In addition to removing the PackageReferences from the project file, I also had to remove the following files from the $ProjectDir\obj directory: Myproject.csproj.nuget.cache Myproject.csproj.nuget.g.props Myproject.csproj.nuget.g.targets project.assets.json

Source: How can I revert to referencing Nuget packages in packages.config after using Package References in a .NET Standard project? – Stack Overflow

Visual Studio Code Tips and Tricks

“Tips and Tricks” lets you jump right in and learn how to be productive with Visual Studio Code. You’ll become familiar with its powerful editing, code intelligence, and source code control features and learn useful keyboard shortcuts. This topic goes pretty fast and provides a broad overview, so be sure to look at the other in-depth topics in Getting Started and the User Guide to learn more.

Resizing images in EPiServer – Dejan Caric

Every EPiServer developer knows that editors love to work with high-resolution images. If those images are not optimized for different devices, they may increase the page loading time and ruin the browsing experience. There is nothing worse than serving 5000x5000px images on a device whose viewport is only 400x700px, or sending big images (15mb+) over a 3G network. The days of fixed-width website design is behind us. HTML5 has support for responsive images using picture element.