RE: P2P SDK and .Net

[Rhett Gong [MSFT]]

Hello John,
So far, there is not corresponding .NET wrapper for P2P SDK. so if you are porting your code to .NET, you may need to rewrite your code from scratch. I am not very sure
what kind of porting you are trying to do. IMO, if you just want .NET UI or something else, why not re-use your code, eg. encapsulating current implementation as a COM
object and use the interfaces exposed through COM Interop in your .NET application? I think it should save a lot of time for you.

In addition, here is an aritcle on Microsoft Win32 to Microsoft .NET Framework API Map, I think it maybe helpful to you and you can find it at:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dndotnet/html/win32map.asp

Thanks,
Rhett Gong [MSFT]
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
http://support.microsoft.com/default.aspx?scid=/servicedesks/msdn/nospam.asp&SD=msdn

This posting is provided "AS IS" with no warranties and confers no rights.

[John A]

My biggest problem is writting in C/C++ due to the fact that most of my
working career over the last 3 years has been spent using .Net entirely. I
guess I will just have to bite the bullet and begin again in C/C++. My
language of choice for a number of years.

--
Thank you,
John

[Rhett Gong [MSFT]]

|>My biggest problem is writting in C/C++ due to the fact that most of my
|>working career over the last 3 years has been spent using .Net entirely. I
|>guess I will just have to bite the bullet and begin again in C/C++. My
|>language of choice for a number of years.

It does not pain so much. And when you get familiar with C/C++, you will find it gives more controls for system programming. We also have managed newsgroups for
questions on Visual C++, when you meet any questions, you can post there.
microsoft.public.vc.language

In addition, I would like to suggest you keep an eye on C++/CLI. If you have read specification for C++/CLI, it would be a best choice in this scenario. :)

[Horton [MSFT]@discussions.microsoft.com Noah Horton [MSFT]]

I am with the P2P team that produced these APIs. We currently do not have
any managed versions of these APIs available, but we are investigating making
such APIs available. It is helpful to us to get community feedback like this
that such APIs are desired.

In the meantime, there is a good set of wrappers available at
http://www.thoughtpost.com that you might try.

-Noah

This posting is provided "AS IS" with no warranties and confers no rights.

[Arkady Frenkel]

Be carefull , you are in the forest ( NG ) where almost all of us those
dinosaurs :).
A lot of MSFT stacks have no manage equivalents , like UPnP I work with :(.
BTW the way I found very useful is if you have C++ Com module you can just
in a second with tlbimp.exe from .Net framework bin make converter dll for
managed code

Arkady

"CSharpDev" <CSha...@discussions.microsoft.com> wrote in message
news:21FEDED1-CF00-4813...@microsoft.com...

> "Noah Horton [MSFT]" wrote:
>
>> I am with the P2P team that produced these APIs. We currently do not
>> have
>> any managed versions of these APIs available, but we are investigating
>> making
>> such APIs available. It is helpful to us to get community feedback like
>> this
>> that such APIs are desired.
>

> ARE YOU KIDDING?!?!?!
> They are not just "desired". It's a shame Microsoft hasn't done that yet!
> What's the point of promoting C# as a primary language for .NET, if C#
> developers are unable to do what's trivial for C++ "dinosaurs"?

[m]

BTW: you can p/invoke anything in .NET

"Arkady Frenkel" <ark...@hotmailxdotx.com> wrote in message
news:eHyEFblT...@TK2MSFTNGP14.phx.gbl...

[Simon Wong [MS]]

We are currently considering exposing a Peer-to-Peer namespace in a future
version of the System.Net namespace. If anyone is interested in such a
namespace, please do email the System.Net team at
ncl...@microsoft.com.dontspam (remove the .dontspam) and let us know if you
are interested in such an API, how you would use it, and what scenarios it
should support.

Thanks for your posting and interest on P2P SDK.

--
Please do not send email directly to this alias. This alias is for newsgroup
purposes only.

This posting is provided "AS IS" with no warranties, and confers no rights.

"CSharpDev" <CSha...@discussions.microsoft.com> wrote in message
news:21FEDED1-CF00-4813...@microsoft.com...
> "Noah Horton [MSFT]" wrote:
>

>> I am with the P2P team that produced these APIs. We currently do not
>> have
>> any managed versions of these APIs available, but we are investigating
>> making
>> such APIs available. It is helpful to us to get community feedback like
>> this
>> that such APIs are desired.
>

[CSharpDev]

That was a joke that went wrong. I didn't mean to insult anyone. I apologize
if I did. I respect those proficient in pre-.NET languages, and I believe
they (== you, Sir) can do way more than dummies like me spoiled by
lightning-fast CPUs and countless gigabites of memory.

The problem with tlbimp is that even though those resulting dlls can be used
in a C# app, essentially it's still the same good old C++...

I think that "old" p2p is going to become extinct pretty soon, after WCF
becomes the basis for most of the new distributed apps.

Thank you for your reply.

Yours sincerely,
Dmitriy

[Arkady Frenkel]

Hi!

"CSharpDev" <CSha...@discussions.microsoft.com> wrote in message

news:223BD597-E0F5-4657...@microsoft.com...

> That was a joke that went wrong. I didn't mean to insult anyone. I
> apologize
> if I did. I respect those proficient in pre-.NET languages, and I believe
> they (== you, Sir) can do way more than dummies like me spoiled by
> lightning-fast CPUs and countless gigabites of memory.
>

No problem , go with it, especially if you have "lightning-fast CPUs and
countless gigabites of memory" :)

> The problem with tlbimp is that even though those resulting dlls can be
> used
> in a C# app, essentially it's still the same good old C++...
>

You'll be with C/C++ a log time because C# built with it ,so any entrance to
internals will cause using of that "dinosaur" :)

> I think that "old" p2p is going to become extinct pretty soon, after WCF
> becomes the basis for most of the new distributed apps.
>

R U sure ? Exactly as previous : winsock is base for WCF ( a.k.a "Indigo" )
so that will be with us pretty long time IMHO :)
Arkady

[Scherbina Vladimir]

When all turns to "anything" then I would like to tell that there're some
issues(problems) concerning invoking API that accepts complex structures as
params

--
Vladimir
http://spaces.msn.com/vladimir-scherbina/

"m" <m@b.c> wrote in message news:Od55llsT...@TK2MSFTNGP11.phx.gbl...

[m]

Yes there are problems. But the only one that beet me was calling a .NET
function from C code in a thread that was not created by the CLR (the CLR
corrupted the stack or returning).

"Scherbina Vladimir" <vladimir....@XgmailY.comZ> wrote in message
news:OBDEwEnU...@TK2MSFTNGP09.phx.gbl...