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
We have a custom tool that runs as part of our build process that uses Namotion.Reflection to extract the XML documentation. This runs fine on Windows and Linux, but on OS X the XML documentation file is not found.
Looking into the code I have found two bugs that should be handled:
If running on OS X, using Assembly.Location folder is not done, only check for NuGet package is done. This is in XmlDocsExtensions.GetPathByOs() (
The Assembly.CodeBase is handled differently on Windows where removing file:/// still results in an absolute path. While on Linux and OS X the first / (slash) is removed so that it becomes a relative address.
We have a custom tool that runs as part of our build process that uses
Namotion.Reflection
to extract the XML documentation. This runs fine on Windows and Linux, but on OS X the XML documentation file is not found.Looking into the code I have found two bugs that should be handled:
Assembly.Location
folder is not done, only check for NuGet package is done. This is inXmlDocsExtensions.GetPathByOs()
(Namotion.Reflection/src/Namotion.Reflection/XmlDocsExtensions.cs
Line 946 in a4354e2
Assembly.CodeBase
is handled differently on Windows where removingfile:///
still results in an absolute path. While on Linux and OS X the first/
(slash) is removed so that it becomes a relative address.Namotion.Reflection/src/Namotion.Reflection/XmlDocsExtensions.cs
Lines 751 to 765 in a4354e2
The text was updated successfully, but these errors were encountered: