Skip to content
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

InheritDoc doesn't replace tags in projects with executable output #12

Open
WindOfMind opened this issue Jul 11, 2019 · 0 comments
Open

Comments

@WindOfMind
Copy link

WindOfMind commented Jul 11, 2019

Hello!
I have ASP.NET Core Web Application (Sdk="Microsoft.NET.Sdk.Web") and target framework netcoreapp2.2.
I'm using /// <inheritdoc /> tags in my models.
And in csproj I've added post and pre-builds events:

<Target Name="PostBuild" AfterTargets="PostBuildEvent">
    <Exec Command="InheritDoc --xml-doc-file-name-patterns &quot;Fusion.*&quot; -b $(MSBuildProjectDirectory) -o" />
  </Target>

  <Target Name="PreBuild" BeforeTargets="PreBuildEvent">
    <Exec Command="dotnet tool install InheritDocTool -g" IgnoreExitCode="true" />
  </Target>

But during project building I get some warnings about finding too many assemblies for XML file.
Log from output is below:

2019-07-10 19:05:16.2412|INFO|InheritDoc.Program|InheritDoc(v2.0.2.0).Run():basePath=(..some path)DocFileNamePatterns=Fusion.*,globalSourceXmlFiles=,excludeTypes=System.Object,overwriteExisting =True
5>2019-07-10 19:05:16.2779|WARN|InheritDoc.Program|GetAssemblyFiles():Found too many assemblies for xml file ... (filepaths)
5>2019-07-10 19:05:16.2779|WARN|InheritDoc.Program|GetAssemblyFiles():Found too many assemblies for xml file ... (filepaths)
5>2019-07-10 19:05:16.4301|INFO|InheritDoc.Program|2 tag(s) replaced in 1 XML documentation file(s) (... (filepath))

So eventually tags are not replaced.
Interesting that if I delete in the bin folder file with exe and run inheritdoc from a console in this folder it will work fine.
One possible solution is to extract all models to a separate library (.dll) project, but it's not too suitable in all cases.
Any thoughts of how it can be fixed in other ways?

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

No branches or pull requests

1 participant