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.

Sign up for GitHub

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

Jump to bottom

Null path when converting project - workaround: restart VS #173

Closed
B0R1K opened this issue Sep 7, 2018 · 5 comments
Closed

Null path when converting project - workaround: restart VS #173

B0R1K opened this issue Sep 7, 2018 · 5 comments
Labels
needs-repro Needs either the input that caused the error, or more information to allow reproducing the error

Comments

@B0R1K
Copy link

B0R1K commented Sep 7, 2018

Not sure what other info to get for this...

image
@B0R1K B0R1K changed the title VB -> C#: Error Converting... VB -> C#: Error Converting Project... Sep 7, 2018
@GrahamTheCoder
Copy link
Member

Thanks for the report, I can imagine that would happen if you try to convert a brand new solution that hasn't been saved anywhere yet. If that's it, let me know and I'll at least put in a better error message explaining.

@B0R1K
Copy link
Author

B0R1K commented Sep 9, 2018

no i am trying to convert an Existing project inside the Existing solution

@B0R1K
Copy link
Author

B0R1K commented Sep 10, 2018

after rebooting problem went away...

@GrahamTheCoder GrahamTheCoder changed the title VB -> C#: Error Converting Project... VB -> C#: Null path when converting project Sep 11, 2018
@GrahamTheCoder
Copy link
Member

Thanks for the update. The only other thing I can think of is that either the solution/project hadn't fully loaded yet (or "lightweight solution mode" maybe?), or that the object I'm asking for the file path has got somehow got disposed/disconnected.

I'll try reproducing this on a large solution during load - was yours a big solution?

@GrahamTheCoder GrahamTheCoder changed the title VB -> C#: Null path when converting project Null path when converting project Sep 18, 2018
@GrahamTheCoder GrahamTheCoder changed the title Null path when converting project Null path when converting project - workaround: restart VS Sep 18, 2018
@GrahamTheCoder GrahamTheCoder added the needs-repro Needs either the input that caused the error, or more information to allow reproducing the error label Oct 10, 2018
@GrahamTheCoder GrahamTheCoder mentioned this issue Feb 13, 2019
Closed
@GrahamTheCoder
Copy link
Member

GrahamTheCoder commented Mar 2, 2019 •
edited
Loading

My fix for #243 should avoid this error happening again. Though there's a small chance that a project file could be missed from the conversion in the case this previously happened. If that happens we can open a new issue for it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
needs-repro Needs either the input that caused the error, or more information to allow reproducing the error
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@B0R1K @GrahamTheCoder