Author: Andreas Plahn

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

Set up staging environments for web apps in Azure App Service | Microsoft Docs

When using deployment slots in Azure Web Apps the appsettings and connectionsstrings are changed when swapping slots.

E.g. the production environment slot has the “production” version of appsettings and connectionstrings and the pre production slot has its own version of those settings in the web.config file.

This is default behaviour, unless you use the app settings in the Azure portal for the environments (overrides web.config file) or check the “Slot setting”. (setting will “stick” with the swap).

Read more here:

Slot config:
Set up staging environments for web apps in Azure App Service | Microsoft Docs

Configure web sites:
https://docs.microsoft.com/en-us/azure/app-service/web-sites-configure

 

Where do I find the Azure Website Deployment password

If you are using azure deployment profiles for Visual Studio you can find the deployment password here:

Login to portal, select the web app service, click the link “Get publish profile” to download. Open the xml file and find the password in element publishProfile attribute userPWD.

Source: Where do I get my actual Azure Website Deployment password? – Stack Overflow

EPiServer – Comparing list properties

Probably in every EPiServer project there will be a need to store a list of links to your content pages. EPiServer.CMS.UI 8.6.0 introduced a new multiple ContentReference property. Usually we could use a single property to store a collection of links. For example when building a media slideshow or when displaying links in a site footer. Using EPiServer there are several possibilities of implementation.

List properties: ContentArea, LinkItemCollection, multiple ContentReference

Read more here: Comparing list properties – Grzegorz Wiecheć

Copying files larger than 2 GB over RDP

Symptoms

When you try to copy a file larger than 2 GB over a Remote Desktop Services or a Terminal Services session through Clipboard redirection (copy and paste) by using RDP client 6.0 or a later version, the file isn’t copied. And you don’t receive an error message.

Cause

It’s a known issue. Copying files larger than 2 GB by using this method isn’t supported.

Resolution

To resolve this issue, use one of the following methods:

  • Use Drive Redirection through Remote Desktop Services or a Terminal Services session if you want to transfer files larger than 2 GB.
  • Use command-line alternatives to copy files larger than 2 GB over a Remote Desktop Services or Terminal Services session. For example, use the following command:
    Console:

    xcopy \\tsclient\c\myfiles\LargeFile d:\temp

Source: Copying files larger than 2 GB over a Remote Desktop Services or Terminal Services session by using Clipboard Redirection (copy and paste) fails silently