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
{{ message }}
This repository was archived by the owner on Apr 30, 2020. It is now read-only.
I get this exception with all projects that I tried (targeting .NET 4.0; translated from German into English) to create a documentation for:
System.IndexOutOfRangeException: Index was outside the bounds of the array.
at SharpDox.Build.Roslyn.Parser.ProjectParser.SeeParser.ResolveAllSeeTokens()
at SharpDox.Build.Roslyn.RoslynParser.ResolveSeeTokens(ParserOptions parserOptions)
at SharpDox.Build.Roslyn.RoslynParser.GetParsedSolution(String solutionFile, ICoreConfigSection sharpDoxConfig, Dictionary`2 tokens, Boolean parseMethodCalls)
at SharpDox.Build.Context.Step.StructeParseCodeStep.RunStep(SDProject sdProject)
at `SharpDox.Build.Context.BuildContext.StartBuild()
I've noticed that this happens when it processes the .NET 4.0 components. The projects themselves seem to be completely fine. I also tried several builds linked in other/similar issues that I found here on GitHub. Unfortunately, none of them worked neither.
Best,
Dominic
The text was updated successfully, but these errors were encountered:
alright, no problem. I know that. :D
I've seen that you've asked in a further comment, if the project is open source. So, if you want to reproduce it maybe using the project, you can find it here: https://github.com/ProgTrade/nUpdate (master)
Okay, I thought so as well, but it seems there is still a problem. :D Did you maybe override the master with commits that excluded this fix again?
Anyway, thanks for your help. :)
Hi,
I get this exception with all projects that I tried (targeting .NET 4.0; translated from German into English) to create a documentation for:
I've noticed that this happens when it processes the .NET 4.0 components. The projects themselves seem to be completely fine. I also tried several builds linked in other/similar issues that I found here on GitHub. Unfortunately, none of them worked neither.
Best,
Dominic
The text was updated successfully, but these errors were encountered: