Old XAFers can remember this old sporadic issue caused by a Visual Studio bug that could not be fixed on the IDE side for years (learn more...). We were frustrated by it no less than our users, and this April (15.1.11+, 15.2.8+, 16.1+) we finally found a way to bypass this nasty behavior of an internal IDE assemblies cache on our side by changing the process of loading assemblies at design time. This was quite a risky change, but so far our testing of many projects under various circumstances went well. We also have not received user reports on the original problem or other side effects with our designers since then (more than 8 months).
That said, I wanted to explicitly clarify with the XAF community whether it is really gone after our changes or not. Please leave a comment below on whether you have seen this error with the latest XAF versions OR you already cannot recall when it occurred last time. If this still bothers you, I would kindly ask you submit a ticket using the Support Center and attach a project where this behavior is stably reproducible, exactly as this kind guy did in the past.
My team and I look forward to hearing from you!
My team and I look forward to hearing from you!
Good to know Dennis - we where using xpand modeleditor plugin since years now to bypass this one. Seems it is time to use VS integrated one again :)
ReplyDeletethx
Noxe
I didn't see it for half a year or so - that would make sense!
ReplyDeleteKrzysztof Krzysztof
Agreed - haven't seen it in quite some time.
ReplyDeleteWe also use the eXpand editor as the integrated one was unusable due to this error.
ReplyDeleteWorks perfect now Dennis - thank you Guys!!
ReplyDeleteHere the same - very good!
ReplyDelete+1!
ReplyDeleteThanks for your answers, Guys!
ReplyDeleteWorks fine here.
ReplyDeleteI have seen the message a fews days ago, but this was because of a duplicate id in the model.
Sometimes I still get the error in 16.1.4.
ReplyDeleteMost of the time, I compile my base solution first. After that I copy the base assemblies to my main application using these as references. It ocurres when opening the application model in my main application
f.e. Dictionary already contains ClassInfo 'MainModel.Common.BOModel.BoBase'. Possible reason: the assembly [MainModel.Common, Version=1.10.0.4, Culture=neutral, PublicKeyToken=null] has been loaded twice.
@Arjan: Would you please submit a ticket using the Support Center and attach a project where this behavior is reproducible (do not forget to specify the exact VS version)?
Delete