London Dev Meetup Rescheduled! Due to unavoidable reasons, the event has been moved to 21st May. Speakers remain the same—any changes will be communicated. Seats are limited—register here to secure your spot!
AI OnAI Off
London Dev Meetup Rescheduled! Due to unavoidable reasons, the event has been moved to 21st May. Speakers remain the same—any changes will be communicated. Seats are limited—register here to secure your spot!
hi
we are experiencing an issue where we are recieiving "unable to map the type for the property <propertyname> in <classname>" - the assembly exists, and now we are receiving the same message, but with a different property and a different class!!! Both properties are contained within the same assembly in 2 diffferent classes!
Firstly, why is the mirroring job not reporting on the first property anymore (I dont expect anyone to be able to answer that), and secondly as its not (as it shouldnt, because the correct assembly exists), why on earth is it unable to map to a property contained within that exact assembly. This kind of suggests some stability issues over the mirroring service. Please, any help would be appreciated.
Thanks.