Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    noxe
    @noxe
    {
    "runtimeOptions": {
    "tfm": "net6.0",
    "frameworks": [
    {
    "name": "Microsoft.WindowsDesktop.App",
    "version": "6.0.0-rc.1.21451.3"
    },
    {
    "name": "Microsoft.AspNetCore.App",
    "version": "6.0.0-rc.1.21452.15"
    }
    ]
    }
    }
    Dennis
    @dengara_gitlab
    @noxe , @kashiash - we are looking to support VS2022 after the official Microsoft release in early December or 2022. In the meantime, you can test this old-good solution that I described back to early .NET 5 days. I elaborated more on this in https://gitter.im/XAF-Community/community?at=5fca29a627085821da8936f3 (note that the "version" parameter changes and you will have to update it).
    noxe
    @noxe
    thx Dennis - i think we should differentiate VS2022 - and .NET6 ?
    Dennis
    @dengara_gitlab
    yes, correct. Visual Studio 2022 support will likely be added in a 22.1.4+ minor, because the Microsoft.VisualStudio.Sdk (17.x versions) and the Microsoft.VSSDK.BuildTools (17.x versions) packages were rely on in the Model Editor for design-time support are in a very early prerelease state and it makes sense to use them only after they are released in November 2021 (after Microsoft's official release of Visual Studio 2022).
    noxe
    @noxe
    thx Dennis - but 22.1.4+ means June 2022? 🤔
    Dennis
    @dengara_gitlab
    Sorry, 21.2.4 of course, around November/December
    noxe
    @noxe
    omg - thx - sounds much better 😁 we are internaly already running on net6 - looks pretty good so far
    Dennis
    @dengara_gitlab
    Guys, using XAF v21.2 previews already? If so, looking for the "winners" who have the most/least of 5 error types we listed in https://docs.devexpress.com/eXpressAppFramework/403389/debugging-testing-and-error-handling/code-diagnostics?v=21.2
    @noxe ? ;-)
    noxe
    @noxe
    image.png
    lol ->
    noxe
    @noxe
    i see many false positives here Dennis - should i create a ticket?
    noxe
    @noxe
    done :) https://supportcenter.devexpress.com/ticket/details/t1035172
    Dennis
    @dengara_gitlab
    Thank you for your feedback, Noxe! 652 - nice 🙂
    noxe
    @noxe
    🙈
    noxe
    @noxe
    is there an aprox. date for the next beta?
    Isa Tahiri
    @isatahiri
    Next beta seems to be next week according to the last post. See in comments
    noxe
    @noxe
    👌
    Dennis
    @dengara_gitlab
    October 13+
    noxe
    @noxe
    nice timing btw ;) since net6.0 rc2 is available today 😜
    noxe
    @noxe
    https://tenor.com/view/f5-refresh-reload-gif-15071315
    noxe
    @noxe
    21.2.2 beta available now :)
    noxe
    @noxe
    i see major refactoring about XafTypesInfo.Instance - any news on this Dennis? :)
    noxe
    @noxe
    living on the bleeding edge ;)
    image.png
    Dennis
    @dengara_gitlab
    @noxe - just testing you, both "Passed" :-)
    noxe
    @noxe
    🤣👌
    Gustavo Marzioni
    @vimarx
    hi @noxe, I saw your post about elsa-core, I would really like to hear your opinion about it because I'm currently seeking a workflow integration.
    noxe
    @noxe
    hi gustavo - as for now - elsa is really great. i looked at https://workflowengine.io/ and https://elsa-workflows.github.io/elsa-core/ - and i decided to go with elsa. it works really great - is extremly customizable - and provides everything we need so far.
    Gustavo Marzioni
    @vimarx
    thanks! and are you using hangfire ?
    noxe
    @noxe
    yes - elsa + hangfire in combination. hangfire for background jobs - and now elsa with hangfire as dispatcher
    noxe
    @noxe
    @dengara_gitlab - can you share some details about the XafTypesInfo.Instance thing?
    Dennis
    @dengara_gitlab
    @noxe , you mean our recent code changes? If so, we are not yet ready - once we do, we will certainly add it to What's New or a blog/SM announce.
    noxe
    @noxe
    yes - just want to get an idea about what these changes are
    Dennis
    @dengara_gitlab
    We are just removing dependecy on the singleton, it's half way done and a lot things are to change (type converters, various criteria, model, reflection helpers).
    kashiash
    @kashiash
    v21.2.3 - Released on 01 Nov 2021
    noxe
    @noxe
    great to hear - thx Dennis!
    Dennis
    @dengara_gitlab
    @noxe , would you please share your experience with a customer (Jacob) from https://supportcenter.devexpress.com/ticket/details/t410727/edit-model-saved-in-shared-model-difference ? I remember you had a role-based layer along with the embedded Model Editor in your WinForms app. Thanks in advance.
    noxe
    @noxe
    sure - i take a look
    Evgeniy Meyke
    @emeyke
    @noxe, whats your balzor path in terms of model editing support?
    noxe
    @noxe
    hey evgeniy - how are you :) - i made some improvements last week - so in our winforms admin application we can now open and edit blazor models :)
    Evgeniy Meyke
    @emeyke
    Thats good to know as this is a key one for me! Happy running @noxe - enjoying your instagram!
    noxe
    @noxe
    thanks man! season 2021 is over now :)
    Dennis
    @dengara_gitlab

    Guys, please help me with NuGet Hotfixes (thank you to those who already replied me via email).

    If you are unsure about our plans, please see my post: https://community.devexpress.com/blogs/news/archive/2021/09/28/nuget-stability-and-authentication-enhancements-hot-fixes-portable-pdb-support-for-windows-and-linux-net-core-desktop-installer-deprecation.aspx

    Based on our current understanding of customer needs, we do not plan to store hotfixes indefinitely, because hotfixes are not recommended for production and are temporarily used (we already have a ton of disclaimers for this).

    We plan to store hot fixes either within a major (and remove them later after a new major is issued) or store just 10-15 the latest hotfixes within the major (and remove them after the limit).

    My concern that NuGet.org does not remove hotfixes at all, and in theory, there may be a customer who leaves his CI on a hot fix and this CI will be broken when a new major or removal limit is reached. For me, this is not a bad thing (because a more stable version is available and it is not good to stay on unstable hotfixes long), but some may disagree.

    What do you think of our plans to remove hotfixes from NuGet after some time?

    2 replies
    noxe
    @noxe
    seems like there is not any traffic anymore here...
    Dennis
    @dengara_gitlab
    November - hot times everywhere. Based on support traffic everyone has just decided to finish their projects 😃
    noxe
    @noxe
    very true - we are also busy with our release for december ;)
    Dennis
    @dengara_gitlab
    @noxe Not sure if you still follow it, but discussions regularly happen on https://www.facebook.com/groups/xafxpoxamarin
    noxe
    @noxe
    of course - follow everywhere ;)
    kashiash
    @kashiash
    @dengara_gitlab when you will release 21.2.4 with VS 2022 support ?
    Dennis
    @dengara_gitlab
    In 1-2 weeks or so