it helps some times Your link is contained in the variable link but hasn't been attached to the DOM yet, so when you try to search for it, using $("div#more a") nothing is found because jQuery is searching the HTML of your page, not the HTML you dynamically added to some variable. You have two options:
var link = $('#more a');
var linker = "http://en.wikipedia.org/wiki/" + entry;
var link = $('<div id="more" contenteditable="true"><p><a href="' + linker + '" id="morelink">Click here</a> to read more.</p></div>');
// The link is now only stored in the variable we created.
// We need to add it to our page. You can replace 'body' with the parent element that the link should be added to.
Adding a custom attribute to a return value using a ParameterBuilder; attribute doesn't show when reflected -- why?
hope this fix your issue It appears I should have paid more attention as I was using the wrong MethodInfo property. Instead of MethodInfo's "ReturnType", I should have been using either "ReturnParameter", or for this specific case, "ReturnTypeCustomAttributes" -- either work for this purpose. "ReturnParameter" specifically mentions custom modifiers. Oops!
var returnCustomAttributes = type.GetMethod("Invoke").ReturnParameter.GetCustomAttributes(typeof(MarshalAsAttribute), false);
checking if any class has a custom attribute defined in assemby where both custom attribute and class are loaded dynamic
Any of those help Your architecture is flawed. It seems you have declared ServiceContractAttribute multiple times, and then yes, the cast won't ever work, since each declaration produces a distinct type. You have to decompose ServiceContractAttribute into a separate assembly defining the common API between the host application and service assemblies, and share it across all services.