Cannot build MSNPSharp in Visual Studio 2010

[GoogleCodeExporter]

Steps to reproduce the problem:
1. Download the source of any version of MSNPSharp as of 2010-12-02
2. Open the solution in Visual Studio 2010
3. Run the Visual Studio 2010 conversion wizard
4. Attempt to compile the solution

I can't compile MSNPSharp because I only have Visual Studio 2010 and it won't 
compile after running the conversion wizard. I get an enormormous number of 
errors (136) similar to the following:

Error   94  The type or namespace name 'ABContactAddCompletedEventHandler' could 
not be found (are you missing a using directive or an assembly reference?) 
[...snip...]\MSNPSHARP_31_STABLE\MSNPSharp\Services\ContactService.cs   1158    133 M
SNPSharp

Error   47  The type or namespace name 'BaseMember' could not be found (are you 
missing a using directive or an assembly 
reference?) [...snip...]\MSNPSHARPSVN\MSNPSHARP_31_STABLE\MSNPSHARP_31_STABLE\MS
NPSharp\IO\SerializableClasses.cs   202 79  MSNPSharp

Other missing names:
  ABContactAddCompletedEventHandler
  abHandleType
  CircleInverseInfoType
  ABServiceBinding
  ActivityDetailsType
  BaseMember
  ContactType
  ExpressionProfileAttributesType
  GetContactsRecentActivityResultType
  MSNWS

I'm running Windows 7 64-bit edition. I just wish there was an 
MSNPSharp_31_stable.dll (ideally I'd like both 32-bit and 64-bit) I could 
download somewhere, or at least some instructions on how to compile this thing. 

I went around (to files ContactService.cs, CircleList.cs, XMLContactList.cs, 
Circle.cs, and many more) and let VS2010 auto-resolve using statements, and it 
looks like there were a lot of places where the following using statement is 
missing:

    using MSNPSharp.Web_References.MSNWS.MSNABSharingService;

SingleSignOn.cs needed this:

    using MSNPSharp.Web_References.MSNWS.MSNSecurityTokenService;

RSIServiceWrapper.cs needed this:

    using MSNPSharp.Web_References.MSNWS.MSNRSIService;

SecurityTokenServiceWrapper.cs needed this:

    using MSNPSharp.Web_References.MSNWS.MSNSecurityTokenService;

SharingServiceBindingWrapper.cs needed this:

    using MSNPSharp.Web_References.MSNWS.MSNABSharingService;

StorageServiceWrapper.cs needed this:

    using MSNPSharp.Web_References.MSNWS.MSNStorageService;

WhatsUpServiceBindingWrapper.cs needed this:

    using MSNPSharp.Web_References.MSNWS.MSNABSharingService;

After adding all those using statements, all I have left is 25 errors that all 
effectively say the same thing:

Error   5   The type or namespace name 'MSNWS' does not exist in the namespace 
'MSNPSharp' (are you missing an assembly reference?)

I have no idea where to get this "MSNPSharp.MSNWS" namespace, so I'm stuck. Is 
there a better way to go about all this? Did the conversion wizard mess up 
something? Please help! I'd really like to get this compiled; I'm currently 
stuck with a really old version of MSNPSharp and am running into bugs that I'm 
hoping are fixed with the new version.

Original issue reported on code.google.com by not...@gmail.com on 2 Dec 2010 at 11:39

[GoogleCodeExporter]

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

[GoogleCodeExporter]

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

[GoogleCodeExporter]

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

[GoogleCodeExporter]

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

[GoogleCodeExporter]

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

[GoogleCodeExporter]

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

[GoogleCodeExporter]

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

[GoogleCodeExporter]

vs2005

Original comment by freezing...@gmail.com on 3 Dec 2010 at 12:32

[GoogleCodeExporter]

Please check out svn and try again. It should work.

Original comment by hepha...@gmail.com on 3 Dec 2010 at 8:34

• Changed state: Fixed
• Added labels: Milestone-Release3.1.0

[GoogleCodeExporter]

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

[GoogleCodeExporter]

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

[GoogleCodeExporter]

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

[GoogleCodeExporter]

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

[GoogleCodeExporter]

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