Failure when controller contains several action methods with the same name

[gmoneh]

If a controller contains several action methods with the same name, the generated code contains ambiguous definitions:

Example:

Have a controller that contains two EditOrderAddress action methods. The generated code is:

    [GeneratedCode("R4Mvc", "1.0")]
    static readonly ActionParamsClass_EditOrderAddress s_EditOrderAddressParams = new ActionParamsClass_EditOrderAddress();
    [GeneratedCode("R4Mvc", "1.0"), DebuggerNonUserCode]
    public ActionParamsClass_EditOrderAddress EditOrderAddressParams => s_EditOrderAddressParams;
    [GeneratedCode("R4Mvc", "1.0"), DebuggerNonUserCode]
    public class ActionParamsClass_EditOrderAddress
    {
        public readonly string model = "model";
    }

    [GeneratedCode("R4Mvc", "1.0")]
    static readonly ActionParamsClass_EditOrderAddress s_EditOrderAddressParams = new ActionParamsClass_EditOrderAddress();
    [GeneratedCode("R4Mvc", "1.0"), DebuggerNonUserCode]
    public ActionParamsClass_EditOrderAddress EditOrderAddressParams => s_EditOrderAddressParams;
    [GeneratedCode("R4Mvc", "1.0"), DebuggerNonUserCode]
    public class ActionParamsClass_EditOrderAddress
    {
        public readonly string oipID = "oipID";
        public readonly string addressType = "addressType";
        public readonly string address = "address";
        public readonly string setAsDefault = "setAsDefault";
        public readonly string saveToAddressBook = "saveToAddressBook";
    }

As you can see, the same identifiers are used twice, therefore causing a compile error on the project.

This issue is specific to version alpha 00395. In previous versions, this was not the case.

[mazycz]

Same for me, when code looks like this

[HttpGet]
public virtual IActionResult ActionName(string mdl)
{
// some code
}

[HttpPost]
public virtual IActionResult ActionName(string mdl2)
{
// some code
}

[dchaib]

I believe this has been caused by #139.

If you don't need this new feature, you can disable it in the settings, by setting GenerateParamsForActionMethods to false. It did the trick for me.

[mazycz]

It Works!
Thank you.

[MarkFl12]

Just to confirm I'm still having this issue preventing me from using GenerateParamsForActionMethods in my project. Considering the Microsoft docs push you into naming your form submission POST controller action as an overload of the GET, this is rather a blocker to the feature being useful.