Skip to content

Fix issues with moving of Diagnostics project #405

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 5 commits into
base: develop
Choose a base branch
from

Conversation

ilijagrbic
Copy link
Contributor

@ilijagrbic ilijagrbic commented Apr 15, 2025

This PR Addresses several issues with ongoing move of Diagnostics project.

1. Versioning
We had an issue with Microsoft.ServiceFabric.Diagnostics package version.
It was generated as version 1.0.0.0, which would fail AsmSpy verification if imported into WindowsFabric repo. It turns out version for this assembly was not generated properly, which this pull request addresses by modifying csproj of this project to be in line with other projects in this repo.

Furthermore, since this project is moved from WindowsFabric repo, where it had version 11.0.0.0 (same as SF version), we need to keep the versioning consistent, so this is addressed by using a conditional MajorVersion property - 12 for this project, 9 for all the rest.

2. References to old Diagnostics package
References to old diagnostics package need to be removed and replaces with references to the Diagnostics project. The reference itself was also removed from Directory.Packages.props

3. Bump version -> 9.3.0

@ilijagrbic ilijagrbic changed the title Fix version for Diagnostics dll Fix issues with moving of Diagnostics project Apr 15, 2025
@ilijagrbic ilijagrbic marked this pull request as ready for review April 15, 2025 14:52
@@ -11,9 +11,11 @@
<AllowUnsafeBlocks>true</AllowUnsafeBlocks>
<NoWarn>1591</NoWarn>
</PropertyGroup>
<ItemGroup>
<ProjectReference Include="..\Microsoft.ServiceFabric.Diagnostics\Microsoft.ServiceFabric.Diagnostics.csproj" />
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you move the new ProjectReference to the same ItemGroup with the other project references and sort the list alphabetically? I use the sort selected lines command in VS and VSCode for this.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Awesome, I was unaware of this feature. Thanks for point it out. :)

<PackageReference Include="Microsoft.ServiceFabric.FabricTransport.Internal" />
</ItemGroup>
<ItemGroup>
<ProjectReference Include="..\Microsoft.ServiceFabric.Services.Remoting\Microsoft.ServiceFabric.Services.Remoting.csproj" />
<ProjectReference Include="..\Microsoft.ServiceFabric.Services\Microsoft.ServiceFabric.Services.csproj" />
<ProjectReference Include="..\Microsoft.ServiceFabric.Diagnostics\Microsoft.ServiceFabric.Diagnostics.csproj" />
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you re-sort these project references? It looks like it was sorted before.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I will do this for both this and other project files.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants