Comments (11)
Great question.
Two challenges to that:
- .NET 4.5 is out of support. .NET 4.5.2 is in support so would be an option.
- Windows containers don't support this scenario since Windows Server 2016 contains .NET Framework 4.6.2. Neither .NET Framework or Windows containers enables us to "go backwards". We cannot provide an older .NET Framework in place of 4.6.2 or an older Windows Server container images than 2016. Everything about Windows containers is forward looking from the point of Windows Server 2016 and Windows 10.
from dotnet-framework-docker.
net452 would probably be fine. The main requirement for my own purposes is to not have net46+.
I was concerned that your second point would be made. 😢 What if we hacked it? You know... took a servercore image and replaced .NET dll's with those delivered by net45x?
from dotnet-framework-docker.
Sure. That could work. It obviously wouldn't be supported/endorsed/hosted but it could work well enough for testing (assuming that there are no Windows 10 app compat issues we worked around; I don't know).
You'd need a copy of 4.5.2 and a Dockerfile that pulled it all together.
from dotnet-framework-docker.
Just one more idea... is .NET Framework an optional component on Server Core? As in, could it be removed with a dism
command or similar, perhaps? If so, we could do that in the dockerfile then install 4.5.x
from dotnet-framework-docker.
That's an interesting q. It might be. You'd have to try.
from dotnet-framework-docker.
I'm going to close this issue. There is no official product direction on this and no obvious guidance for me to give you. I gave you another Microsoft contact offline for you to brainstorm with on possible avenues to make this work for your scenario.
from dotnet-framework-docker.
i would vote for this. just trying to setup a ci with docker, and its not possible to compile our 4.5.2 projects 👎
from dotnet-framework-docker.
@Vittel, it sounds like you want to vote for it, but you gave it a thumbs down, so I'm a bit confused.
Also, you don't need this to compile 4.5.2 projects, since you can target net452 even with the net46 runtime on the box. You just need the net452 targeting pack installed.
I need this because I want to run tests on the net452 runtime.
from dotnet-framework-docker.
Was a thumbs down for closing the ticket.
Also what you just wrote is absolutely correct as i had figured out earlier. My ci container is up and running :)
from dotnet-framework-docker.
@Vittel, what @AArnott says is correct. You don't need his proposal for your needs. What would benefit you is: #37. We intend to add a .NET Framework 4.5.2 targeting pack as part of that PR (or a later one).
from dotnet-framework-docker.
@richlander thanks for confirming. also: #24 (comment) 💃
from dotnet-framework-docker.
Related Issues (20)
- Feature Request: Framework SDK Images based on Full Windows HOT 1
- unable to clone git repo, what is the solution for this. HOT 1
- Unable to install Latest Visual C++ Redistributable in Windows Containers HOT 1
- Unable to add any workloads/components
- Could not find a base address that matches scheme net.tcp for the endpoint with binding NetTcpBinding. Registered base address schemes are [http]. HOT 3
- Can no longer add Microsoft.VisualStudio.Component.SQL.SSDTBuildSku component to image HOT 4
- DOTNET_RUNNING_IN_CONTAINER not set in LTSC2019 windows docker images HOT 1
- Docker builds failed for framework/aspnet:4.8-windowsservercore-ltsc2022 HOT 1
- Revert disabling of prebuild validation
- Automate the collection of release data and update the appropriate files HOT 2
- Investigate how to migrate off of Windows Server 2016 build agents HOT 1
- "Related repositories" links broken in MAR
- msbuild suceeded for net48 and net462 solutions but no dll files generated HOT 5
- Running simple visual basic script for unzipping a zip file throws Unspecified Error HOT 1
- New-IISSiteBinding command not present in latest mcr.microsoft.com/dotnet/framework/wcf:4.8 HOT 7
- Example of logging support
- Install 4.8.1 targeting pack HOT 3
- Remove installation of .NET 5 runtime in SDK images
- Remove .NET Core 3.1 runtime from SDK when unsupported HOT 1
- Include .NET 7 runtime in SDK images when it is GA
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from dotnet-framework-docker.