Same here. No external library, just code snippets.

I'm sorry, but kicking someone when he's down is highly offensive. You could have been a lot shorter and still get the point across. There was no reason to phrase it like this. Just my opinion.

The EU didn't change rules retroactively, the rules Ireland offered to Apple were not legal according to EU rules. Therefore, Apple must pay some extra taxes to Ireland, and Ireland probably will get fined at some point by the EU.

That is not what happened. See the linked article in the first post. "Member states cannot give tax benefits to selected companies - this is illegal under EU state aid rules," said Commissioner Margrethe Vestager. Since Ireland is part of the EU, it has to abide by the EU rules.

I think you're flaming 😂😂

For me, to try to solve your question, it was necessary to ask for some more info. Working with AppDomains and dynamically loading assemblies is tricky, and I need to know what it is exactly that is loaded in the AppDomain, and what the start-up parameters are of said AppDomain (like the base-directory). My apologies if this was not to your liking. Good luck solving your problem.

I implied we were talking about developers and var, not how it affects reviewers. But fair enough I guess. If you know what GetDescendant() does, then you'll know the return type (assuming here). If you don't know what the method does, then maybe that should be made clear first. What is more important, the method and what it does, or the specific technical return type? I'm not trying to convince you of anything, I'm just trying to understand your way of thinking.

Ok, I'll bite. But I am not saying this or that, just interested in your opinion. Why wouldn't you use var? What's wrong with it?

But if you don't like the option that changes a fully-specified type to 'var', why are you using it? I'm assuming here that Resharper doesn't do that by itself, or if it does that it is a 'feature' that can be turned off. (No, I am not using Resharper myself, never have) (Yes, I do prefer 'var': it saves keystrokes; intellisense provides me with the name of type if I need it)

More information is needed. - What is the base directory of the AppDomains? - How are you triggering the code in the AppDomain? - Is the SimplePlugins.DLL also stored in each plugin-subfolder? - Which assemblies are now loaded in the appdomain? Debug to find out the exact location. - 'Why doesn't IsSubclassOf find the specified derived type' - does not make sense. IsSubclassOf returns either true or false.

The delegate is immutable. So handler -= someHandler; is not modifying or updating the original delegate, it is creating a new delegate which is then stored in handler. So the copy-of-the-handler is indeed a copy of the reference to the (immutable) delegate.

And why do you have that opinion about an agile environment? What other alternative do you consider an option?

Linq is all about defining the query instead of the execution of the query. You say you can implement Except in a single line of code. Can you also do that for grouping, ordering, projection? And all those other possibilities, all used in combination? Using Ling you are sacrificing a little performance, and you are (read: should be) gaining a lot in maintenance. You can implement the above probably without problems. Can you also read the implementation of others without any problems? Using Linq you and your co-workers are all using the same methods, and therefor, can read each others code a lot easier, compared to a different implementation for you and every co-worker you have. Of course, you can completely kill the performance, and no-one will say that Linq is faster, and yes, you have to know what you are doing. But that is no different from all the 'other tools in your toolbox'.

You can easily step into it using F11. You would see the deferred execution in action ;)

Oh my, such negativity towards SO. I've been a long time user of the site myself, and while I am not saying it is perfect, most answers I see do try to help the person asking the question by answering the question as best as possible. It is true that a question that to be exactly that (a specific question) and not a general 'how do I do this or that?'. Also it is appreciated that you have tried something, and are stuck (see http://whathaveyoutried.com/). And yes, I think both things are fair to ask.

How about the AppDomain.UnhandledException Event? http://msdn.microsoft.com/en-us/library/system.appdomain.unhandledexception.aspx[^]