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
I fixed a bug in TestCentric.Extensibility due to incorrect use of the extension method GetFrameworkName in CecilExtensions.cs. That method merely returns the value of the assembly's TargetFrameworkAttribtue, which is not always present.
However, it was being used on the assumption that it always returned the TargetFramework for which the assembly had been built. Determining that would require some additional steps and involves a few assumptions, making it an unsuitable library API.
After thinking it over, I believe this API should be removed. The assumptions and necessary steps can be incorporated in the individual applications that use TestCentric.Metadata. In fact, that's how I resolved the bug in TestCentric.Extensibility.
The text was updated successfully, but these errors were encountered:
I fixed a bug in TestCentric.Extensibility due to incorrect use of the extension method
GetFrameworkName
inCecilExtensions.cs
. That method merely returns the value of the assembly'sTargetFrameworkAttribtue
, which is not always present.However, it was being used on the assumption that it always returned the TargetFramework for which the assembly had been built. Determining that would require some additional steps and involves a few assumptions, making it an unsuitable library API.
After thinking it over, I believe this API should be removed. The assumptions and necessary steps can be incorporated in the individual applications that use TestCentric.Metadata. In fact, that's how I resolved the bug in TestCentric.Extensibility.
The text was updated successfully, but these errors were encountered: