All these Build videos are mixed with the audio so low that we have to crank our volumes to hear them... so if sound happens from somewhere else on our devices ... BAM! We are blasted out of our chairs.
As a temporary fix: Right click the volume icon in the system tray, click Open Volume Mixer. Turn up the volume for the browser video, then turn down the system sounds volume.
both Apple and Google created new UI framework to make ui with Swift / Kotlin, without XAML or extra steps, this is the future, WPF isn't what .net core need, it needs a TRUE modern UI framework in C# only
I have written a poem to support .NET :d .NET .NET you are the old ones, But don't you'll able to compete everyone Time and again you compete with trends, People say you are but loved enterprise ones! .NET .NET with .NET Core you'll be the future! :D #DevOTram
I've been trying to replicate the location app on this video but as soon as I put in the MapControl the xaml designer breaks and the app no longer compiles. Any thoughts?
So why isn't this titled 'Building .net desktop applications with UWP' - I thought that was the future of Windows. Now I'm confused. And yes I understand the relationship between UWP and .net core to an extent. But is UWP a dead end? UWP was meant to be the Windows head of the .net core body, now .net core has it's own head.
Because if you are looking to specifically target Windows PC's you would make a WPF application, Universal Windows Platform is designed to be generic and work universally across Windows 10, Windows 10 Mobile, Xbox One and HoloLens without having to re-write for each platform.
@Tyler K is not dead I am developing a point of sale based on UWP, I can print receipts, use sqlite or sqlserver as data base, export reports to excel, create pdf file as report.
@Tyler K No i do not wasting time, i already used the benefits of UWP for example creating an app package for distribution and install the app, on Windows form or WPF you do not have this benefit, you need third parties to create an installer, other benefit is UWP controls, third parties controls to enhance the Xaml controls, alot of libraries of xaml control or c# libraries. Open serial ports, Payment gateway. you can use Win32 libraries on UWP
This is a deadblow to .NET desktop. Watch out: if there is a security issue in .Net, you now have to update all your distributed apps yourself. Now you are resposible for patching microsoft .net security updates.
This is all about changing the target .Net version in the package, for the newer subpackage to apply and rebuilding the app. But Flatpaks at least have runtimes which can update separately, so, MSIX gone all the Snap way bundling everything.
No, it's fantastically great that there is no support for *obsolete* operating systems. Windows 10 has been out for 4 years. If you're still running Windows 7 or 8 then shame on your organization for choosing to be left behind.
@@bguen1234 I work for big outsourcing company and I can definitely tell that most of large financial companies (1k+ employees) did not update their park of machines to win 10 because everything works as it is and such massive change will bring losses in time and obviously money. Even small product companies have to support wide range of OSes targeting large audience. So no, there is no reason to drop support for 30-50% of users taking in account that core3 would work on win 7+, but Microsoft does not want it to.
@@Chipsaru With support of Windows 7 ending on January 14, 2020 and Core 3 looking to release in September 2019 it doesn't make much sense for them to support Windows 7. If you have legacy systems then you can still use the .net framework as @Ravian X Reaver pointed out. I'm sure many companies will be running OS's that are not supported leaving themselves vulnerable to attack, such as the ransomware and Windows XP issues but, that doesn't mean that Windows should encourage that sort of behaviour.
@@DogDemuro I successfully ported to 2 WPF applets to .net core 3.0 preview 5. Now I want to move some classes and WPF UserControls into a .Net Standard 2.0 library to use between .net 4.x and .net core 3. Where is the best place to post my errors? I set a library to use Net standard (2.0.3), with the MS.Win.SDK.Contracts latest preview, with assemblies added: WindowsBase from 4.7.2. Visual Studio 2019 suggested adding System.Widows.Forms from the netcoreapp3.0 folder. Now there is a conflict Error CS7069 Reference to type 'Component' claims it is defined in 'System.ComponentModel.Primitives', but it could not be found
@@DogDemuro Unable to port one of my base libraries because I use the dynamic keyword. I get the following 2 errors: Missing compiler required member 'Microsoft.CSharp.RuntimeBinder.CSharpArgumentInfo.Create' Missing compiler required member 'Microsoft.CSharp.RuntimeBinder.Binder.Convert' I should add that I followed the Port desktop apps to net core 3.0 documentation. I first want my library to be netstandard2.0. Added Microsoft.Windows.Compatibilty pack. The API Analyzer gave my project a score of 100%.
@@AdamsTaiwan can you reach out to us at netcore3modernize @ microsoft dot com? If you could provide some context (what kind of applications you're working to port, what is motivating you to port, and what challenges you've been encountering), someone should be able to help you! Also, if you have any steps or sample projects to reproduce the issues you're encountering, that will probably speed things up from our end. Looking forward to hearing from you soon!
Because what you learn for core isn't dead, it's just merging into .NET 5.0. So you'll have Span, etc. everywhere and you don't need to guess which .NET framework your target PC has.
Because as Microsoft has said, .net 5.0 is really just .NET Core vNext. And if people want to still call it .Net Core then go right ahead. The reason they are calling it .Net 5 is because they are attempting to merge them all together.
As others have pointed out, you have got the wrong end of the stick on this one. Full quote below: "We’re skipping the version 4 because it would confuse users that are familiar with the .NET Framework, which has been using the 4.x series for a long time. Additionally, we wanted to clearly communicate that .NET 5 is the future for the .NET platform. We are also taking the opportunity to simplify naming. We thought that if there is only one .NET going forward, we don’t need a clarifying term like “Core”. The shorter name is a simplification and also communicates that .NET 5 has uniform capabilities and behaviors. Feel free to continue to use the “.NET Core” name if you prefer it." Source: devblogs.microsoft.com/dotnet/introducing-net-5/
It won't. .NET 5 will be the next version of .NET Core after 3.0. It just drops the "Core" name because there will be no need to clarify that it's Core since there will be no other .NET other than Core at that point.
i want a new winforms designer as good or better than the current in winforms Core.- otherwise nobody will move their projects there. unfortunately we need and 3rd parties to work on that "conversion too" like devexpress....
If talking about an Intranet application (no MS Store), with your business logic, based on DAX for example, you sometimes would want autoupdates without notice, because your users are too stupid to know about what are updates and why should they FUCKING STOP THEIR WORK TO INSTALL THEM AAAAAARRRRRHHHH. But they have enough brain to work at the store.
What you would expect from Microsoft, lol? Also, Linux has it's own similar solutions like Flatpak. Or you would expect Microsoft to create a cross-platform Bluetooth library and maps? :D
@@llo5673 .Net Core is truly cross-platform. WPF and Microsoft Windows 10 UWP API's - not. Except, by cross-platform you mean "It will run and work on all Microsoft platforms, like Xbox and Windows"
![Chino Pacas - Modo Capone (with Drake & Fuerza Regida) [Video Oficial]](http://i.ytimg.com/vi/zjv8TQ0gBkg/mqdefault.jpg)
All these Build videos are mixed with the audio so low that we have to crank our volumes to hear them... so if sound happens from somewhere else on our devices ... BAM! We are blasted out of our chairs.
As a temporary fix: Right click the volume icon in the system tray, click Open Volume Mixer. Turn up the volume for the browser video, then turn down the system sounds volume.
She's amazing
both Apple and Google created new UI framework to make ui with Swift / Kotlin, without XAML or extra steps, this is the future, WPF isn't what .net core need, it needs a TRUE modern UI framework in C# only
Hoowwwww thats the only thing here
No one is mentioning how beautiful she is?
Btw, great presentation.. Lot of details packed in it and worth a watch
A ton of great info here, thank you!! Good job on your presentation too!
I have written a poem to support .NET :d
.NET .NET you are the old ones,
But don't you'll able to compete everyone
Time and again you compete with trends,
People say you are but loved enterprise ones!
.NET .NET with .NET Core you'll be the future!
:D #DevOTram
I would like to start using .NET CORE 3. To make an updater/launcher program for a videogame. Please can you recommend me some material to start?
Reynaldo Bernard De Dios De La Cruz
Well dont use .net for this
I've been trying to replicate the location app on this video but as soon as I put in the MapControl the xaml designer breaks and the app no longer compiles. Any thoughts?
What I don’t get is why winforms is not getting ef core and stuck with the slow 6.3
So why isn't this titled 'Building .net desktop applications with UWP' - I thought that was the future of Windows. Now I'm confused. And yes I understand the relationship between UWP and .net core to an extent. But is UWP a dead end? UWP was meant to be the Windows head of the .net core body, now .net core has it's own head.
Because if you are looking to specifically target Windows PC's you would make a WPF application, Universal Windows Platform is designed to be generic and work universally across Windows 10, Windows 10 Mobile, Xbox One and HoloLens without having to re-write for each platform.
@@FATPENGUIN96 you can use it for windows IoT as well.
UWP it is only run in Windows 10 if you are developing a WPF app you have the XAML controls of UWP and the App Package.
@Tyler K is not dead I am developing a point of sale based on UWP, I can print receipts, use sqlite or sqlserver as data base, export reports to excel, create pdf file as report.
@Tyler K No i do not wasting time, i already used the benefits of UWP for example creating an app package for distribution and install the app, on Windows form or WPF you do not have this benefit, you need third parties to create an installer, other benefit is UWP controls, third parties controls to enhance the Xaml controls, alot of libraries of xaml control or c# libraries. Open serial ports, Payment gateway.
you can use Win32 libraries on UWP
This is a deadblow to .NET desktop. Watch out: if there is a security issue in .Net, you now have to update all your distributed apps yourself. Now you are resposible for patching microsoft .net security updates.
This is all about changing the target .Net version in the package, for the newer subpackage to apply and rebuilding the app.
But Flatpaks at least have runtimes which can update separately, so, MSIX gone all the Snap way bundling everything.
It is a shame there is no support for win 7/8/8.1. Enterprises use them still and upgrading your app means support for older platforms too.
Winforms, WPF support 7/8/8.1
@@RavianXReaverdid you watch this video? It is not in combination with core 3 or MSIX installer or app package
No, it's fantastically great that there is no support for *obsolete* operating systems. Windows 10 has been out for 4 years. If you're still running Windows 7 or 8 then shame on your organization for choosing to be left behind.
@@bguen1234 I work for big outsourcing company and I can definitely tell that most of large financial companies (1k+ employees) did not update their park of machines to win 10 because everything works as it is and such massive change will bring losses in time and obviously money. Even small product companies have to support wide range of OSes targeting large audience. So no, there is no reason to drop support for 30-50% of users taking in account that core3 would work on win 7+, but Microsoft does not want it to.
@@Chipsaru With support of Windows 7 ending on January 14, 2020 and Core 3 looking to release in September 2019 it doesn't make much sense for them to support Windows 7. If you have legacy systems then you can still use the .net framework as @Ravian X Reaver pointed out. I'm sure many companies will be running OS's that are not supported leaving themselves vulnerable to attack, such as the ransomware and Windows XP issues but, that doesn't mean that Windows should encourage that sort of behaviour.
“Ask the app developer for a new app package. This one isn’t signed with a trusted certificate (0x800B0100)” error message.
I'm having trouble moving a WPF library file to .net standard 2.0.
Is it a .NET Framework Class Library application? How can we help?
@@DogDemuro I successfully ported to 2 WPF applets to .net core 3.0 preview 5. Now I want to move some classes and WPF UserControls into a .Net Standard 2.0 library to use between .net 4.x and .net core 3. Where is the best place to post my errors?
I set a library to use Net standard (2.0.3), with the MS.Win.SDK.Contracts latest preview, with assemblies added: WindowsBase from 4.7.2. Visual Studio 2019 suggested adding System.Widows.Forms from the netcoreapp3.0 folder.
Now there is a conflict Error CS7069 Reference to type 'Component' claims it is defined in 'System.ComponentModel.Primitives', but it could not be found
@@DogDemuro Unable to port one of my base libraries because I use the dynamic keyword. I get the following 2 errors:
Missing compiler required member 'Microsoft.CSharp.RuntimeBinder.CSharpArgumentInfo.Create'
Missing compiler required member 'Microsoft.CSharp.RuntimeBinder.Binder.Convert'
I should add that I followed the Port desktop apps to net core 3.0 documentation. I first want my library to be netstandard2.0. Added Microsoft.Windows.Compatibilty pack. The API Analyzer gave my project a score of 100%.
@@AdamsTaiwan can you reach out to us at netcore3modernize @ microsoft dot com? If you could provide some context (what kind of applications you're working to port, what is motivating you to port, and what challenges you've been encountering), someone should be able to help you!
Also, if you have any steps or sample projects to reproduce the issues you're encountering, that will probably speed things up from our end.
Looking forward to hearing from you soon!
1st , I use vs code, will study back end later
why learn core when .net 5.0 will kill it all?
Because what you learn for core isn't dead, it's just merging into .NET 5.0. So you'll have Span, etc. everywhere and you don't need to guess which .NET framework your target PC has.
Because as Microsoft has said, .net 5.0 is really just .NET Core vNext. And if people want to still call it .Net Core then go right ahead. The reason they are calling it .Net 5 is because they are attempting to merge them all together.
As others have pointed out, you have got the wrong end of the stick on this one. Full quote below:
"We’re skipping the version 4 because it would confuse users that are familiar with the .NET Framework, which has been using the 4.x series for a long time. Additionally, we wanted to clearly communicate that .NET 5 is the future for the .NET platform.
We are also taking the opportunity to simplify naming. We thought that if there is only one .NET going forward, we don’t need a clarifying term like “Core”. The shorter name is a simplification and also communicates that .NET 5 has uniform capabilities and behaviors. Feel free to continue to use the “.NET Core” name if you prefer it."
Source: devblogs.microsoft.com/dotnet/introducing-net-5/
It won't. .NET 5 will be the next version of .NET Core after 3.0. It just drops the "Core" name because there will be no need to clarify that it's Core since there will be no other .NET other than Core at that point.
Tyler K
Its partial true. Windows Applications are NOT cross platform.
i want a new winforms designer as good or better than the current in winforms Core.- otherwise nobody will move their projects there.
unfortunately we need and 3rd parties to work on that "conversion too" like devexpress....
26:50 updates without informing the user? yeah those annoying things win10 does we dont want that in our apps and clients!
If talking about an Intranet application (no MS Store), with your business logic, based on DAX for example, you sometimes would want autoupdates without notice, because your users are too stupid to know about what are updates and why should they FUCKING STOP THEIR WORK TO INSTALL THEM AAAAAARRRRRHHHH. But they have enough brain to work at the store.
NOT CROSS PLATFORM !!!
What you would expect from Microsoft, lol?
Also, Linux has it's own similar solutions like Flatpak.
Or you would expect Microsoft to create a cross-platform Bluetooth library and maps? :D
@@FixingGunsInAir ı thought .net core created for cross-platform
@@llo5673 .Net Core is truly cross-platform. WPF and Microsoft Windows 10 UWP API's - not. Except, by cross-platform you mean "It will run and work on all Microsoft platforms, like Xbox and Windows"
Not a single comment for the redhair? Bug...
I just found the video bud ;) Noticed!
Never ever build a .net desktop app. Use something independend from .net. Like c++ or delphi. For server side your fine.