I was hoping that you will describe the steps that you did to trigger the Visual Studio crash in full details.
Suggestion that Alexander has posted is to resolve a potential issue with application of code generation templates. These templates are executed when you try to save your RLINQ model and if this is the last action you do before your Visual Studio crashes there is strong indication that there is a problem with code generation.
disable the warning for execution of T4 templates from Tools -> Options -> Text Templating - Show Security Message
by setting the value to False
Another possible cause is if you have huge number of types mapped in your RLINQ model.
Is it the case? How many types do you have in your model (approximate number is totally acceptable)?
I had asked you about your Visual Studio extensions because they may associate with certain file types or react to new files or change of content and cause the crash.
My last suggestion is to enable logging for the Visual Studio instance and reproduce the crash. After that please send us the log or post it's content for analysis. For more information please check this article
how to enable the ActivityLog
of Visual Studio. The workflow can be used in Visual Studio 2013 too.
OpenAccess ORM is now Telerik Data Access
. For more information on the new names, please, check out the Telerik Product Map