-
-
Notifications
You must be signed in to change notification settings - Fork 114
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SequenceGenerator starting with version 4.231.6.1 (lab) prevents Blazor/Win Model Editor from loading #1030
Comments
as always perfect, thanks! |
eXpand.lab release 23.1.601.3 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. |
Hi, starting with version 4.231.6.1 it looks like that loading SequenceGenerator in Module-Project
RequiredModuleTypes.Add(typeof(Xpand.XAF.Modules.SequenceGenerator.SequenceGeneratorModule));
prevents DevExpress Model Editor in Visual Studio from loading (not eXpand Model Editor).
Model Editor in Blazor project doesn't work
Model Editor in Win project doesn't work
Model Editor in Module project is working
If you downgrade nuget packages to 4.231.6 it is working again.
Please note: to test you have to build the solution. After failed loading you can downgrade nuget, rebuild solution and then restart visual studio. Now you can open Model Editor again and it should work.
DXApplication3.zip
I use lab because there is a fix relating to SequenceGenerator/ObjectSpace observation.
The text was updated successfully, but these errors were encountered: