The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
I've always found that no matter how good a hand-over is, it's never good enough.
You lucky people even have handovers? Here I only recieve the the team project name in tfs and the production url. Best part of it is that, at the same time, I also inherit client's who have no idea how the application is expected to work(In new recruits), so we both learn together and redefine the requirements in change requests
I don't quite get this...
.NET Core is supposed to be multi-platform, right?
And now they're including technology that is not multi-platform...
If they include just a little bit more it's just .NET Framework again, but with some multi-platform parts.
The .NET Core runtime is definitely cross platform, but it's always been possible to write .NET Core libraries that only work on one platform. You can PInvoke Win32 and GDI functions in a .NET Core application today, and that definitely won't work anywhere other than Windows.
This is sort of the same thing - .NET Core itself is still cross platform, but if you want to make a WPF or WinForms app, you'll have to add a few Windows specific DLLs to your app bundle to make it happen. It probably makes sense to look at the WPF and WinForms functionality as NuGet packages that you can pull in when you need them. I think in one of the demos Scott Hunter did, he just added WinForms as a package reference in the csproj file.
The .NET core remains multiplatform.
But it now has the opportunity to use platform specific code, when available.
Of course the result application (using platform specific code) is not multiplatform hey?
This, however, comes with many advantage for the application developer. You can take advantage of .NET Core functionality in your platform specific app, such as:
- performance enhancement
- self contained deployment (doesn't depends on OS version of .NET)
- native compilation.
Because .NET Framework 4.8 wont support many of the new features .NET Core 3.0 will.
.NET Framework will move much slower and isn't compatible with .NET Standard 2.1 and thus for new projects looking to take advantage of new .NET Standard 2.1+ features and use WPF on Windows for Win32 apps, you will need to target .NET Core 3.0+ which has a newer .NET Runtime.
I'm glad you've found culture and enlightenment, but no, you never use Tea in a Tim Tam Slam. Ever.
And the instructions should be more accurate: you bite off the corners - about 1cm each end, biting off diametrically opposite ends. You can bite off the entire end if you are careful and only bite off the minimum, but we all know through Bernoulli's equation that fluid flow increases with decreasing cross sectional area, so go the corners not the full end.
A little over a month into the AI TensorFlow Challenge and we have 130 participants who've tried out the AI TensorFlow Tutorial, and about 80 who've successfully completed all 5 steps of the tutorial - way to go! The first 100 participants to complete the entire tutorial will win themselves a $25 Amazon.com gift card, and we also have $2,500 in article prizes up for grabs. Early Christmas shopping anyone?
Also, if you found the tutorial useful and are looking to learn more about TensorFlow, Packt Publishing is offering a free Getting Started with TensorFlow eBook. Check it out and let us know your thoughts.