Peer Channel Team Blog : Random Peer Channel Tips

Tip: Automatically deploying P2P (PNRP) components on XPSP2

peerchan — Thu, 04 Jan 2007 02:58:00 GMT

Scenario: Setting up PNRP/P2P Networking components on XPSP2

Tip:

There is a command line option of installing windows components that we sometimes use (Please note that this is a general way of installing windows components by command line and is not exclusive to the P2P components- I would strongly advise you to test this first before using the solution in a commercial application deployment solution- it works fine for some of our automated tests so as far as I know it works well):

1. Save the following text as a .txt file locally to %SystemDrive%

[Components]
Netoc=on
[NetOptionalComponents]
P2P=1

2. Run the following command to install IPv6 on the machine (required for P2P):

netsh int ipv6 install

3. Now execute the following command to install the P2P Networking Pack:

%systemroot%\system32\Sysocmgr.exe /i:%systemroot%\inf\sysoc.inf /u:%SystemDrive%\EnablePnrpOnXPSP2.txt /q /w

This is the best I have so far as automated deployment of the Advanced Networking pack (aka P2P pack) is concerned on Windows XP.

I haven't tried it myself, but I am guessing this could be integrated into the Setup package as well.

Note: Feel free to share your feedback and whether you are able to get this to work for your application deployment.

-Shalini

Tip: Peer Channel diagnostics using WCF Tracing/Message Logging

peerchan — Mon, 02 Oct 2006 08:33:00 GMT

Scenario: You want to enable WCF tracing for troubleshooting purposes

Tip: You need to use the App.config file to enable WCF Tracing and Message Logging. The following (either 1 or 2 depending on your scenario) will end up generating a .svclog file named MyAppTraceFile.svclog. This file is viewable using the ServiceTraceViewer.exe tool (shipped with the Windows SDK - maybe found in the Tools directory)

1. If you already have an App.config file that your application uses, modify it as follows:

a. In the <system.serviceModel> section in your file, add the following tag:

<messageLogging maxMessagesToLog="30000"

logEntireMessage="true"

logMessagesAtServiceLevel="true"

logMalformedMessages="true"

logMessagesAtTransportLevel="true">

</messageLogging>

</diagnostics>

b. Now, add the following additional <system.diagnostics> section anywhere after your <system.serviceModel> ends but within the root <configuration> section.

<system.diagnostics>

</listeners>

</source>

</listeners>

</source>

</sources>

</sharedListeners>

</system.diagnostics>

2. If you have configured PeerChannel imperatively in code and don’t have a config file that your App uses, simply create one with the following contents:

<system.serviceModel>

<messageLogging maxMessagesToLog="30000"

logEntireMessage="true"

logMessagesAtServiceLevel="true"

logMalformedMessages="true"

logMessagesAtTransportLevel="true">

</messageLogging>

</diagnostics>

</system.serviceModel>

<system.diagnostics>

</listeners>

</source>

</listeners>

</source>

</sources>

</sharedListeners>

</system.diagnostics>

</configuration>

-Shalini.

Tip: Peer Channel and custom Message contracts

peerchan — Mon, 02 Oct 2006 07:40:00 GMT

Scenario: Say, we have defined a custom Message contract to use in our Application like so:

public enum SendMessageType

{

Send,

Ack,

Resend,

}

[MessageContract(IsWrapped=false)]

public class TestMessage

{

[MessageHeader]

public SendMessageType Type;

[MessageHeader]

public int MessageId;

}

[ServiceContract(CallbackContract = typeof(IMessage))]

public interface IMessage

{

[OperationContract(IsOneWay = true)]

void SendMessage(TestMessage message);

}

Symptom: Messages are not being received by the peers and the client channels are being torn down due to FaultException when sending messages.

Tip: Make sure that the TestMessage Message Contract above actually has an explicit constructor defined as well. So the modified TestMessage Message contract looks like:

[MessageContract(IsWrapped=false)]

public class TestMessage

{

[MessageHeader]

public SendMessageType Type;

[MessageHeader]

public int MessageId;

public TestMessage()

{

}

-Shalini.

Tip: Sending large Peer Channel messages and NetPeerTcpBinding.ReaderQuotas

peerchan — Mon, 02 Oct 2006 05:48:00 GMT

Scenario: Trying to send large WCF messages over the Peer Channel

Symptom: Peers do not receive messages even though NetPeerTcpBinding.MaxReceivedMessageSize is appropriately configured.

Tip: Set the NetPeerTcpBinding.ReaderQuota field values to integer.MaxValue like so:

<readerQuotas

maxDepth="2147483647"

maxStringContentLength="2147483647"

maxArrayLength="2147483647"

maxBytesPerRead="2147483647"

maxNameTableCharCount="2147483647" />

</binding>

</netPeerTcpBinding>

-Shalini.