You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
chunyu3 opened this issue
Mar 22, 2023
· 2 comments
Assignees
Labels
ClientThis issue points to a problem in the data-plane of the library.EngSysThis issue is impacting the engineering system.MgmtThis issue is related to a management-plane library.
This PR breaks the command dotnet new azsdkdpg --name Azure.XXX.Contosoz --clientName Contosoz --groupName XXX --serviceDirectory contoso --force to generate a valid template.
The Generated file name is not correct.
e.g. the project file name:
Actual: Azure.XXX.csproj
expected: Azure.XXX.Contosoz.csproj
The text was updated successfully, but these errors were encountered:
The root cause is, in dotnet 7.0.2, When we reference a derived symbol in a symbol generator, the generated symbol value does not contain the derived symbol.
jsquire
added
Client
This issue points to a problem in the data-plane of the library.
Mgmt
This issue is related to a management-plane library.
EngSys
This issue is impacting the engineering system.
and removed
needs-triage
Workflow: This is a new issue that needs to be triaged to the appropriate team.
labels
Mar 22, 2023
ClientThis issue points to a problem in the data-plane of the library.EngSysThis issue is impacting the engineering system.MgmtThis issue is related to a management-plane library.
Library name and version
dotnet new azsdkdpg
Describe the bug
This PR breaks the command
dotnet new azsdkdpg --name Azure.XXX.Contosoz --clientName Contosoz --groupName XXX --serviceDirectory contoso --force
to generate a valid template.The Generated file name is not correct.
e.g. the project file name:
Actual:
Azure.XXX.csproj
expected:
Azure.XXX.Contosoz.csproj
The text was updated successfully, but these errors were encountered: