The Wayback Machine - https://web.archive.org/web/20201201010802/https://github.com/microsoft/cpprestsdk/issues/25
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

TestRunner.exe never created and BingRequest program always throws exception #25

Closed
spencerparkin opened this issue Nov 27, 2015 · 4 comments
Labels
bug

Comments

@spencerparkin
Copy link

@spencerparkin spencerparkin commented Nov 27, 2015

An exception is always thrown in the wait entered in the BingRequest demo. I gave it a search string and a file name that I believe were valid, so I'm ruling out "garbage in, garbage out" as a problem.

Build always fails, but building again succeeds, probably because DevStudio does not get the dependencies right.

Using VS2013, v120 build tools, x64, Windows 10.

@ras0219-msft ras0219-msft added the bug label Nov 30, 2015
@kavyako
Copy link
Contributor

@kavyako kavyako commented Dec 3, 2015

Could you copy paste the build error here so we can investigate it?

@alexkaratarakis
Copy link
Contributor

@alexkaratarakis alexkaratarakis commented Dec 3, 2015

I tried:

  • cpprestsdk 2.7.0 with VS2015, x64, Windows 10
  • cpprestsdk 2.7.0 with VS2013, x64, Windows 10

and it works as expected. As kavyako mentioned above, could you provide some more info around your error messages so we can look into it?

@spencerparkin
Copy link
Author

@spencerparkin spencerparkin commented Dec 4, 2015

If it's working for you, then never mind...could've been something weirdo on my machine. I don't have everything setup anymore to test it again...switched to cURL to get my project done.

There was no build error. Every time I ran the BingRequest demo, it threw an exception deep in the wait code.

Sorry...shouldn't have said anything...or at least given a callstack.

@alexkaratarakis
Copy link
Contributor

@alexkaratarakis alexkaratarakis commented Dec 4, 2015

I see. In that case I will close this bug.
Should the issue occur again in the future, please feel free to reopen this bug or report a new one.
Thanks!

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

Successfully merging a pull request may close this issue.

None yet
4 participants
You can’t perform that action at this time.