• Create a class with the name PackageCreation in a c# project called AProj. Add a static method with the method signature public void Execute()


• Create another class call CallPackageCreation in another c# project called BProj, inside the class create a method call PackageCreation, inside the method type in this code:PackageCreation.Execute()


• Now I want to change the method name in BProj PackageCreation to PackageCreationMethod, I use VA refactoring tool to do this. I expect to only rename the method, but not the class. But the Rename function offers me two instances of PackageCreation, including the class reference in the method PackageCreation

    class bugFindRefPackageCreation
    {
        public static void Execute()
        {

        }
    };

    class bugFindRefCallPackageCreation
    {
        public void bugFindRefPackageCreation()
        {
            bugFindRefPackageCreation.Execute();  // compiler error here
        }
    };

quote:

---

Originally posted by feline

I appear to be doing something wrong, but I am not sure what. I don't do much C# programming, so perhaps I have made a silly mistake. Using VS2005 in projA I have the code:

    class bugFindRefPackageCreation
    {
        public static void Execute()
        {

        }
    };

and in projB I have the code:

    class bugFindRefCallPackageCreation
    {
        public void bugFindRefPackageCreation()
        {
            bugFindRefPackageCreation.Execute();  // compiler error here
        }
    };

I have made the class / method names a bit more unique, to make sure there are no problems with the other classes in my test project, but this should not matter. projB has the correct using namespace and correct dependencies to call items in projA, I already have a different test setup and working using these two projects.

First problem - the code does not compile. I get the error message:

'c_sharp_class_library2.Bugs.bugFindRefCallPackageCreation.bugFindRefPackageCreation()' is a 'method', which is not valid in the given context


Second problem - I have run both Find References and Rename on "bugFindRefPackageCreation" in both projects, and it only ever finds references in that project, so I am not seeing the problem you are reporting.

---

• You had it right when you said that code cannot compile. But this is precisely the reason why I want to rename the method to something else


• I don't understand what do you mean by and it only ever finds references in that project, for me, when I tried to find reference for the method "bugFindRefPackageCreation", it should only return one reference, namely, the method itself, not the static function in other class that it calls

    class bugFindRefPackageCreation    // this is found
    {
        public static void Execute()
        {

        }
    };

    class bugFindRefCallPackageCreation
    {
        public void bugFindRefPackageCreation()   // this is found
        {
            bugFindRefPackageCreation.Execute();  // and this is found
        }
    };

quote:

---

Originally posted by feline

I am confused. Using my code, when I run Find References in ProjA on "bugFindRefPackageCreation" with the code:

    class bugFindRefPackageCreation    // this is found
    {
        public static void Execute()
        {

        }
    };

VA finds one reference, as indicated by the comment.

When I run Find References on ProjB on "bugFindRefPackageCreation" with the code:

    class bugFindRefCallPackageCreation
    {
        public void bugFindRefPackageCreation()   // this is found
        {
            bugFindRefPackageCreation.Execute();  // and this is found
        }
    };

VA finds two references, as indicated by the comment. To me this seems quite reasonable. Is this what you are seeing? If you are seeing something different then it suggests my test is not setup correctly.

If this is what you are seeing then my initial reaction is VA see's something that looks recursive, and it is doing the best it can.

---

quote:

---

Originally posted by feline

I think I understand now.

My concern is how to tell that bugFindRefPackageCreation is a class on one line and a function on another line.

If we ignore the second project for now, since that is not strictly relevent, and just look at this small piece of code, I can tell that bugFindRefPackageCreation.Execute is not a function, since there are no brackets on bugFindRefPackageCreation.

However since this is C# bugFindRefPackageCreation might be a property which returns a class type which supports .Execute()

Does this make sense?

I can picture a situation where VA is going to have very little chance of working out what is going on, so is going to behave in an "unpredictable" manor if we try and make this change. At least this behaviour, while undesirable, is predictable.

---