In our test environment, we have recreated the exact set-up you described. Unfortunately even then we were unable to reproduce the behavior you described. Are there any other modification in the project or in the environment set-up you think could be relevant? Could you please also attach the project file (.csproj
) of the project that contains your Telerik Data Access
Let me explain in a bit more detail what is happening - the Attributes Editor
use reflection to read the metadata of the referenced assemblies and extract the attribute types within them. From the description you provided it appears that this reflection process is interrupted in an unexpected manner causing the issue.
Then using the reflected attribute types information and the user's input, the Attributes Editor
actually modifies the xml located in the .rlinq
file. Once this is done, the Telerik Data Access
code generation kicks in and generates the actual domain classes.
Based on that I could suggest you the following workaround:
1. Open the .rlinq
file as text.
2. Notice that there is <Types>
tag. In this tag you will notice that there are <DomainType>
tags. In each of these there are <Property>
3. Lets suppose you have an Author
class that has a Name
property and you would like to apply the IgnoreDataMemberAttribute
attribute from the System.Runtime.Serialization
namespace. In order to do that please locate the corresponding <Property>
tag as explained above. Once you located it please add as a child tag in it the following code:
Please note that you need fresh values for the guids marked in red.
In order to make the process more visible I have attached two identical .rlinq
files. One of them has a property decoreted with an attribute where as the other does not have one. You could use a tool to complere those files as text and see the exact differences I described above.
Additionally, in order to get to the bottom of this issue and identify its cause, you could use Fusion Logs
(please see this blog post
as an example) to exactly pin-point which assembly has failed to load on your side.
I hope this helps. Do not hesitate to get back to us with any further questions.
Check out the latest announcement
about Telerik Data Access vNext as a powerful framework
able to solve core development problems.