Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Make base entity classes use MarshalByRefObject
See original GitHub issueMarshalByRefObjects as you may know are for cross-AppDomain communication. If you’re going for “modern and secure” practices, implementing it would be a good idea. There are no downsides to this known to me.
AppDomains could be used to safely load DLL modules in a restricted sandboxed environment, and by using MarshalByRef enabled objects any entity can easily be accessed between AppDomains.
Code changes are easy and unnoticeable. In case of SocketEntity.cs for example, it’s a matter of changing
SocketEntity<T> : IEntity<T>
to
SocketEntity<T> : MarshalByRefObject, IEntity<T>
Issue Analytics
- State:
- Created 7 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
.NET Standard doesn’t cover AppDomains, and since Discord.Net 1.0 targets .NET Standard 1.1 and 1.3, it can’t implement AppDomain APIs. This is a frustrating issue for many that relied upon AppDomains, as you can imagine.
Closing due to https://github.com/discord-net/Discord.Net/pull/2230#issuecomment-1089247749