Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rewrite the .NET Framework story for the install docs #44426

Closed
7 tasks done
adegeo opened this issue Jan 18, 2025 · 0 comments · Fixed by #44900
Closed
7 tasks done

Rewrite the .NET Framework story for the install docs #44426

adegeo opened this issue Jan 18, 2025 · 0 comments · Fixed by #44900
Assignees
Labels
dotnet-framework/svc in-pr This issue will be closed (fixed) by an active pull request. install-deployment/subsvc 📌 seQUESTered Identifies that an issue has been imported into Quest. resolved-by-customer

Comments

@adegeo
Copy link
Contributor

adegeo commented Jan 18, 2025

Type of issue

Missing information

Description

The information about 1.1 is sort of messed up, along with a lot of other stuff. Parts of the docs say that the app vendor needs to upgrade to 2.0, while others say it's supported. It's possible that specific features of 1.1 can't run on modern Windows, I just don't know unless I find an extremely complex app to test with. I did use Windows XP and Visual Studio 2003 to create some 1.1 apps. Running them on Windows 11 prompted me to install 3.5. After the install finished, the 1.1 apps worked.

The install docs for all of Windows and Windows Server should be simplified.

Todo:

  • Check on the app manifest supporting an upgrade to .NET Framework 4.
    See if this actually works or not. Perhaps tweak the 1.1 sample I made to output the current .NET Framework runtime it's running on.
  • Clean up all references to 1.1.
  • Find out if there's something special about 1.1. Why don't the references just say 1.0?
  • Windows 11 article has the instructions for server. Fix this
  • Merge the different install articles into one with support + instructions
  • Retire individual articles
  • Upgrade screenshots

Page URL

https://learn.microsoft.com/en-us/dotnet/framework/install/run-net-framework-1-1-apps?source=recommendations

Content source URL

https://github.com/dotnet/docs/blob/main/docs/framework/install/run-net-framework-1-1-apps.md

Document Version Independent Id

456e8771-1cfb-8775-47d9-ca0ea23b795d

Article author

@adegeo

Metadata

  • ID: 9a97c8bd-53e6-c249-2429-2494ba576434
  • Service: dotnet-framework
  • Sub-service: install-deployment

Related Issues


Associated WorkItem - 363613

@adegeo adegeo self-assigned this Jan 18, 2025
@dotnet-policy-service dotnet-policy-service bot added the ⌚ Not Triaged Not triaged label Jan 18, 2025
@adegeo adegeo added 🗺️ reQUEST Triggers an issue to be imported into Quest. doc-enhancement and removed ⌚ Not Triaged Not triaged labels Jan 18, 2025
@dotnetrepoman dotnetrepoman bot added the 🗺️ mapQUEST Only used as a way to mark an issue as updated for quest. RepoMan should instantly remove it. label Jan 18, 2025
@dotnet-policy-service dotnet-policy-service bot removed the 🗺️ mapQUEST Only used as a way to mark an issue as updated for quest. RepoMan should instantly remove it. label Jan 18, 2025
@sequestor sequestor bot added 📌 seQUESTered Identifies that an issue has been imported into Quest. and removed 🗺️ reQUEST Triggers an issue to be imported into Quest. labels Jan 18, 2025
@adegeo adegeo moved this from 🔖 Ready to 🏗 In progress in dotnet/docs February 2025 sprint project Feb 5, 2025
@dotnetrepoman dotnetrepoman bot added the 🗺️ mapQUEST Only used as a way to mark an issue as updated for quest. RepoMan should instantly remove it. label Feb 5, 2025
@dotnet-policy-service dotnet-policy-service bot removed the 🗺️ mapQUEST Only used as a way to mark an issue as updated for quest. RepoMan should instantly remove it. label Feb 5, 2025
@dotnetrepoman dotnetrepoman bot added the 🗺️ mapQUEST Only used as a way to mark an issue as updated for quest. RepoMan should instantly remove it. label Feb 14, 2025
@adegeo adegeo changed the title Rewrite the .NET Framework 1-3.5 story for the install docs Rewrite the .NET Framework story for the install docs Feb 14, 2025
@dotnet-policy-service dotnet-policy-service bot removed the 🗺️ mapQUEST Only used as a way to mark an issue as updated for quest. RepoMan should instantly remove it. label Feb 14, 2025
@adegeo adegeo moved this from 🏗 In progress to 👀 In review in dotnet/docs February 2025 sprint project Feb 18, 2025
@dotnetrepoman dotnetrepoman bot added the 🗺️ mapQUEST Only used as a way to mark an issue as updated for quest. RepoMan should instantly remove it. label Feb 18, 2025
@dotnet-policy-service dotnet-policy-service bot removed the 🗺️ mapQUEST Only used as a way to mark an issue as updated for quest. RepoMan should instantly remove it. label Feb 18, 2025
@dotnet-policy-service dotnet-policy-service bot added the in-pr This issue will be closed (fixed) by an active pull request. label Feb 20, 2025
@github-project-automation github-project-automation bot moved this from 👀 In review to ✅ Done in dotnet/docs February 2025 sprint project Feb 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dotnet-framework/svc in-pr This issue will be closed (fixed) by an active pull request. install-deployment/subsvc 📌 seQUESTered Identifies that an issue has been imported into Quest. resolved-by-customer
Projects
No open projects
Development

Successfully merging a pull request may close this issue.

2 participants