is this still something you consider - especialy "removing static XafTypesInfo dependencies " ?
In 2020, we made some refactorings with regard to SecuritySystem usage - we no longer recommend using SecuritySystem.Instance usage especially in non-XAF apps and made it possible for the security module to work with CurrentUserId in a common scenario (see the code in https://supportcenter.devexpress.com/ticket/details/k18352/how-to-implement-the-createdby-createdon-and-updatedby-updatedon-properties-in-a). As for the types info system, you would better describe your current top-level problem:-)
most problem now is to run multiple clients / databases within one since instance - in yóur case our webservice. multiple clients have different runtime members for example
or are there other ideas to host a singe application / web serivce / what ever - which serves differnt clients/databases - with diferent metadata / runtime members ?
@Noxe, i had so far experimented with a single instance web app that swaps connection string for different customers. Some on SQL server some on MySQL and with own runtime members. Kind of worked ok. No service though, win clients connecting directly to own databases.
Cool! Thank you for the update, especially in the light of XAF v21.1 plans to migrate the modules to .NET 5 by default (.NET Framework will be unaffected).
Breaking Change in v21.1: https://supportcenter.devexpress.com/ticket/details/t985962/core-xaf-s-blazor-and-winforms-net-core-assemblies-target-net-5 - JFYI
Guys, we want to try something we have not done before, because we were afraid of risks. We want to automate your target framework change from .NET Core 3 to .NET 5 for XAF Blazor and WinForms projects using the Project Converter.
We want to edit CSPROJ and update the SDK and some system dependencies based on the Microsoft guidance: https://docs.microsoft.com/en-us/aspnet/core/migration/31-to-50?view=aspnetcore-5.0&tabs=visual-studio#update-razor-class-libraries-rcls. This is a bit risky (this may not cover some tricky scenarios with custom 3rd party dependencies), but it is still better than manually updating 3-5-10-20+ projects in Visual Studio through the project Properties menu + you will still have to deal with 3rd party code anyway.
What do you think? Please reply with + or - (with a comment).
Cool! Thank you for the update, especially in the light of XAF v21.1 plans to migrate the modules to .NET 5 by default (.NET Framework will be unaffected).
Breaking Change in v21.1: https://supportcenter.devexpress.com/ticket/details/t985962/core-xaf-s-blazor-and-winforms-net-core-assemblies-target-net-5 - JFYI
Guys, we want to try something we have not done before, because we were afraid of risks. We want to automate your target framework change from .NET Core 3 to .NET 5 for XAF Blazor and WinForms projects using the Project Converter.
We want to edit CSPROJ and update the SDK and some system dependencies based on the Microsoft guidance: https://docs.microsoft.com/en-us/aspnet/core/migration/31-to-50?view=aspnetcore-5.0&tabs=visual-studio#update-razor-class-libraries-rcls. This is a bit risky (this may not cover some tricky scenarios with custom 3rd party dependencies), but it is still better than manually updating 3-5-10-20+ projects in Visual Studio through the project Properties menu + you will still have to deal with 3rd party code anyway.
What do you think? Please reply with + or - (with a comment).
(+) I think the risk is bigger if done manually. A verbose log of the migration would be very helpful--this is already expected from you guys as you're very good at this historically!
@kayamax , @GenesisSupzup - Guys, emailed you the latest EAP v21.1.1.21096. Thanks for your interest!
ALL: if you also want to test it before the official Beta in 2-3 weeks (active Universal subscription is required), please email me at dennis@devexpress.com (I do not regularly check this chat at this time, so email is better).
https://www.codeproject.com/Surveys/2333/Low-code-or-no-code-platforms-Do-you-use-them
or here:
https://www.codeproject.com/Messages/5798622/Re-We-moved-our-30-years-legacy-VB6-app-to-a-multi
Cool! Thank you for the update, especially in the light of XAF v21.1 plans to migrate the modules to .NET 5 by default (.NET Framework will be unaffected).
Breaking Change in v21.1: https://supportcenter.devexpress.com/ticket/details/t985962/core-xaf-s-blazor-and-winforms-net-core-assemblies-target-net-5 - JFYI
Guys, we want to try something we have not done before, because we were afraid of risks. We want to automate your target framework change from .NET Core 3 to .NET 5 for XAF Blazor and WinForms projects using the Project Converter.
We want to edit CSPROJ and update the SDK and some system dependencies based on the Microsoft guidance: https://docs.microsoft.com/en-us/aspnet/core/migration/31-to-50?view=aspnetcore-5.0&tabs=visual-studio#update-razor-class-libraries-rcls. This is a bit risky (this may not cover some tricky scenarios with custom 3rd party dependencies), but it is still better than manually updating 3-5-10-20+ projects in Visual Studio through the project Properties menu + you will still have to deal with 3rd party code anyway.
What do you think? Please reply with + or - (with a comment).(+) I think the risk is bigger if done manually. A verbose log of the migration would be very helpful--this is already expected from you guys as you're very good at this historically!
Thank you for your feedback. We are trying to implement it before the Beta as follows: a developer runs the Project Converter and receives a dialog that warns 1) if .NET 5+ SDK is not installed and it must be installed to use XAF v21.1 projects; 2) links to the Breaking Change and Microsoft documentation for more information. If a developer presses Continue, we automatically try to update XAF WinForms and Blazor project files to .NET 5 (as per the Breaking Change) and also update the old WindowsDesktop NuGet packages as per https://supportcenter.devexpress.com/ticket/details/t984618/structural-changes-to-nuget-packages-and-the-unified-component-net-core-desktop-product
Once again, I appreciate interest of XAF developers who emailed me earlier for the EAP v21.1 (pre-alpha) builds before the official Beta in 2-3 weeks.
