explain the codes Reflection

Question

1.00/5 (3 votes)

See more:

C#

class MyTestClass
   {
       static public void PrintMethods(string className)
       {

           try
           {
               Type classType = Type.GetType(className);

               var methodNames =
                   from methodInfo in classType.GetMethods()
                   where methodInfo.GetParameters().Any(parameterInfo => parameterInfo.ParameterType == typeof(string))
                   select methodInfo.Name;

               foreach (var method in methodNames)
                   Console.WriteLine(method);

           }
           catch (Exception)
           {

           }

       }

       static public void CallStaticMethod(string className, string methodName)
       {
           try
           {
               using (StreamReader reader = new StreamReader(@"data.txt"))
               {
                   Type.GetType(className).GetMethod(methodName, BindingFlags.Static | BindingFlags.Public).Invoke(null, new string[] { reader.ReadToEnd() });
               }
           }
           catch(Exception)
           {

           }
       }
   }

Posted 22-Sep-13 17:53pm

the dark Knight

Add a Solution

Comments

Tom Wauters 23-Sep-13 0:03am

What don't you understand?

ArunRajendra 23-Sep-13 0:05am

What you want to know. Be specific?

2 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Abhinav S · Answer 1 · 2013-09-22T18:14:00

Solution 1

You are listing out a set of methods where the method parameters are of type string.

Posted 22-Sep-13 18:14pm

Abhinav S

Sergey Alexandrovich Kryukov · Answer 2 · 2013-09-22T18:15:00

Usually, we do not "explain" the code taken by our inquirers somewhere on the Web, because doing so means loosing a huge amount of time for nothing. There is too much trash out there, so why trying to explain it all. On this forum, one of out experts demonstrated that "explanation" of a single code line could take a whole article. Remember, we know nothing about your background and knowledge and don't know how detailed the "explanation" should be. In other words, the notion of explanation is not well-defined. Anyway, not well enough to start such explanation. You rather need some general instruction on learning programming and APIs you need.

You are supposed to write your own code, and, if you are stuck, ask for help. This would be much more effective. If you really want to look how others write code, do it, but, to get explanation 1) ask the author of it, 2) find each and every word you don't understand and find it in the original documentation (in this case, MSDN). Actually, you need to do item #2 first, before asking any questions.

By the way, the code sample you show is almost self-explanatory. At the same time, in practice, reflecting the type by its name is a very bad technique, but this is only one line. Anyway, not understanding such code is rather a result of some laziness, which is normally a pretty good thing, but not in this case. You should not have looked at the sample code at all, before you read through the documentation. Only then reading someone else's code could be useful, to certain extent.

—SA