4 ms·
Xaml hot reload only works on about half of our views at work, and even then it tends to break itself. I've tried net framework, net core, and net 5. The newer
by eyegor 6y ago
Xaml hot reload only works on about half of our views at work, and even then it tends to break itself. I've tried net framework, net core, and net 5. The newer targets break less often but we still can't ship net 5 thanks to Windows 7 extended support contracts from Microsoft. It doesn't even compare to blazors implementation. And c# hot reload breaks frequently around asyncs and lambdas.
- GiorgioG 6y ago> The newer targets break less often but we still can't ship net 5 thanks to Windows 7 extended support contracts from Microsoft You make it sound like it's Microsoft's fault your customers won't move off of Windows 7.
- mattmanser 6y agoHe has a point, for example now they've finally stopped supporting IE11 you can legitimately say to customers that supporting IE11 is no longer possible because it's a security hole. Extended support by MS for Windows 7 means the only reason you're not supporting it yourself is your lack of motivation, and so to your customers (and your own upper management), for a big contract that's not going to wash. You might even find that their contract even says something to that effect.
- miffy900 6y agoI may be misreading your comment, but in case you're not aware .NET 5 supports Windows 7 as a deployment platform: https://github.com/dotnet/core/blob/main/release-notes/5.0/5.0-supported-os.md https://github.com/dotnet/core/blob/main/release-notes/5.0/5... And it does not specifically require any paid extended support contract from Microsoft to actually install and run.