I do mainly desktop dev but reading that Core is now the platform with rapid improvements I wonder if it's possible to write WPF or UWP apps with .NET Core or Standard. Does anyone know?
[deleted]
.NET Standard 2.1
21–30 of 124 posts
Re: .NET Standard 2.1
#22I do mainly desktop dev but reading that Core is now the platform with rapid improvements I wonder if it's possible to write WPF or UWP apps with .NET Core or Standard. Does anyone know?
This is coming in .NET Core 3. Slated for Q1 2019 AFAIK. https://blogs.msdn.microsoft.com/dotnet/2018/05/07/net-core-...
Very good. For a moment I was worried that desktop development would stay on Framework which from the article seems to slowly being pushed into maintenance mode.
Re: .NET Standard 2.1
#23I do mainly desktop dev but reading that Core is now the platform with rapid improvements I wonder if it's possible to write WPF or UWP apps with .NET Core or Standard. Does anyone know?
Not WPF per se, but if you're looking for something similar check out https://github.com/AvaloniaUI/Avalonia
Re: .NET Standard 2.1
#24I do mainly desktop dev but reading that Core is now the platform with rapid improvements I wonder if it's possible to write WPF or UWP apps with .NET Core or Standard. Does anyone know?
This is coming in .NET Core 3. Slated for Q1 2019 AFAIK. https://blogs.msdn.microsoft.com/dotnet/2018/05/07/net-core-...
If WPF is coming in .NET Core, does this mean we are going to be able to run WPF apps on Linux and Mac?
Re: .NET Standard 2.1
#25Earlier quoted context omitted.
This is coming in .NET Core 3. Slated for Q1 2019 AFAIK. https://blogs.msdn.microsoft.com/dotnet/2018/05/07/net-core-...
If WPF is coming in .NET Core, does this mean we are going to be able to run WPF apps on Linux and Mac?
I highly doubt it. As far as I know WPF is way too entangled with Windows.
Re: .NET Standard 2.1
#26So they added Span as a big thing ...
> (Span is) at the heart of most performance-related improvements in .NET Core 2.1. Since it allows managing buffers in a more efficient way, it can help in reducing allocations and copying. We consider Span to be a very fundamental type as it requires runtime and compiler support in order to be fully leveraged.
Small struct that is declared as
public readonly ref struct Span
{
private readonly ref T _pointer;
private readonly int _length;
...
}
template
struct slice {
const T* start;
unsigned int length;
...
}
Such small thing definitely speed ups many areas and surprisingly quite a lot, parsing in particular.
Nothing new under the Sun, eh?
Re: .NET Standard 2.1
#27Re: .NET Standard 2.1
#28Earlier quoted context omitted.
This is coming in .NET Core 3. Slated for Q1 2019 AFAIK. https://blogs.msdn.microsoft.com/dotnet/2018/05/07/net-core-...
If WPF is coming in .NET Core, does this mean we are going to be able to run WPF apps on Linux and Mac?
Nope, it will be a windows only capability.
-Edit-
I should add that the purpose of them adding this capability isn't to set up a new cross-platform UI suite. It is just to lure enterprise shops to .NET core by supporting more of their .NET Framework workloads
Re: .NET Standard 2.1
#29I thought we already have .NET 4. I don't understand.
Re: .NET Standard 2.1
#30So they added Span as a big thing ... > (Span is) at the heart of most performance-related improvements in .NET Core 2.1. Since it allows managing buffers in a more efficient way, it can help in reducing allocations and copying. We consider Span to be a very fundamental type as it requires runtime and compiler support in order to be fully leveraged. Small struct that is declared as public readonly ref struct Span { p…
Does your template work with memory managed by a GC and provide all the memory safety guarantees that .NET does? If so, does it work seamlessly across the stack & the heap for both managed memory and unmanaged memory at the same time?
I get it, similar concepts - but let's not dismiss the value in this addition.