Skip to content
This repository was archived by the owner on Apr 30, 2020. It is now read-only.

IndexOutOfRangeException when parsing .NET 4.0 components #91

Open
dbforge opened this issue Oct 1, 2017 · 5 comments
Open

IndexOutOfRangeException when parsing .NET 4.0 components #91

dbforge opened this issue Oct 1, 2017 · 5 comments

Comments

@dbforge
Copy link

dbforge commented Oct 1, 2017

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:

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

@geaz
Copy link
Owner

geaz commented Oct 4, 2017

Hi Dominic,

will check this issue in the next few days. Just returned from vacation :)

@dbforge
Copy link
Author

dbforge commented Oct 4, 2017

Hi,

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)

Best,
Dominic

@geaz
Copy link
Owner

geaz commented Oct 9, 2017

I saw that this bug was already fixed in a past commit. I will try to release a new version today which will fix your issue.

@dbforge
Copy link
Author

dbforge commented Oct 9, 2017

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. :)

@geaz
Copy link
Owner

geaz commented Oct 9, 2017

The fixes are just in the dev branch at the moment.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants