![]() If you don't see an answer to your question here, check our previously reported issues on GitHub and our release notes. We've captured items here that don't fit in the other topics. Our docs contain a Common questions section as needed for specific topics. ![]() Configure IntelliSense for cross-compiling.Just yesterday I made money installing on a customer's laptop with Windows 7. ![]() In closing here's an anecdote: I made an accounting system 10yrs ago that runs on. which is not going to be nice at all if it happens). if Visual Studio 2023 comes out and is only supported for. My only request is you don't put a constraint on the versions of Visual Studio we can use (e.g. So while time marches on and we all eventually have to upgrade, it's important to keep in mind not only the cost for Microsoft to keep supporting old versions, but also the cost of upgrades for the many many more people out there who may have to buy new hardware in order to get new software (rarely a good deal, cost-wise). NET 6 means buying a new developer-grade laptop (that's a $2,000+ investment). My immediate reaction to this announcement was "I won't use. It is perfectly functional and likely to have a few more years of life in it (Toshiba used to build them good!). I have a ten year old laptop that runs Windows 8.1. I understand the theory behind this change but in practice it is going to make a lot of people unhappy (and "a lot" here means "more than you could initially imagine"). Doing so would be mean and very unfriendly.NET 6 should work fine (in an unsupported configuration) on Windows 7 well into the future. You should just accept that the environment isn't getting any more care and feeding.Īgain, we're NOT going to add blocks on. NET (in a given environment) when the more foundational operating system is already end-of-life. To my mind, it is incongruent to expect the. NET team won't support them either? It's a much bigger deal that the operating system isn't supported. Your users are not receiving patches for security, crashes, timezone updates, or new hardware. However, you already have to accept that the Windows team is not supporting your users on Windows 7. We're not going to block you from doing that. let's say you have an app and you want to sell it to or support in Windows 7. I want to make a more general observation. We encourage you to migrate to Windows 10 or 11 if you would like to use. Windows Server 2016+ will be supported throughout. NET 7 General Availability) to a newer operating system or plan to purchase Windows Server ESU. NET 7 on Windows Server 2012/R2 unless you have a migration plan (within a year of. NET 8, assuming you have purchased ESU updates. We will offer support for Windows Server 2012/R2 throughout. Windows Server 2012/R2 ESU will start mid-way through the. At that time, Windows 8.1 will no longer be supported with. Windows 8.1 is supported until January 2023. At that time, Windows 7 will no longer be supported with. Windows 7 will be supported for those organizations until the ESU offering ends, which is January, 2023. NET 6) for organizations that have purchased Extended Security Updates (ESU). Windows 7 and Windows 8.1 are currently supported with. NET support for Windows 7 and 8.1 will end in January 2023
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |