Skip to content

Conversation

@paul1956
Copy link
Contributor

@paul1956 paul1956 commented Aug 24, 2024

Fixes partial fix for #11215

Proposed changes

Remove Utils that conflicts with .Net Core but different in return values
Modernize ExceptionUtils, it was originally ported from VB-6 and much of it no longer is needed and its overly complicated.
Fix broken TimeTests

Customer Impact

None

Regression?

  • Time Tests were broken and failing silently

Risk

  • Minimal 100% Test coverage of replaced code

Test methodology

100% Test Coverage

Test environment(s)

Visual Studio 100% Coverage

Microsoft Reviewers: Open in CodeFlow

@paul1956 paul1956 requested a review from a team as a code owner August 24, 2024 23:07
@paul1956 paul1956 changed the title Modernize ExceptionUtil,s fix Time Tests REVIEW 1st Modernize ExceptionUtils fix Time Tests REVIEW 1st Aug 24, 2024
@paul1956 paul1956 changed the title Modernize ExceptionUtils fix Time Tests REVIEW 1st Modernize ExceptionUtils fix, Time Tests REVIEW 1st Aug 24, 2024
@codecov
Copy link

codecov bot commented Aug 24, 2024

Codecov Report

Attention: Patch coverage is 67.07819% with 80 lines in your changes missing coverage. Please review.

Project coverage is 75.19972%. Comparing base (463173d) to head (a831f48).
Report is 13 commits behind head on main.

Additional details and impacted files
@@                 Coverage Diff                 @@
##                main      #11982         +/-   ##
===================================================
+ Coverage   75.18905%   75.19972%   +0.01067%     
===================================================
  Files           3073        3076          +3     
  Lines         632769      632876        +107     
  Branches       46794       46794                 
===================================================
+ Hits          475773      475921        +148     
+ Misses        153610      153554         -56     
- Partials        3386        3401         +15     
Flag Coverage Δ
Debug 75.19972% <67.07819%> (+0.01067%) ⬆️
integration 18.02949% <11.85185%> (-0.01097%) ⬇️
production 48.44499% <42.96296%> (+0.01855%) ⬆️
test 97.02183% <97.22222%> (-0.00010%) ⬇️
unit 45.45560% <40.74074%> (+0.05883%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

@paul1956 paul1956 changed the title Modernize ExceptionUtils fix, Time Tests REVIEW 1st Modernize ExceptionUtils, fix Time Tests REVIEW 1st Aug 25, 2024
@paul1956 paul1956 changed the title Modernize ExceptionUtils, fix Time Tests REVIEW 1st Modernize ExceptionUtils add Test Coverage, fix Time Tests REVIEW 1st Aug 25, 2024
@paul1956
Copy link
Contributor Author

paul1956 commented Aug 27, 2024

@lonitra @Tanya-Solyanik @KlausLoeffelmann Not sure who I should be tagging, I have split my large VB PRs to 4 small(er) PR's.

This one is logically the most complex but has 100% test coverage of the change.
The following two #11987 which adds test infrastructure (in response to a closed PR) and #11863 both add tests

The final #11867 is what I started a year ago is to replace WebClient with HTTP initially for download. It also adds Async NetworkDownload functions but they require an API review so they are not public. This last PR only changes a few files and adds SR strings, but it relies on everything before for test coverage.

@paul1956 paul1956 changed the title Modernize ExceptionUtils add Test Coverage, fix Time Tests REVIEW 1st Modernize VB ExceptionUtils add Test Coverage, fix Time Tests REVIEW 1st Aug 27, 2024
Copy link
Member

@lonitra lonitra left a comment

Choose a reason for hiding this comment

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

Couple comments, otherwise generally LGTM


Imports System.Runtime.CompilerServices

<Assembly: InternalsVisibleTo("Microsoft.VisualBasic.Forms.Tests, PublicKey=002400000480000094000000060200000024000052534131000400000100010007d1fa57c4aed9f0a32e84aa0faefd0de9e8fd6aec8f87fb03766c834c99921eb23be79ad9d5dcc1dd9ad236132102900b723cf980957fc4e177108fc607774f29e8320e92ea05ece4e821c0a5efe8f1645c4c0c93c1ab99285d622caa652c1dfad63d745d6f2de5f17e5eaf0fc4963d261c8a12436518206dc093344d5ad293")>
Copy link
Member

Choose a reason for hiding this comment

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

Why is this needed?

Copy link
Contributor Author

@paul1956 paul1956 Sep 5, 2024

Choose a reason for hiding this comment

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

If you mean the public key, it does not work without it. Possibly because there are 2 project namespaces with the same name, 1 in VB and another in C#. I opened an issue #11031 about this last year and it’s still open.

Copy link
Member

Choose a reason for hiding this comment

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

I see, @KlausLoeffelmann could you provide guidance on whether this is the preferred approach for writing tests which need visibility?

@lonitra lonitra added the waiting-author-feedback The team requires more information from the author label Sep 5, 2024
@dotnet-policy-service dotnet-policy-service bot removed the waiting-author-feedback The team requires more information from the author label Sep 5, 2024
@lonitra lonitra added the waiting-author-feedback The team requires more information from the author label Sep 5, 2024
@dotnet-policy-service dotnet-policy-service bot removed the waiting-author-feedback The team requires more information from the author label Sep 5, 2024
@lonitra lonitra added the waiting-author-feedback The team requires more information from the author label Sep 6, 2024
…/TestUtilities/TestData/DualTimeZones.TimeZoneNames.vb

Co-authored-by: Loni Tra <[email protected]>
@dotnet-policy-service dotnet-policy-service bot removed the waiting-author-feedback The team requires more information from the author label Sep 6, 2024
@paul1956
Copy link
Contributor Author

@lonitra any more feedback? What are next steps?

Copy link
Member

@lonitra lonitra left a comment

Choose a reason for hiding this comment

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

LGTM

@lonitra lonitra added the ready-to-merge PRs that are ready to merge but worth notifying the internal team. label Sep 10, 2024
@lonitra lonitra merged commit ce8b46f into dotnet:main Sep 11, 2024
@dotnet-policy-service dotnet-policy-service bot added this to the 10.0 Preview1 milestone Sep 11, 2024
@dotnet-policy-service dotnet-policy-service bot removed the ready-to-merge PRs that are ready to merge but worth notifying the internal team. label Sep 11, 2024
@github-actions github-actions bot locked and limited conversation to collaborators Oct 14, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants