Point the manual .NET 1.1 install using tools instead of mentioning vendors being required #44395
Conversation
dotnet-policy-service
bot
added
dotnet-framework/svc
install/subsvc
community-contribution
The same link is already added to the 'See also' section, so it is not reuired to be left in the original text, especially being out of context when the previous part has changed.
|
Hey @BartoszKlonowski thanks for doing this. I was just looking a little more into this issue and I'm unsure if this is actually correct. It may be that the doc says 3.5 supports 1.0-3.5 apps, but that might not be true. I'm seeing a lot of supplemental information on the net that talks about 1.1 needing a separate install. I think we need to do some testing before we know what the correct statement is. 1.1 may be treated differently than 1.0. |
|
I went down memory lane and spun up a Windows XP VM with VS 2003 and created two .NET Framework 1.1 apps, winforms and a console app. Then I had Azure create a Windows 11 machine and I tried running those apps. I was prompted to install .NET Framework 3.5 After it installed, both apps were able to run. |
|
Thanks @BartoszKlonowski ! |
This pull request fixes #44186
It replaces the vendors being required sentence with the link to installing the .NET 1.1 as suggested in the issue.
Internal previews