Extend the LinqService
See original GitHub issueHi,
I would like to extend the methods provided of the LinqService. Is this somehow possible?
using(var db = new MyServiceContext(binding, endpointAddress )){
db.CallMyMethod();
}
If I understand I have to get the underlying channel, but this one does not include my Interface. I also don’t want to recreate the given LinqService class.
Issue Analytics
- State:
- Created 4 years ago
- Comments:54 (54 by maintainers)
Top Results From Across the Web
How can I extend a LINQ-to-SQL class without having to ...
I need to extend linq-to-sql classes by own parameters and dont want to touch any generated classes. Any better suggestes are welcome.
Read more >Enterprise Mobile Managment FAQs - LINQ Services
Get answers to our most frequently asked questions. Don't see what you're looking for? Contact us with your question and we'll get it...
Read more >EMS LINQ Production Support and Service Level Availability ...
EMS LINQ's Service Availability commitment for a given calendar month is 99.5%. ... respects in accordance with the Documentation and, to the extent...
Read more >FAQs
Yes! We accept insurance with some insurers and states. We are constantly working to expand the insurance plans that we accept. For more...
Read more >LINQ over WCF - linq2db
NET application. Go to the LinqWcfService.svc.cs file and replace base interface with LinqToDB.ServiceModel.LinqService.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I can also use anonymous Types, joins,… interlinq allows serializeing of them. I use Json.Net for Serialization over a websocket connection.
A short update, until now the remote context works like expected!