"Input file must be a full path name" when using ReSharper

[citizenmatt]

ReSharper uses the Visual Studio editor for various windows, such as the Stack Trace Explorer. When showing one of these windows, the Error List window pops up, showing an error of EditorConfig core error: Input file must be a full path name.

Can EditorConfig not report an error if the document is in-memory, rather than a physical file?

[Mpdreamz]

We totally could yeah 👍 , cycles are a bit limited on my end though 👎

We have a massive PR waiting that I do not have the time to jump back on on for the at least a month though but will take this (and other open issues) into account then.

[philals]

+1

[brianloekkeborg]

+1

[cyberboy666]

+1

[roji]

+1

[joce]

+1

[robertcoltheart]

This is fixed in master and is currently awaiting a release to the VS gallery.

[citizenmatt]

Cool! If you can add a comment here when it's actually released, I'll tweet about it from the resharper account.

[areyling]

+1

[zvirja]

@Mpdreamz Could you please provide us with approximate estimates when we can expect new version to be released?
This issue is pretty annoying and there is no way to work around it :(

[Mpdreamz]

We currently still have these open issues that I would like to see resolved before releasing, no real estimate on those.

@citizenmatt we could use your help with one of the most blocking issues: #45 , let me know if you have time somehere to help us diagnose and fix this issue 😄

Nightlies are pushed here: https://ci.appveyor.com/project/Mpdreamz/editorconfig-visualstudio/build/artifacts

[drusellers]

YAY - here's hoping it hits VS soon.

[roji]

Any chance someone can release a version with this fix? It's been months and the issue has already been fixed... Seems like a shame to delay for so long because of other issues...

[netonjm]

+1

[DamianSuess]

+1 for a fix that was done 5.5 months ago. It's causing red flags during our build process.

[zvirja]

No need to wait for a fix from plugin side.
There is a ticket in R# and they will support EditorConfig natively soon. Therefore, if R# is installed - we can just uninstall this plugin.

[jozefizso]

It's possible to hotfix the 0.5 release with patch to this issue?

[btull89]

+1

[citizenmatt]

BTW, ReSharper 2017.1 supports EditorConfig directly now! Please give it a go :)

[illanonline]

+1