Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

mthalman
Copy link
Member

@mthalman mthalman commented Aug 19, 2022

Adds .NET Fx 4.8.1 Dockerfiles. As far as support for Windows Server, 4.8.1 is only supported on Windows Server 2022 so that is the only version being included here.

This is marked as a draft PR right now because further changes will be needed. But it is ready to review. Right now 4.8.1 is configured to be installed by itself. But as part of the September servicing release, a 4.8.1 patch will be installed as well. That will require a template and Dockerfile change.

In addition to new 4.8.1 Dockerfiles, these changes also add the 4.8.1 reference assemblies to the other SDK versions. This allows, for example, a 4.8 SDK container to be used to build (but not run or test) a 4.8.1 project.

Fixes #981

The code being removed was leftover from long ago when we had SDK images for other versions besides 3.5 and 4.8. Now everything is consistent wrt which targeting packs are installed.
--add Microsoft.Component.ClickOnce.MSBuild ^ `
--add Microsoft.Net.Component.4.8.1.SDK ^ `
--add Microsoft.NetCore.Component.Runtime.3.1 ^ `
--add Microsoft.NetCore.Component.Runtime.5.0 ^ `
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Friendly reminder that this will need to be integrated with the active PR to remove the 5.0 runtime from the sdk image.

@mthalman mthalman marked this pull request as ready for review September 13, 2022 13:09
@mthalman
Copy link
Member Author

Marking this as ready to review now. I will merge this in prior to creating the PR for the servicing updates.

@mthalman mthalman merged commit 950c9b5 into microsoft:main Sep 13, 2022
@mthalman mthalman deleted the 4.8.1 branch September 13, 2022 13:40
# NuGet version to install
NUGET_VERSION=6.2.1 `
# Install location of Roslyn
ROSLYN_COMPILER_LOCATION="C:\Program Files (x86)\Microsoft Visual Studio\2022\BuildTools\MSBuild\Current\Bin\Roslyn"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why is this needed?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure. It was added a long time ago: #89. @MichaelSimons, do you remember?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I see there was a customer reported issue when it was not defined correctly - building aspnetcore app with msbuild.exe

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I read through that issue but I'm not really sure how that would have any impact. That isn't used anywhere I can think of (alos did a bit of searching).

&& del microsoft.net.compilers.2.9.0.zip `
&& %windir%\Microsoft.NET\Framework64\v4.0.30319\ngen install C:\RoslynCompilers\tools\csc.exe /ExeConfig:C:\RoslynCompilers\tools\csc.exe `
&& %windir%\Microsoft.NET\Framework64\v4.0.30319\ngen install C:\RoslynCompilers\tools\vbc.exe /ExeConfig:C:\RoslynCompilers\tools\vbc.exe `
&& %windir%\Microsoft.NET\Framework64\v4.0.30319\ngen install C:\RoslynCompilers\tools\VBCSCompiler.exe /ExeConfig:C:\RoslynCompilers\tools\VBCSCompiler.exe
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These are very old and unsupported compilers. My intuition is that by putting them directly into the C:\RoslynCompilers\tools the are preferred over the more recent compilers being installed. Is that the case? If so is there a reason for this cause it seems counter to pushinig people to supported tooling.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The aspnet Dockerfiles were originally defined by @HongGit's team which were then merged into this repo. Hopefully @HongGit can provide some info here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Install 4.8.1 targeting pack
3 participants