Source, Ingest, Prepare, Analyze and Consume
All about code tracking and management for example, Azure DevOPS branching and merging, Release management, Continuous integration (CI) and Continuous deployment (CD).
Running build pipeline for a web application targeting .NETFramework Version 4.6.1 using 2022 build agent, I have received this error;
The reference assemblies for .NETFramework,Version=v4.6.1 were not found. To resolve this, install the Developer Pack (SDK/Targeting Pack) for this framework version or retarget your application. You can download .NET Framework Developer Packs at https://aka.ms/msbuild/developerpacks The solution is to change the build agent to 2019.
Start by updating the list of repository packages:
sudo apt update
When this is done, run the update command:
sudo apt dist-upgrade
Follow any instructions and wait for the Pi update. When you’re done, type in:
sudo apt clean
This will delete unnecessary files that were uploaded during the update. Finish by restarting:
sudo reboot
When your Raspberry Pi is restarted, you will use the latest version of Raspbian.
For more info, read here
If the application is targeting multiple frameworks e.g. NET Core 2.1 and .NET Framework 4.6.1, you will need to install Hosting Bundle for it. Here is how;
https://dotnet.microsoft.com/en-us/download/dotnet/2.1
Restart your IIS box.
Make sure App poll is using v4.0 of .NET CLR version.
This will also help to solve this error;
IIS: Handler “aspNetCore” has a bad module “AspNetCoreModuleV2” in its module list
.Net Framework 4.5 was installed on my machine and on the IIS Application Pool, I set the .NET CLR version to 4.0.
The AppPool’s .NET CLR Version is different from the .NET Framework Version.
The AppPool’s .NET CLR Version is different from the .NET Framework Version.
The .NET CLR Version 4.0 is the CLR base for the following .NET Framework Versions:
So having a .NET CLR Version of 4.0 just means you support the above Frameworks, which will run under their deployed framework version.
Source: https://learn.microsoft.com/en-us/dotnet/standard/clr#clr-versions
Here is a full mapping of CLR to .NET Framework versions, based off this official documentation. https://learn.microsoft.com/en-us/dotnet/framework/migration-guide/versions-and-dependencies#version-information
CLR 1.0
.NET Framework 1.0
CLR 1.1
.NET Framework 1.1
CLR 2.0
.NET Framework 2.0
.NET Framework 3.0
.NET Framework 3.5
CLR 4
.NET Framework 4
.NET Framework 4.5
.NET Framework 4.5.1
.NET Framework 4.5.2
.NET Framework 4.6
.NET Framework 4.6.1
.NET Framework 4.6.2
.NET Framework 4.7
.NET Framework 4.7.1
.NET Framework 4.7.2
.NET Framework 4.8
Reference
This article is for the basic process template. The hierarchy is Epic, Issue and Task. Each level in this hierarchy has a page. Keep in mind that page follows a 3 section layout, Detail, Planning and Related work.
Epic customization Click on three dots (…) on the right side in Epic.
This will show following page;
Click on New field. You will get to following page;
The frequently used fields are already listed in “Use an existing field” but if you want to create a new one, you can use “Create a field”. More important, on the left side of navigation, pay attention to Layout section. This is where you can decide where to store this field; left, center or right.
Some standard fields that can be used in these pages are;
Risk, Effort, Business Value, Start Date, Target Date, T-shirt sizing, Story points, Activity, Original Estimate, Remaining Work, Completed Work.
Resources
https://learn.microsoft.com/en-us/azure/devops/organizations/?view=azure-devops