Null reference exception in Xpand.Extensions.XAF.Xpo.ObjectSpaceExtensions, ln. 144 #1088
Labels
Milestone
Comments
|
eXpressAppFramework log extract: |
|
provide me a sample please it is about the DataStoreProxy that is used it looks, what's the reason u use that proxy btw |
|
Found this lines of code added in February 2021:
Not sure why this has been added, anyway a hint where I can do some further research. Also working on a sample |
|
that shot says does not say much just points to IsSupported method for this DataStore, I cannot even tell if the DataStoreProxy is something u do not even use |
|
Creating a sample application throwing the same error is not that simple, I am working on it. Do you have an idea what can be checked in the erroneous application in parallel? |
|
no really looks like it depends on the configuration u have and the way u use the proxy, such combinations are endless and pointless to spent my resources pursuing what can go wrong |
|
Sample has been created, you should shortly get an email with invitation to the repo |
|
The pre-release 4.242.5.0 in the Reactive.XAF To minimize version conflicts we recommend that you use the Xpand.XAF.Core.All, Xpand.XAF.Win.All, Xpand.XAF.Web.All packages. Doing so, all packages will be at your disposal and .NET will add a dependecy only to those packages that you actually use and not to all (see the Modules installation-registrations youtube video). Released packages:No packages released.Please update the related Nuget packages and test if issues is addressed. These are nightly nuget packages available only from our NugetServer. If you do not use these packages directly but through a module of the main eXpandFramework project, please wait for the bot to notify you again when integration is finished or update the related packages manually. Thanks a lot for your contribution. |
|
eXpand.lab release 24.2.500.0 includes commit that relate to this task: Please test if it addresses the problem. If you use nuget add our LAB NugetServer as a nuget package source in VS. To minimize version conflicts we recommend that you switch to PackageReference format and use only the eXpandAgnostic, eXpandWin, eXpandWeb packages. Doing so, all packages will be at your disposal and .NET will add a dependecy only to those packages that you actually use and not to all (see the Modules installation-registrations youtube video). Thanks a lot for your contribution. |
|
I have upgraded the sample solution's Nugets to reference DevExpress 24.2.5 and eXpand 24.2.501, but the exception is still being thrown. Changed code has been pushed to the sample repo.
|
|
u used the nuget servers and not the lab get-xpandpackages -Source lab -PackageType XAFModules
Id Version Source
-- ------- ------
Xpand.XAF.Modules.AutoCommit 4.242.6.1 Lab
Xpand.XAF.Modules.Blazor 4.242.6.1 Lab
Xpand.XAF.Modules.BulkObjectUpdate 4.242.6.1 Lab
Xpand.XAF.Modules.CloneMemberValue 4.242.6.1 Lab
Xpand.XAF.Modules.CloneModelView 4.242.6.1 Lab
Xpand.XAF.Modules.Email 4.242.6.1 Lab
Xpand.XAF.Modules.GridListEditor 4.242.6.1 Lab
Xpand.XAF.Modules.HideToolBar 4.242.6.1 Lab
Xpand.XAF.Modules.JobScheduler.Hangfire 4.242.6.1 Lab
Xpand.XAF.Modules.JobScheduler.Notification 4.242.6.1 Lab
Xpand.XAF.Modules.MasterDetail 4.242.6.1 Lab |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
𝗗𝗲𝘀𝗰𝗿𝗶𝗯𝗲 𝘁𝗵𝗲 𝗯𝘂𝗴
After upgrading eXpand to version 24.2.302, our WinForms application throws a null reference exception in Xpand.Extensions.XAF.Xpo.ObjectSpaceExtensions, ln. 144 on startup. After confirming the error message the startup process continues, the null reference exception is anyway thrown multiple times until the application is started up, it seems anytime when an objectspace is to be created.
According to the stack trace, the problem seems to be somehow related with the SequenceGenerator module.
𝗦𝗰𝗿𝗲𝗲𝗻𝘀𝗵𝗼𝘁𝘀
The text was updated successfully, but these errors were encountered: