Closed GoogleCodeExporter closed 8 years ago
Ah, I see now. I needed to change all namespaces named
MSNPSharp.MSNWS.XXX;
to
MSNPSharp.Web_References.MSNWS.XXX;
Still, this is still a bug if it won't compile in Visual Studio 2010 without
making dozens of changes by hand.
Original comment by not...@gmail.com
on 2 Dec 2010 at 11:43
Wasn't as simple as just "change A.XXX to B.XXX", but I got it to compile after
adjusting several using statements. All of them had to do with where MSNWS was
located, though.
Original comment by not...@gmail.com
on 2 Dec 2010 at 11:48
Might have to do with how I compiled it, so I'll post this here.
I wrote a simple app that logs into MSN, sends a message, and exits. Some
error happened in SerializableDictionary.cs, line 111:
reader.ReadStartElement("item");
reader.ReadStartElement("key");
>> TKey key = (TKey)keySerializer.Deserialize(reader);
reader.ReadEndElement();
reader.ReadStartElement("value");
Unfortunately I didn't take note of the details and couldn't get it to occur
again :(
Original comment by not...@gmail.com
on 3 Dec 2010 at 12:05
You should post this issue to Microsoft, I think it's a bug of VS2010. But I
will still think about how to overcome this.
Original comment by freezing...@gmail.com
on 3 Dec 2010 at 12:09
And for the 2nd, issue, please provide detail log for the error.
Original comment by freezing...@gmail.com
on 3 Dec 2010 at 12:15
To be clear, what's the latest version of Visual Studio you test MSNPSharp with?
Original comment by not...@gmail.com
on 3 Dec 2010 at 12:21
Posted to Microsoft:
https://connect.microsoft.com/VisualStudio/feedback/details/627277/visual-studio
-2010-conversion-wizard-issues
Original comment by not...@gmail.com
on 3 Dec 2010 at 12:26
vs2005
Original comment by freezing...@gmail.com
on 3 Dec 2010 at 12:32
Please check out svn and try again. It should work.
Original comment by hepha...@gmail.com
on 3 Dec 2010 at 8:34
Thanks, a checkout of MSNPSHARP_31_STABLE now compiles right away after going
through the VS2010 conversion wizard!
Original comment by not...@gmail.com
on 3 Dec 2010 at 5:11
Do you still think the VS2010 conversion wizard was causing issues? (I'm not
sure if you fixed it as a workaround or found some MSNPSharp problem that fixed
it)
Original comment by not...@gmail.com
on 3 Dec 2010 at 5:15
No, this is not MS$ issue. I think when Pang converted the project files to
mono develop format, web references was gone. See r1868.
I think everything is ok... It there is a problem with this?
>> TKey key = (TKey)keySerializer.Deserialize(reader);
Original comment by hepha...@gmail.com
on 3 Dec 2010 at 5:31
Nope it all looks good, thanks.
No idea what to think about the Deserialize error; it was just peculiar to me
that it happened the *first* time I tried to test the build, so I figured it
must have had to do with the way I built MSNPSharp, but it was probably just a
big coincidence. I couldn't reproduce it, so just ignore it. If it happens
again, I'll post it as a new issue with more details.
Original comment by not...@gmail.com
on 3 Dec 2010 at 5:47
Good job guys, but do you have any idea of how to avoid that? Or I should post
an issue to the MonoDevelop team?
Original comment by freezing...@gmail.com
on 3 Dec 2010 at 10:08
Original issue reported on code.google.com by
not...@gmail.com
on 2 Dec 2010 at 11:39