Re: Always seemed an uphill task
Don't forget that Microsoft are bringing out MAUI (Multi-Platform Application User Interface) in .NET 5
462 posts • joined 21 May 2009
"Isn't that what .NET 5.0 is?"
No it isn't. .NET 5 is .NET Core. It was going to be .NET Core 4. But, Microsoft decided to rename it so not to confuse it with .NET Framework 4.x.
But it will confuse the hell out of developers when their Framework project is moved to .NET 5 and there are a ton of breaking changes.
I got a call from my cousin that needed help with setting up a "home office" yesterday.
The company she works for have told all their staff to work from home due to the coronavirus.
Their IT Dept. just dropped off the equipment at her house and left her to set it up.
Got the computer up and running and connecting to their VPN but not the VOIP telephone. It required configuring and there were no instructions. At least she can email the IT Dept and vent at them.
Frankly, the requirements docs were nonsensical and had little bearing on what the customer actually wanted
What they ask for and what they want are two different things. That's 99.9% of all requirement docs.
Just easier to bypass the Project Managers and talk directly to the people that will use the actual thing to get an idea of what is actually required.
So can the United Kingdom of Great Britain and Northern Ireland lose UK if it loses N.I.?
If Northern Ireland separated from the UK, the UK would become Kingdom of Great Britain.
If Scotland got their indepedence, KGB would become Kingdom of England (England and Wales)
If Wales then got independence, we will still be Kingdom of England.
Question is would we get the tld for .kgb or .ke?
If Scotland has independence, would we also lose .gb?
However, it is still a confusing picture, especially for .NET developers who bought into XAML and WPF or perhaps Silverlight, a cross-platform version of WPF which a decade ago looked like it might be the future. One of the annoyances is that WinUI XAML is different from WPF XAML, and Xamarin Forms XAML different again, with no easy porting between the three
Micosoft needs to unify XAML so it's the same across WPF, WinUI and Xamarin. Converting WPF to .NET Core and the development of Xamarin Forms 4 would have been the perfect time. Maybe rethink it in Xamarain Forms 5 when .NET 5 comes out next year.
As for XAML Island, when it was introduced it just felt like a stop gap that would last a couple of years.
Many many moons ago, once had one where the user could not understand that when they edited and saved a document from an email attachment, that all their changes have "gone" when they reopen the email attachement. I had to train them to save the attachement in My Documents first, then edit the document and if they needed to edit the document again to use the one in My Documents, not resave the attachment then edit it...
As a full stack developer I even cring at databases being created with the default settings of Entity Framework especially NVARCHAR(MAX). I prefer creating databases the right way with T-SQL.
There's been a few colourful words while "fixing" this mess. In the end, the database performance has improved considerably.
Biting the hand that feeds IT © 1998–2020