Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I backuped a project and then reinstalled my OS (Win 7, if it matters).
I reinstalled VS 2010, and I reinstalled the support of protobuf.net to VS 2010.
Before that, the serializing and de-serializing were both perfectly OKAY, but now the wont work, and every time i step into them with the debugger:
(edit)
From the comments, it sounds like the question relates to the production versions from the home page, here. In which case, it simply sounds like the _fixed is the directory I did the build from.
You could try including the pdb (from the zip) alongside the dll; that is the debugging symbols, and will probably help the trace tool you are using. But more important is: what does the exception say?
Some psychic debugging… is it simply that it sits there doing nothing? That is the expected behaviour if the input stream is not yielding data, and hasn’t formally closed itself – for example reading from an open socket that isn’t sending data. Where are you reading from in this scenario?