Is this supposed to work for win 7? Because it sure don’t for me. Changing
dotnet publish -r win10-x64 -c Release --self-contained .\DevComrade
to
dotnet publish -r win7-x64 -c Release --self-contained .\DevComrade
doesn’t seem to fix it.
Installer for .NET SDK claims to have worked without errors.
Thanks.
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Windows 7
Windows 7 is a major release of the Windows NT operating system developed by Microsoft. It was released to manufacturing on July 22,...
Read more >Windows 7 - Microsoft Lifecycle
Windows 7 follows the Fixed Lifecycle Policy. This applies to the following editions: Enterprise, Enterprise N, Home Basic, Home Premium, Home Premium N, ......
Read more >Software Download
Windows. Windows 11 on a laptop. Windows 11 · Windows 10 on a laptop. Windows 10 · Windows 8.1 on a laptop. Windows...
Read more >Windows 7 support ended on January 14, 2020
The specific end of support day for Windows 7 was January 14, 2020. Technical assistance and software updates from Windows Update that help ......
Read more >Install Windows 7 Service Pack 1 (SP1)
Learn how to install Windows 7 Service Pack 1 (SP1). Includes info about how to get the download, requirements, and more.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

Thanks anyway. I know how it is about time. AT the beginning it seems like there’s plenty of time, later, not so much.
If I find a way to make it work on win 7, I’ll post back.
–peter
On 2/13/2022 1:07 PM, Andrew Nosenko wrote:
Thanks. That doesn’t work, either, though leads to fewer errors.
It seems that maybe .NET wants some win 7 specific features that don’t actually exist in .NET 6? (Probably MS made no effort to support win 7 in NET 6, I guess.)
I wonder if an executable built under win 10 would run in win 7. Not near my win 10 machine right now.
Here are the errors: (“…” replacing my long path)
…\DevComrade\DevComrade.csproj : error NU1100: Unable to resolve ‘Microsoft.CodeAnalysis.CSharp.Scripting (>= 4.0.0-6.final)’ for ‘net6.0-windows7.0’.
…\AppLogic\AppLogic.csproj : error NU1100: Unable to resolve ‘Microsoft.CodeAnalysis.CSharp.Scripting (>= 4.0.0-6.final)’ for ‘net6.0-windows7.0’. [C:\pctools\windows-utilities\clipboard\formatting-stripper\DevComrade\devcomrade-main\DevComrade\DevComrade.csproj]
…\AppLogic\AppLogic.csproj : error NU1100: Unable to resolve ‘System.Configuration.ConfigurationManager (>= 6.0.0-rc.2.21480.5)’ for ‘net6.0-windows7.0’. [C:\pctools\windows-utilities\clipboard\formatting-stripper\DevComrade\devcomrade-main\DevComrade\DevComrade.csproj]
…\DevComrade\DevComrade.csproj : error NU1100: Unable to resolve ‘System.Configuration.ConfigurationManager (>= 6.0.0-rc.2.21480.5)’ for ‘net6.0-windows7.0’.
Failed to restore …\DevComrade\DevComrade.csproj (in 177 ms). Failed to restore …\AppLogic\AppLogic.csproj (in 177 ms).
Regardless, thanks for the help, and the code.
–peter
On 2/12/2022 2:08 PM, Andrew Nosenko wrote: