[BUG] Not able to create VirtualMachineScaleSetVM instance for unit test. Ambiguous constructor call for Azure compute SDK > 47.0

[KalpeshChavan12]

Describe the bug
Compilation error while creating instance of VirtualMachineScaleSetVM class instance for unit test.

Expected behavior
Following should compile

 var vmssVm = new VirtualMachineScaleSetVM(location: "",
                                                    sku: new Sku() { Name = "xyz" },
                                                    storageProfile: new StorageProfile()
                                                    {
                                                        OsDisk = new OSDisk()
                                                        {
                                                            OsType = OperatingSystemTypes.Linux
                                                        }
                                                    });

Actual behavior (include Exception or Stack Trace)
What is the actual behavior?
Compilation error, ambiguous call

Program.cs(46,30,46,54): error CS0121: The call is ambiguous between the following methods or properties: 'VirtualMachineScaleSetVM.VirtualMachineScaleSetVM(string, string, string, string, IDictionary<string, string>, string, Sku, bool?, string, VirtualMachineScaleSetVMInstanceView, HardwareProfile, StorageProfile, AdditionalCapabilities, OSProfile, SecurityProfile, NetworkProfile, VirtualMachineScaleSetVMNetworkProfileConfiguration, DiagnosticsProfile, SubResource, string, string, string, VirtualMachineScaleSetVMProtectionPolicy, Plan, IList<VirtualMachineExtension>, IList<string>)' and 'VirtualMachineScaleSetVM.VirtualMachineScaleSetVM(string, string, string, string, IDictionary<string, string>, string, Sku, bool?, string, VirtualMachineScaleSetVMInstanceView, HardwareProfile, StorageProfile, AdditionalCapabilities, OSProfile, SecurityProfile, NetworkProfile, VirtualMachineScaleSetVMNetworkProfileConfiguration, DiagnosticsProfile, SubResource, string, string, string, VirtualMachineScaleSetVMProtectionPolicy, Plan, IList<VirtualMachineExtension>)'

To Reproduce
Steps to reproduce the behavior (include a code snippet, screenshot, or any additional information that might help us reproduce the issue)

1. Create new project and create class as mentioned in issue.
2. Use https://www.nuget.org/packages/Microsoft.Azure.Management.Compute >= 47.0
3. Build project

Note: Build successful version <= 46.0.0

Environment:

• Name and version of the Library package used: [e.g. Azure.Storage.Blobs 12.2.0]
• Hosting platform or OS and .NET runtime version (dotnet --info output for .NET Core projects): [e.g. Azure AppService or Windows 10 .NET Framework 4.8]
• IDE and version :: Visual Studio 19

[jsquire]

Thank you for your feedback. Tagging and routing to the team member best able to assist.

[ghost]

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @Drewm3, @avirishuv.

Issue Details

---

Describe the bug
Compilation error while creating instance of VirtualMachineScaleSetVM class instance for unit test.

Expected behavior
Following should compile

 var vmssVm = new VirtualMachineScaleSetVM(location: "",
                                                    sku: new Sku() { Name = "xyz" },
                                                    storageProfile: new StorageProfile()
                                                    {
                                                        OsDisk = new OSDisk()
                                                        {
                                                            OsType = OperatingSystemTypes.Linux
                                                        }
                                                    });

Actual behavior (include Exception or Stack Trace)
What is the actual behavior?
Compilation error, ambiguous call

Program.cs(46,30,46,54): error CS0121: The call is ambiguous between the following methods or properties: 'VirtualMachineScaleSetVM.VirtualMachineScaleSetVM(string, string, string, string, IDictionary<string, string>, string, Sku, bool?, string, VirtualMachineScaleSetVMInstanceView, HardwareProfile, StorageProfile, AdditionalCapabilities, OSProfile, SecurityProfile, NetworkProfile, VirtualMachineScaleSetVMNetworkProfileConfiguration, DiagnosticsProfile, SubResource, string, string, string, VirtualMachineScaleSetVMProtectionPolicy, Plan, IList<VirtualMachineExtension>, IList<string>)' and 'VirtualMachineScaleSetVM.VirtualMachineScaleSetVM(string, string, string, string, IDictionary<string, string>, string, Sku, bool?, string, VirtualMachineScaleSetVMInstanceView, HardwareProfile, StorageProfile, AdditionalCapabilities, OSProfile, SecurityProfile, NetworkProfile, VirtualMachineScaleSetVMNetworkProfileConfiguration, DiagnosticsProfile, SubResource, string, string, string, VirtualMachineScaleSetVMProtectionPolicy, Plan, IList<VirtualMachineExtension>)'

To Reproduce
Steps to reproduce the behavior (include a code snippet, screenshot, or any additional information that might help us reproduce the issue)

1. Create new project and create class as mentioned in issue.
2. Use https://www.nuget.org/packages/Microsoft.Azure.Management.Compute >= 47.0
3. Build project

Note: Build successful version <= 46.0.0

Environment:

• Name and version of the Library package used: [e.g. Azure.Storage.Blobs 12.2.0]
• Hosting platform or OS and .NET runtime version (dotnet --info output for .NET Core projects): [e.g. Azure AppService or Windows 10 .NET Framework 4.8]
• IDE and version :: Visual Studio 19

Author:	KalpeshChavan12
Assignees:	allenjzhang
Labels:	Compute - VMSS, Service Attention, Mgmt
Milestone:	-

[yungezz]

route to service team to have a look

[amjads1]

@avirishuv Could you please look into the issue?

[avirishuv]

hi @yungezz is this an issue in the SDK layer, would you mind investigating?

[yungezz]

hi @HarveyLink could you help to take a look? thanks

[HarveyLink]

Hi @KalpeshChavan12 , this issue has been fixed in version 49.1.0, would you mind update to the latest version and try your code?

[ghost]

Hi @KalpeshChavan12. Thank you for opening this issue and giving us the opportunity to assist. We believe that this has been addressed. If you feel that further discussion is needed, please add a comment with the text “/unresolve” to remove the “issue-addressed” label and continue the conversation.

[ghost]

Hi @KalpeshChavan12, since you haven’t asked that we “/unresolve” the issue, we’ll close this out. If you believe further discussion is needed, please add a comment “/unresolve” to reopen the issue.