Current filter:
                                You should refresh the page.
                                  • UPDATED on Sep 26th 2019
                                    Refer to the attached project (Samplev19.1.zip) and online documentation: .NET Core 3.0 and .NET Standard 2.0 Support.

                                    ================================================================

                                    OUTDATED CONTENT

                                    Prerequisites

                                    • XAF v19.2.1+.
                                    .NET Core 3.0 SDK and runtime Preview 8 or newer.
                                    Visual Studio 2019 v16.3 Preview 2 or newer.

                                    How to Test

                                    1. Open the attached solution in Visual Studio 2019 v16.3 Preview 2 or newer. The sample project uses Microsoft.NET.Sdk.WindowsDesktop SDK and targets netcoreapp3.0.

                                    2. Make sure that versions of installed dependencies are no less than shown in the attached screenshots. Take special note of the following NuGet packages: DevExpress.WindowsDesktop.Xaf and DevExpress.WindowsDesktop.Core. You can install them from the https://nuget.devexpress.com/early-access/api feed (learn more).

                                    3. Run the project Sample.NetCore3.Win. Remember that you are working with an early preview version that didn't go through the same rigorous testing as our official releases. Feel free to contact us in case of any difficulties.

                                    XAF modules supported in this preview are:
                                    Clipboard-File-1.png
                                     

                                    Important notes on supported modules:
                                    1. Even though the Security System modules are available, they do not currently provide the WCF-related functionality. It is unlikely that a replacement solution based on technologies like in EasyTest above will be ready by the v19.2 release time, so only Integrated Mode is available at this time. We have also cleaned the new package from the ancient security system implementations based on IPermission, ISecuritySimple, etc.
                                    2. Known issues that affect other standard XAF functionality:
                                    - https://github.com/dotnet/corefx/issues/12180 - important for the Application Model compilation and cache libraries like ModelAssembly.dll. We currently use Roslyn API in certain scenarios.
                                    - https://github.com/dotnet/corefx/issues/24829 - important for tracing options in configuration files.
                                     
                                    Unsupported modules in this preview are:
                                    Modules that will not be supported permanently due to .NET Core platform limitations or due to deprecated status:
                                    1. All ASP.NET WebForms and Mobile (Maintenance Mode) modules: DevExpress.ExpressApp.Web*, DevExpress.ExpressApp.*Mobile, DevExpress.ExpressApp.DataService.
                                    Our primary focus in 2020 will be on XAF’s Blazor UI but we will do what we can to address the needs of those reliant on our ASP.NET WebForms UI.
                                    2. DevExpress.ExpressApp.HtmlPropertyEditor.Win, DevExpress.ExpressApp.Reports.Win, DevExpress.ExpressApp.Workflow.* (related discussion)
                                     
                                    Modules temporarily unsupported in this preview and that will likely be supported in the final release:
                                    1. EasyTest modules: DevExpress.EasyTest, TestExecutor, DevExpress.ExpressApp.EasyTest.*. Instead of .NET Remoting, we are forced to use Kestrel web server with ASP.NET Core, gRPC or other options.
                                    2. EF modules: DevExpress.ExpressApp.*EF and DevExpress.Persistent.*EF.
                                    3. DevExpress.ExpressApp.ReportsV2, DevExpress.XtraWizard, DevExpress.BonusSkins, DevExpress.XtraCharts.Extensions, DevExpress.XtraReports.Extensions and some other libraries that we forgot for this early-access NuGet feed or which are not yet ready. If you are missing any library, please specify its name not to miss anything.

                                    See Also
                                    .Net Core 3 DevExpress WinForms Demos
                                    .Net Core 3 WPF Demos

                                Show all comments
                                • Martin Praxmarer - DevExpress MVP 03.20.2019

                                  btw - i think it makes sense that you update your answer above - one has to use at least preview3 - i had preview1 which did not work.

                                  with preview3 everything is ok

                                • Dennis (DevExpress) 03.20.2019

                                  Yeah, already did that:-)

                                • Martin Praxmarer - DevExpress MVP 03.20.2019

                                  if this envolves it would be interessting to get some performance comparisons - if there are any gains specific for XAF when runnung under core 3.0 - i am still not sure if there is still an ngen for dotnetcore

                                • Dennis (DevExpress) 03.20.2019

                                  This is a very good question, Noxe, because this is one of the migration motivations for .NET users.
                                  Hopefully, we will answer it with numbers when we and Microsoft finish all the .NET Core 3.0-related work and optimizations, since it is too early to judge at this stage.

                                • Achmad Mulyadi 05.22.2019

                                  Wow, too good to be true. But hell yeah it's happening, .NET Core 3 here I come.

                                • Manuel Grundner [DevExpress MVP] 08.20.2019

                                  @Noxe: i am still not sure if there is still an ngen for dotnetcore
                                  As far as I know they work on crossgen https://github.com/dotnet/coreclr/blob/master/Documentation/building/crossgen.md as well as ReadyToRun https://devblogs.microsoft.com/dotnet/announcing-net-core-3-0-preview-6/

                                • Martin Praxmarer - DevExpress MVP 08.20.2019

                                  Thx Manuel - yes i am following all those channels and reading about various staff which is coming... i think i am playing around the next weeks with core 3

                                • Manuel Grundner [DevExpress MVP] 08.20.2019

                                  @Martin I did some testing with PublishReadyToRun, PublishSingleFile, SelfContained and PublishTrimmed:

                                  PublishReadyToRun seams to work. Application startup is a lot faster (did check on a surface laptop 2 on battery to be sure) startup time is cut in half. (with win-x86 TFM) Application also feels more responsive.

                                  PublishSingleFile works as well produces a single executable with 237MB
                                  SelfContained works as well. When combined with SelfContained it produces 480MB
                                  PublishTrimmed does still work, but seams to make no difference.

                                  That leave me with one question for the team: is the current strategy packing everything into those 2 nuget packages (DevExpress.WindowsDesktop.Core and DevExpress.WindowsDesktop.Xaf) going to stay? Or is this just for the EAP?

                                • Martin Praxmarer - DevExpress MVP 08.20.2019

                                  impressive results manuel! cant wait to try how our application performs with core 3.

                                  "is the current strategy packing everything into those 2 nuget packages " - had the same in my mind today as i did a short test...

                                • Dennis (DevExpress) 08.20.2019

                                  That leave me with one question for the team: is the current strategy packing everything into those 2 nuget packages (DevExpress.WindowsDesktop.Core and DevExpress.WindowsDesktop.Xaf) going to stay? Or is this just for the EAP?

                                  We used this schema for almost a year in our components. Would you please elaborate a bit more on your concerns, scenarios and expected results?

                                • Martin Praxmarer - DevExpress MVP 08.20.2019

                                  What about if i only need a minimal set of references for example for our utilities library - which we sharee beteen win and web? i think i do not want to add DevExpress.WindowsDesktop.Core to this library ? thought there would be some smaller packages?

                                • Martin Praxmarer - DevExpress MVP 08.20.2019

                                  Hi Dennis,

                                  i see that DevExpress.ExpressApp.ReportsV2.Win is missing in the packages - is this because of the early EAP? also missing XtraReports.Extensions or XtraScheduler.Reporting / Docs?

                                • Alex Gn (DevExpress) 08.21.2019

                                  Hello Martin,
                                  We do not have these modules for .NET Core at this moment. We plan to add them in the nearest release.

                                • Martin Praxmarer - DevExpress MVP 08.21.2019

                                  thx Alex - looking forward to the release :) Had also Spreadsheet and Wizards missing - but so far the application is running!

                                • Martin Praxmarer - DevExpress MVP 08.21.2019

                                  @manuel - got our application running - cannot really say it is much faster - detailviews even load slower in my first tests...

                                  also - seems that report scripting is not available/supported - which is a showstopper currently for us

                                • Dennis (DevExpress) 08.21.2019

                                  Thank you for your feedback, Noxe. I will also share your related ticket link here for other XAF users: Reporting - Scripting on .NET Core.

                                • Martin Praxmarer - DevExpress MVP 08.21.2019

                                  Thx man!

                                • Joerg Egger 08.21.2019

                                  Hi Dennis!

                                  Which modules are curently not supported in .NET Core?

                                • Dennis (DevExpress) 08.23.2019

                                  @Martin: I've created a separate ticket on your behalf (T809021: How to share code between WinForms, WebForms and other .NET Core 3.0 Desktop and .NET Framework libraries). I also want to share a link to your recent ticket too: NetCore3.0 Application and NetStandard2.0 Modules - both discussions will be very interesting for the XAF/XPO community.
                                   
                                  @Joerg:

                                  XAF modules supported in this preview are:
                                  Clipboard-File-1.png
                                   

                                  Important notes on supported modules:
                                  1. Even though the Security System modules are available, they do not currently provide the WCF-related functionality. It is unlikely that a replacement solution based on technologies like in EasyTest above will be ready by the v19.2 release time, so only Integrated Mode is available at this time. We have also cleaned the new package from the ancient security system implementations based on IPermission, ISecuritySimple, etc.
                                  2. Known issues that affect other standard XAF functionality:
                                  - https://github.com/dotnet/corefx/issues/12180 - important for the Application Model compilation and cache libraries like ModelAssembly.dll. We currently use Roslyn API in certain scenarios.
                                  - https://github.com/dotnet/corefx/issues/24829 - important for tracing options in configuration files.
                                   
                                  Unsupported modules in this preview are:
                                  Modules that will not be supported permanently due to .NET Core platform limitations or due to deprecated status:
                                  1. All ASP.NET WebForms and Mobile (Maintenance Mode) modules: DevExpress.ExpressApp.Web*, DevExpress.ExpressApp.*Mobile, DevExpress.ExpressApp.DataService.
                                  Our primary focus in 2020 will be on XAF’s Blazor UI but we will do what we can to address the needs of those reliant on our ASP.NET WebForms UI.
                                  2. DevExpress.ExpressApp.HtmlPropertyEditor.Win, DevExpress.ExpressApp.Reports.Win, DevExpress.ExpressApp.Workflow.* (related discussion)
                                   
                                  Modules temporarily unsupported in this preview and that will likely be supported in the final release:
                                  1. EasyTest modules: DevExpress.EasyTest, TestExecutor, DevExpress.ExpressApp.EasyTest.*. Instead of .NET Remoting, we are forced to use Kestrel web server with ASP.NET Core, gRPC or other options.
                                  2. EF modules: DevExpress.ExpressApp.*EF and DevExpress.Persistent.*EF.
                                  3. DevExpress.ExpressApp.ReportsV2, DevExpress.XtraWizard, DevExpress.BonusSkins, DevExpress.XtraCharts.Extensions, DevExpress.XtraReports.Extensions and some other libraries that we forgot for this early-access NuGet feed or which are not yet ready. If you are missing any library, please specify its name not to miss anything.
                                • Manuel Grundner [DevExpress MVP] 08.25.2019

                                  @Dennis: I know that we can use a custom installer to reduce application size, but isn't that wasteful? For example on build servers restoring almost 200MB is something that I rather would avoid. Providing a metapackage is absolutely fine for me (the asp.net team does the same) but they keep their packages small. Previous you provided packages for all assemblies in separate packages, so why now change the strategy with dotnet core? Besides application size, I think it's harder to share modules with the community (like eXpand).

                                • Dennis (DevExpress) 08.26.2019

                                  @Manuel: Thank you for your feedback. I've commented on this in the separate How to share code between WinForms, WebForms and other .NET Core 3.0 Desktop and .NET Framework libraries ticket devoted to this topic.

                                • Rene Schlei 08.27.2019

                                  Hi Dennis,
                                  i see that DevExpress.XtraScheduler.v19.2.Extensions dll is missing in the packages.
                                  We need this one for the DevExpress.XtraScheduler.UI.ResourcesTree.

                                • Dennis (DevExpress) 08.27.2019

                                  @Rene: I've created a separate ticket on your behalf (T809883: DevExpress.XtraScheduler.v19.2.Extensions dll is missing in the .NET Core 3.0 Desktop packages) and forwarded it to the XtraScheduler team for a follow up. Thank you for testing!

                                0 Solutions

                                Creation Date Importance Sort by