Comments
Sort by recent activity
Your question is a bit vague. You didn't provide information as to where you're receiving this error. Is this within Visual Studio itself, a direct command line compile of the code, or otherwise? The likely problem is that you've included a using directive for Excel and System.Windows.Forms and both name spaces contain an entry for 'Button'. This would cause a symbol resolution ambiguity between the two namespaces.
To resolve this issue, either specify the namespace and class-name directly (ala. System.Windows.Forms.Button) or include a few aliases which resolve the ambiguity by introducing a new symbol that's unambiguous, such as:
using SButton = System.Windows.Forms.Button;
using EButton = Excel.Button;
Naturally the names you'd use for both cases need to also be unambiguous, or similar problems may result. You can also create a namespace alias like so:
using E = Excel;
using Forms = System.Windows.Forms;
Then utilize namespace qualifiers to resolve it in a terser, yet correct, manner (versus the verbose full namespace+class form):
E::Button or Forms::Button.
That's the furthest I can answer your question given the lack of more information. This is really a forum for support of the Red Gate Reflector program, though. / comments
Your question is a bit vague. You didn't provide information as to where you're receiving this error. Is this within Visual Studio itself, a direct command line compile of the code, or otherwise?...
Is this a question, or a statement?
I'm pretty sure anyone who's competent enough to use a decompiler isn't going to click a dubious link like that. Are you asking for help in decompiling the dynamic link library contained within the file posted, or are you posting a link to a tutorial on how to do, what the program this board covers does, or what?
My guess, based upon the random handle, link, and response e-mail, is it's spam; perhaps even viral spam. / comments
Is this a question, or a statement?
I'm pretty sure anyone who's competent enough to use a decompiler isn't going to click a dubious link like that. Are you asking for help in decompiling the dyna...
Also I think certain other issues might arise should the given library be encrypted with a strong name. Changes to the assembly name can cause the entire assembly to fail to load, such is the benefit of a library using a strong name. Granted that's under the assumption a strong name is used.
If not, you're really limited to small changes. I'm not entirely sure on how the PEHeader and CLR header work, but I think some of them work by using position notifiers to point to data. If the data length is shifted (ie. you change the length of a string, shifting all bytes left or right depending on whether you deleted or inserted data), and the numbers aren't updated, the assembly can be viewed as corrupted. Someone with more knowledge of the headers might be able to shed some light on this.
Also I'm curious as to the reason you'd want to alter the actual target name in the first place. I can't really see a viable reason to do so other than re-branding. Perhaps more information as to why you want to change it would be pertinent, as a different path might actually be more viable for reaching your end goal. / comments
Also I think certain other issues might arise should the given library be encrypted with a strong name. Changes to the assembly name can cause the entire assembly to fail to load, such is the bene...