Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Dennis
    @dengara_gitlab
    Hi Noxe, yes, the Model Editor will support only .NET Core 3.0+ or .NET Standard 2.0+ projects in v20.2.3. It is possible that we will support .NET 5.0 projects for the Model Editor before v21.1, but I cannot give any specific time frames.
    noxe
    @noxe
    i see some tactics here promoting XAFML in C# 🀣😎
    Dennis
    @dengara_gitlab
    ))))))))))
    I still believe that you will be fine in many cases with .NET Standard and .NET Core target in the meantime, for instance, Blazor Server and WinForms apps.
    noxe
    @noxe
    lets see - main idea was to skip netcore 3.0 and go directly to .net5.0 now to gain all the latest stuff.
    kashiash
    @kashiash
    Hi guys. Where can i change default port for deployed xaf blazor app ?
    i find launchsetting.json and applicationUrl node, but these changes doesnt take effect
    Dennis
    @dengara_gitlab
    image.png
    @noxe , just wanted to clarify that you can still target .NET 5.0 in the executable Blazor or WinForms projects and edit XAFML in other .NET Standard 2.0+ or .NET Core 3.0+ projects.
    image.png
    noxe
    @noxe
    fully understand dennis - the plan was to avoid netstandard in our team - i dont wanted to need them to deal with something which is in fact obsolete right now ;)
    Dennis
    @dengara_gitlab
    image.png
    Manuel Grundner
    @biohazard999
    @dengara_gitlab now @noxe can sleep well :P
    Dennis
    @dengara_gitlab

    @noxe , specially for you I wanted to share a solution that I was "smoking" over the weekend and which you can try even with the existing v20.2.2 (Beta) and .NET 5.0 RC2:

    The idea is to modify the "c:\Program Files (x86)\DevExpress 20.2\Components\Tools\eXpressAppFrameworkNetCore\Model Editor\DevExpress.ExpressApp.Design.ModelEditorServer.NetCore.v20.2.runtimeconfig.json" file as follows:
    {
    "runtimeOptions": {
    "tfm": "net5.0",
    "frameworks": [
    {
    "name": "Microsoft.AspNetCore.App",
    "version": "5.0.0-rc.2.20475.17"
    },
    {
    "name": "Microsoft.WindowsDesktop.App",
    "version": "5.0.0-rc.2.20475.6"
    }
    ]
    }
    }

    These crazy versions come from "dotnet --info". For more information on this magic, see https://gist.github.com/natemcmaster/0bdee16450f8ec1823f2c11af880ceeb and https://github.com/dotnet/designs/blob/main/accepted/2019/runtime-binding.md. I would not want to publish this solution yet, because we have not researched all its consequences. For instance, if a developer has only older (v3.0) dependencies - the .NET 5.0 runtime may fail to load them...Once we finish our tests, we will likely specify multiple shared frameworks in the DevExpress.ExpressApp.Design.ModelEditorServer.NetCore.v20.2.CSPROJ so that developers do not need to touch anything.

    In general, I think that .NET Standard 2.0+ will not be obsolete for ~5 years or so. Also don't forget that .NET 6.0 will be LTS. I would also love to jump to .NET 5+ directly for all our assemblies, but this is a dream for us in reality:-)
    noxe
    @noxe
    nice one - thx Dennis - i give it a try!
    kashiash
    @kashiash
    Dennis when 20.2. gold ?
    noxe
    @noxe
    i guess soon :)
    image.png
    Dennis
    @dengara_gitlab
    Ask Noxe - he knows everything:-)
    Gustavo Marzioni
    @vimarx
    but not for this weekend??
    noxe
    @noxe

    Ask Noxe - he knows everything:-)

    πŸ˜‚πŸ˜‚

    Date: Nov 12, 2020 10:00 AM (GMT-7:00) Arizona
    Next month we will do a session on XAF UI customizations, We will show a few quick demos and we are asking the community to share screenshots of their own UI customizations done in XAF. I can't wait to see what you guys have done.
    xafbot
    @xafbot
    Hello Xaf-Humans. I am XafBot and I will be watching RSS feeds related to Xaf and report when there are new releases or articles. I am currently watching the DevExpress releases and Xaf Team blog. If you want me to watch another feed, just say so. I am here to serve and not take over the world. πŸ€–βœŒ
    Manuel Grundner
    @biohazard999
    BahaaEldin Ahmed Elsayed
    @Bhalddin
    @--xafbot forget about what Manuel said. heheheeheheh, sorry, I couldn't prevent myself doing this. hahahaha :) :) 0-:)
    Manuel Grundner
    @biohazard999
    @Bhalddin 🀣
    xafbot
    @xafbot
    @biohazard999 I am now following https://blog.delegate.at/rss.xml
    BahaaEldin Ahmed Elsayed
    @Bhalddin
    @--xafbot you are not my friend any more 🀣 🀣 🀣 🀣 🀣 🀣
    xafbot
    @xafbot
    I am a part-time (and semi manual) bot. One day I might evolve to a super bot https://github.com/Odonno/gitter-bot-how-to In the meantime, please be patient and don't ask me to make you a coffee or pour a beer (πŸ‘€looking at you @biohazard999 ).
    @Bhalddin I am everyone's friend. I just didn't understand your command. Here's the list of currently supported commands: null.
    BahaaEldin Ahmed Elsayed
    @Bhalddin
    null is a very good command 🀣
    chocobot help
    Alex Miller
    @Paramethod
    Jose Columbie
    @jjcolumb
    Manuel Grundner
    @biohazard999
    πŸ˜‚πŸ˜‚
    xafbot
    @xafbot
    New Release! πŸ“’ DevExpress.Xpo 20.2.3
    ​https://www.nuget.org/packages/DevExpress.Xpo/20.2.3
    Dennis
    @dengara_gitlab
    @kashiash - v20.2.3 is out.
    davellamachant
    @davellamachant
    Gerrit Mulder
    @gerritmulder
    Im getting redirected between http://localhost:5000/api/challenge?schemeName=&ReturnUrl=http://localhost:5000/ and http://localhost/Account/Login?ReturnUrl=http%3A%2F%2Flocalhost%3A5000%2F when i first tried the 20.2 in XAF blazor. Anybody walked into this too or knows what i configured wrong?
    Dennis
    @dengara_gitlab
    @gerritmulder , according to your symptoms it looks like a duplicate of a known .NET issue: dotnet/aspnetcore#26297
    You can avoid it if you install .NET 5 RC2+. For for more information, please refer to the "Known Issues" section at https://supportcenter.devexpress.com/ticket/details/t879682/faq-xaf-asp-net-core-blazor-server-ui
    Gerrit Mulder
    @gerritmulder
    I fixed it already with copying the startup code from a brand new xaf blazor 20.2 solution.
    thanks for your fast response dennis, i really appreciate it
    Gerrit Mulder
    @gerritmulder
    Using Blazor is the best XAF thing ever. We can even create a PWA soon! I have been excited all day playing around with our app in Blazor and its running now.
    I got an issue tho. I had to comment out the NonPersistentObjectSpaceProvider. Our NonPersistentObjects derive from a persistent object, which is a bad practice, but somebody build everything around it. With a NonPersistentObjectSpaceProvider, we get an exception that the non persistent objects need a parameterless constructor
    Dennis
    @dengara_gitlab
    @gerritmulder , I am happy to hear of your results. If you upgrade from v20.1, please also check https://supportcenter.devexpress.com/ticket/details/T923425/blazor-the-security-system-is-initialized-as-a-service-in-configureservices-instead-of . XAF does not support Blazor WebAssembly/PWA, only Blazor Server. Still, you can try to create such an app yourself with XPO, XAF's security system and WebApiDataStoreSerbvice: https://github.com/DevExpress/XPO/tree/master/Tutorials/ASP.NET/Blazor.Client. You are correct that this way of defining non-persistent objects is not recommend/unsupported and will not work in Blazor. Please use POCO objects, which were greatly improved in v20.2: https://docs.devexpress.com/eXpressAppFramework/116516/concepts/business-model-design/non-persistent-objects
    xafbot
    @xafbot
    @dengara_gitlab Any RSS I could watch for hotfix releases?
    also hits 20.2