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.

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

WebApi in Visual Studio 2017 (latest) #12

Open
AndreasLohr opened this issue Apr 2, 2018 · 3 comments
Open

WebApi in Visual Studio 2017 (latest) #12

AndreasLohr opened this issue Apr 2, 2018 · 3 comments

Comments

@AndreasLohr
Copy link

hi,

I just tried to use the library in a WebApi project, but cannot get it running for more than 4 hours.
The problem is simply, that the result is always null. I believe, it is because the txt-file is somehow not loaded/available.
I tried without specifying any Application variables. Doesn´t work.
I tried with a hardcoded path (as application variable) in the IIS folder. Doesn´t work.
Make sure, full rights are applied to the folder. Nothing changed.
A small testproject (Webapi), that only invokes the TryParse once would be great. Because even that doesnot work for me. I have choosen some empty asp.net project and included only references for WebApi.
Thank you in advance!

Best
Andreas

@danesparza
Copy link
Owner

Do the unit tests work for you?

@AndreasLohr
Copy link
Author

Yes, run & pass.

@AndreasLohr
Copy link
Author

Can you check, if that works on your end?
By the way: Maybe it would be good to embed 1 copy of the file into the library and then try to download actual version.
Because for me it looks, that if the library doesnot, it is because the file cannot get downloaded for some reason. Whatsever reasons. Even if the embeded file would be outdated, it would be still better than no file at all.

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

No branches or pull requests

2 participants