-
-
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
Visual Studio Model Editor not working due to ModelMapper module #488
Comments
do u have any suggestions? why this message is not clear?
probably an additional action could resolve this case, I will update u again.
VS insanity is really costly I thought it might be possible to avoid it, I might reconsider this desicion. |
Sometimes the VS Model Editor complains about being unable to load "System.Interactive, Version=3.2.0.0" at Xpand.XAF.Modules.ModelMapper.Services.ModelExtendingService.AddExtenders(ModelInterfaceExtenders extenders) It was not clear for me, that nothing is wrong with my setup and it is just not possible to use the VS Model Editor anymore. I'm not sure whether it is possible to check if the VS Model Editor is running and throw an InvalidOperationException("Use XpandModelEditor!!!") in this case?!
Great!
If you find an alternative for Merge User Model and also display a nice error message when trying to use the default VS ModelEditor, using the XpandModelEditor is absolutely fine for me! |
both the action and the message is possible, I still not sure where to spent resources though.
I am interested in this comment, can u elab a bit more. What makes u say that a static contructor is not called? |
Right now in my development setup, a SuperUser customizes ListViews/DetailViews and sends me the Model.User.xafml to merge in the changes into our different modules xafmls. Of course it is also possible to merge changes with a texteditor, but this is really an annoying job. Therefore I really would like to use the 'Merge User Model...' action again.
I guess you are right: The static constructor should be called always. Probably I attached the Debugger to late. Nevertheless the various static Assembly fields (_xafWinAssembly, ...) are null and therefore the error is thrown. |
You can try the ModelDifference module for now until I update u it can merge differences at runtime in seperate layers and then u can manually copy them to your model.user.xafml |
actually the real problem is that VS maybe not able to handle so many resources introduced from the mapping, anyway I am starting a trial on the MMM and I will update u asap |
if i remember well u r not in GAC right? |
Sounds like a sensible workaround
Latest DevExpress version is installed in the GAC on my development machine, eXpand is not installed. On our build server DevExpress is not installed in the GAC, but this shouldn't matter. |
we might need to set an eviroment variable to help vs locate the assemblies if not in gac and not in path |
But this is not the problem on my side. The DX assemblies are in the GAC. Or are you talking about Xpand assemblies? |
sorry I am used to adding thoughts/notes on the ticket itself not to lose them |
The DevExpress.XAF repository includes commits that relate to this task: 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 the Xpand.XAF.Modules 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. |
Thank you! Unfortunately there still seems to be a bug: If I open Model.xafml from my agnostic module, everything is fine. But if I try to open Model.xafml from my winforms module, the
|
i tested against XVideoRental however there are changes in the eXpand modules yet to be published. u will get notified again |
eXpand.lab release 19.1.502.2 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. Thanks a lot for your contribution. |
the above release at least in my tests in XVIdeoRental works fine |
The DevExpress.XAF repository includes commits that relate to this task: 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 the Xpand.XAF.Modules 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. |
I'm still getting the |
According to stack overflow, VS designers copy dlls to the ProjectAssemblies folder by default. Therefore it should be save to ignore duplicates in this folder |
yes there is a different initialization for the double thats why I added that constrain.
unfortunately i cannot repro it on my side what the locations of ModelMapper? check the log |
2 types are different if they come for different assembly even if versions, token match |
I already posted the log for the old version. Locations are the same for the new version
The winforms designer cache is a standard feature of VS, but I think it is not documented very well (and it is the cause of some annoying bugs...) Unfortunately I still cannot use the ModelEditor, because I'm now back to the |
did u close this by mistake? No I do not use the GAC, #494 not yet published contain related fixes, subscribe there to get notifiex, also please update your modelmapper to the latest or wait for update the eXpandFramework all together I will integrate it soon. |
|
eXpand.lab release 19.1.502.7 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. Thanks a lot for your contribution. |
eXpand.lab release 19.1.502.8 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. Thanks a lot for your contribution. |
Thank you!!! btw: According to the debugger, only the ModelMapper.dll from the ProjectAssemblies path is loaded... |
It took me quite a while to realize that the Visual Studio Model Editor is not working anymore due to issues in the ModelMapper module. Do you have any plans to fix these issues? At least a better error message should be shown.
I also noticed, that the 'Merge User Model...' command is not working anymore since I upgraded from 19.1.3 to 19.1.5. Is this caused by the same issue? Is there any alternative in the XpandModelEditor?
The text was updated successfully, but these errors were encountered: