Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

[QUESTION]"Part URI cannot start with two forward slashes " occurs when v4 to v5 #1459

Closed
GitOffice opened this issue Feb 9, 2020 · 8 comments · Fixed by #1466
Closed

[QUESTION]"Part URI cannot start with two forward slashes " occurs when v4 to v5 #1459

GitOffice opened this issue Feb 9, 2020 · 8 comments · Fixed by #1466
Assignees
Labels

Comments

@GitOffice
Copy link

Install-Package LiteDB -Version 4.1.4 is OK, but it is not for Version 5.0.1
73990223-7f175380-4983-11ea-8af2-b2350428e025

@mbdavid
Copy link
Collaborator

mbdavid commented Feb 10, 2020

Is this error occurs only with LiteDB? I try reproduce here but has no problem (and there is no more issues about this).

@JensSchadron JensSchadron self-assigned this Feb 10, 2020
@JensSchadron
Copy link
Contributor

While I can't reproduce this issue myself, I'm going to investigate this a bit more.

@JensSchadron
Copy link
Contributor

I think I might have a possible solution for this issue.
As per this response, I might be able to resolve it by leaving the PackagePath attribute for the License file empty in the csproj file.
Another solution would be to give the license file an extension (.txt or .md) as per this link

@GitOffice I also noticed that you're using a pretty old version of the Package Manager Console Host (v2.12.0.817). I, myself, am on v5.4.0.6292 so that might explain why both David and I can't reproduce your issue :)

@mbdavid
Copy link
Collaborator

mbdavid commented Feb 10, 2020

Wow, @JensSchadron can be right. v5 has update 2 tags: License e Icon as recommended nuget upload package

@JensSchadron
Copy link
Contributor

@GitOffice So a new version (5.0.3) will be released somewhere next week as stated in #1466.
Please let us know if the fix I did actually works :) If not, I'll try fixing it the other way. So, best case, you can install LiteDB next week, worst case in 2 weeks from now.

@GitOffice
Copy link
Author

Got it.Thanks.

@JensSchadron
Copy link
Contributor

@GitOffice 5.0.3 just got released today, could you please let me know if you could install this version?

@GitOffice
Copy link
Author

Thanks, It works and saves my tons of time.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants