Learn MS NET

How to permanently disable Windows Compatibility Telemetry

sam@hykedesigns.com — Sun, 3 May 2020 22:59:40 -0800

While looking at Task Manager on my Windows 10 computer, I noticed a Windows Compatibility Telemetry process running and consuming about 12% of my CPU.

I was wondering what this was and how to turn it off if it is not necessary, after some research I came up with the answers and thought I would post them here for reference for anyone else who was looking for the same information.

The Windows Compatibility Telemetry is a service in Windows 10 which contains technical data on how the computer and its software are working. This services periodically sends data to Microsoft for improvement of the system and how to enhance the customer user experience. To stop the service from running and consuming resources we can disable the services from the Task Scheduler with the following steps:

Click Start, type Task Scheduler, and press Enter.
On the TaskScheduler window, go to the following path: Task Scheduler Library\Microsoft\Windows\Application Experience.
ON the Application Experience folder, look for Microsoft Compatibility Appraiser.
Right-click on it, select Disable, and then confirm to complete the process.
Once you’re done, check that the issue is resolved.

This will stop the service from running on your Windows 10 machine.

How to fix docker: Got permission denied issue on Ubuntu

sam@hykedesigns.com — Thu, 30 Apr 2020 17:24:00 -0800

With .NET Core cross platform and working on Linux as well as Windows and Macs, I've started to dabble again with Ubuntu and trying to see how I can use it for work with Docker and .NET Core.

After installing the latest version of Ubuntu 20.04 and getting it up and running I started to work on installing Docker. After looking I found several ways to install the latest stable version of Docker.

If you want to run docker as non-root user then you need to add it to the docker group.

Create the docker group if it does not exist

$ sudo groupadd docker

Add your user to the docker group.

$ sudo usermod -aG docker $USER

Run the following command or Logout and login again and run (that doesn't work you may need to reboot your machine first)

$ newgrp docker

Check if docker can be run without root

$ docker run hello-world

Taken from the docker official documentation: manage-docker-as-a-non-root-user

Setting a custom location for node_modules path with yarn

sam@hykedesigns.com — Wed, 9 Oct 2019 13:49:16 -0800

When installing packages with yarn the default folder that they are added to is “node_modules” in the directory of the project. Normally this does not present a problem unless you want to setup a different folder structure for your project. The problem I have seen with yarn as I have just started to use it with my projects is that the documentation is not the most concise that can be found.

One way we can change the output is to append the command line with the option of --modules-folder. this option works but can be a problem when updating modules or if you have a large number of packages that you would like to add to your project.

Yarn does have a way of configuring command line options for a project by including a .yarnrc file in the same folder as your package.json file. Yarn will use this file every time a command is executed. Within this file we can place the following –-modules-folder some/folder, now when we run yarn it will automatically place the packages in the some/folder structure.

This allows us to provide a custom location for using our packages and changing the project file structure easily and consistently.

IdentityUI has a breaking change in .NET Core 3.0

sam@hykedesigns.com — Wed, 11 Sep 2019 00:54:09 -0800

With ASP.NET Core 3.0, Identity UI was moved to use the new static web assets introduced in this version. With this move there are some breaking changes to be aware of:

.AddDefaultUI(UIFramework.Bootstrap4) no longer works.

With the new change Bootstrap 4 is now the default UI Framework for use with Identity UI. If you are in need of using an older version of the framework then this can be done by using the IdentityUIFrameworkVersion property in your project file.

The overload for AddIdentityUI that took a UIFramework parameter no longer exists in the latest versions of 3.0. If you are using Bootstrap 4, simply call AddIdentityUI(). If you need to use Bootstrap3, add the following line to your project file inside a PropertyGroup.

<IdentityUIFrameworkVersion>Bootstrap3</IdentityUIFrameworkVersion>

As I find more changes they will be posted here.

How to update a Docker container to the latest version

sam@hykedesigns.com — Mon, 19 Aug 2019 05:31:00 -0800

Having needed to update some Docker containers and getting familiar with how Docker works I though I would post this here so I have it for reference and if anyone else is looking to do the same thing.

On my installation of docker I run DotNet Core in containers and with each new update to the SDK new containers get published and it becomes necessary to update them every month or so.

As we can see on my installation at the moment the 2.2 versions are 4 months old

PS C:\WINDOWS\system32> docker images | findstr "dotnet"                                                                
mcr.microsoft.com/dotnet/core/sdk          3.0-buster               3930ade3a33a        4 days ago          695MB
mcr.microsoft.com/dotnet/core/aspnet       3.0-buster-slim          1d97a08ada5a        4 days ago          207MB
mcr.microsoft.com/dotnet/core/sdk          <none>                   4e9e8dec2900        3 weeks ago         707MB
mcr.microsoft.com/dotnet/core/aspnet       <none>                   de4e4dcb9041        3 weeks ago         196MB
mcr.microsoft.com/dotnet/core/sdk          2.2                      e268893be733        4 months ago        1.74GB
mcr.microsoft.com/dotnet/core/sdk          2.2-stretch              e268893be733        4 months ago        1.74GB
mcr.microsoft.com/dotnet/core/aspnet       2.2-stretch-slim         cb2dd04458bc        4 months ago        260MB
microsoft/dotnet                           2.1-aspnetcore-runtime   a5f99632e68d        4 months ago        253MB
mcr.microsoft.com/dotnet/core/aspnet       2.2                      df2a085ca3a8        4 months ago        260MB

In order to update the container and make sure they are the latest version, I ran pull:

PS C:\WINDOWS\system32> docker pull mcr.microsoft.com/dotnet/core/sdk:2.2                                               
2.2: Pulling from dotnet/core/sdk
9cc2ad81d40d: Pull complete                                                                                             
e6cb98e32a52: Pull complete                                                                                             
ae1b8d879bad: Pull complete                                                                                             
42cfa3699b05: Pull complete                                                                                             
dcc190332ff6: Pull complete                                                                                             
b49aea48d777: Pull complete                                                                                             
67e832fd5d6a: Pull complete                                                                                             
Digest: sha256:e1b19d391986f21b177c1ba47f8a8519bf5cff66a9459d04f3aea23e1a7ec30f
Status: Downloaded newer image for mcr.microsoft.com/dotnet/core/sdk:2.2
mcr.microsoft.com/dotnet/core/sdk:2.2

Now I have an update container for version 2.2 of the DotNet Core SDK

PS C:\WINDOWS\system32> docker images | findstr "dotnet"                                                                
mcr.microsoft.com/dotnet/core/sdk    2.2                   08657316a4cd        4 days ago          1.74GB

This will update the container that is located locally and if you were having any problems simply restart any container that uses that particular container to gain the latest version. The concludes the update of the container.

Can’t run dotnet in Windows Subsystem for Linux (WSL)

sam@hykedesigns.com — Mon, 12 Aug 2019 04:43:14 -0800

Having installed Bash on Ubuntu on your Windows 10 computer, your now looking to create a new application using .NET Core.

You start up a windows command prompt and run the bash command or directly run the Ubuntu command from your Windows menu. Once it is up and running you type in dotnet to create a new project and you receive this.

As you can see from the image it says that command not found, this will not work but the problem isn’t that the command doesn’t exists unless the .NET Core SDK is not installed, but that in linux you need to add the .exe extension to your command. If we type in dotnet.exe we will receive the following instead:

Now that we have figured out how to launch dotnet in WSL we can continue to develop our application using this framework.

HTTP Error 500.30–ANCM In-Process Start Failure

sam@hykedesigns.com — Tue, 18 Jun 2019 04:41:07 -0800

While preparing an app to run on my local IIS server for the first time I received this error. It provides some clues as to what is happening but does not give a direct cause and can be very frustrating when trying to get that app ready for production.

HTTP Error 500.30 - ANCM In-Process Start Failure

Common causes of this issue:

The application failed to start
The application started but then stopped
The application started but threw an exception during startup

Troubleshooting steps:

Check the system event log for error messages
Enable logging the application process' stdout messages
Attach a debugger to the application process and inspect

For more information visit: https://go.microsoft.com/fwlink/?LinkID=2028265

The page that we receive here basically takes us to the standard installation for the ASP.NET Core Module, which may be a good place to start to see if there was a misconfiguration when the module was installed.

Now if the issue continues there are some ways to determine what the issue is

Check Application Event Log

Access the Application Event Log:

Open the Start menu, search for Event Viewer, and then select the Event Viewer app.
In Event Viewer, open the Windows Logs node.
Select Application to open the Application Event Log.
Search for errors associated with the failing app. Errors have a value of IIS AspNetCore Module or IIS Express AspNetCore Module in the Source column.

Run the app at a command prompt

Many start-up errors don’t produce much useful information in the Application Event Log. Another option is to run the app at a command prompt on the hosting system if there is access to do that.

Framework-dependent deployment

If the app is deployed as framework-dependent:

At a command prompt or PowerShell window, navigate to the folder that contains the app and launch the app by executing the assembly with dotnet.exe.

dotnet .\<assembly_name>.dll – substitute <assembly_name> with the name of the application

In the console window, if there are any errors they will written in the output.
If the errors only occur when making a request to the app, launch a browser and make a request to the app. Usually this will be at http://localhost:5000/. If the app responds normally with no error, the problem more likely related to the hosting configuration and not the app.

Self-contained deployment

If the app is deployed as self-contained then follow the above steps substituting <assembly_name>.exe for dotnet .\<assembly_name>.dll and follow the rest of the steps.

ASP.NET Core Module stdout log

To enable and view stdout logs:

Navigate to the app folder on the host system.
If the logs folder isn’t present create the folder.
Edit the web.config file. Set stdoutLogEnabled to true and change the stdoutLogFile path to point to the logs folder (for example: .\logs\stdout) stdout in the path is the log file name prefix.
Ensure your application pool’s identity has write permissions to the logs folder.
Save the updated web.config file.
Make a request to the app or site.
Look in the logs folder and find the latest log file.
Check the file for errors.

Once trouble shooting is complete make sure to turn off logging in the web.config file by setting stdoutLogEnabled to false

Hopefully this helps solve your issue.

How to serve files without extensions in IIS

sam@hykedesigns.com — Mon, 17 Jun 2019 10:53:00 -0800

By default, IIS will not serve up files without an extension. Never the less sometimes we need to allow IIS to serve up these files.

The following web.config file can be placed in the directory that you want to serve up these files from.

<?xml version="1.0" encoding="UTF-8"?>
    <configuration>
         <system.webServer>
             <staticContent>
                 <clear />
                 <mimeMap fileExtension="." mimeType="*/*" />
             </staticContent>
         </system.webServer>
</configuration>

The mimeType can be adjusted to allow a specific type of file to be downloaded from the server as well.

Stopping Chrome from redirecting from http to https for a domain

sam@hykedesigns.com — Fri, 14 Jun 2019 10:54:00 -0800

While moving a website that had SSL enabled previously and trying to get SSL setup back I was having issues in chrome redirecting to the https:// protocol.

I found a solution in the new version of chrome, browse to chrome://net-internals on the menu on the left Click Domain Security Policy and at the bottom of the page that comes up enter the domain you want to delete security policies on the Delete domain security policies input box.

This resolved the redirect for me and made the site work as I wanted it to at the moment.

Denied: requested access to the resource is denied

sam@hykedesigns.com — Thu, 13 Jun 2019 10:55:00 -0800

While working on a project I recently was working on pushing up a Docker image to the Docker registry and received the following

The push refers to repository [docker.io/user/project]

9a6d7cb5cc75: Preparing

a7ab0be8f866: Preparing

91b97cbb40f2: Preparing

04e6caa5b49e: Preparing

3bffb3181da2: Preparing

5dacd731af1b: Waiting

denied: requested access to the resource is denied

This did not seem right as I had just previously logged in successfully to the Docker Registry with my username and password. Turns out that I had not logged in to docker.io only the registry itself so I was not allowed to do what I wanted to do with my Docker push command.

I then proceeded to login in with the following command

docker login –u “username” –p “password” docker.io

This will log you in to the correct location in Docker Hub to push your container.

Hope this helps.