A great video worth sharing

from Killers

This is probably a bit old, but still worth sharing

Article on WCF configuration

Based on some of my significant recent deep dives into WCF, I have written an article that talks about configuring WCF services.  Here is a link to the article.

http://www.devx.com/dotnet/Article/38407.

More readable version is here

Tim Russert – You will be missed

When i  watch news channels and follow politics there is one name and one channel i always stop at

When Tim Russert is on the show.

Meet the press was such a great show and kept me

focused for an hour or so.

Of all the interviewers i have seen so far he is clearly the best. I had no option when his show was on, but to stop what i was doing and watch his show.When i change channels looking for a news channel, if i saw Tim, i knew what i was watching.

You will be missed Tim. May you rest in peace.

Dr Randy Pausch’s last lecture.

This is a simply amazing video by Dr Randy Pausch. Every minute spent is worth your time. dont miss it.

I wanted to get his book. But found this video instead.

Here is the list of lessons learned

• Loyalty is a two-way street.
• Never give up.
• You get people to help you by telling the truth. Being earnest. I’ll take an earnest person over a hip person every day, because hip is short term. Earnest is long term.
• Apologize when you screw up and focus on other people, not on yourself.
• Get a feedback loop and listen to it. … Anybody can get chewed out. It’s the rare person who says, oh my god, you were right. … When people give you feedback, cherish it and use it.
• Show gratitude.
• Don’t complain. Just work harder.
• Be good at something, it makes you valuable.
• Work hard.
• Find the best in everybody. … No one is all evil. Everybody has a good side; just keep waiting, it will come out.
• And be prepared. Luck is truly where preparation meets opportunity.

I like to move it move it

This song is hilarious from the movie Madagascar.
Love the guy with the indian accent.

WCF MexTCP issue -There is already a listener on IP endpoint 0.0.0.0:portnumber

If you happen to use mex endpoint together with other endpoints in a configuration file for your service, AND if you get error “There is already a listener on IP endpoint”, just remove the port number for the mex end point or if you want you can add the “portSharingEnabled” property in the binding configuration.

portSharingEnabled=”true”

Don’t use

Instead use

You still can WSDL Even if you don’t have port number

The error looks like this:

Service cannot be started. System.ServiceModel.AddressAlreadyInUseException: There is already a listener on IP endpoint 0.0.0.0:8081. Make sure that you are not trying to use this endpoint multiple times in your application and that there are no other applications listening on this endpoint. —> System.Net.Sockets.SocketException: Only one usage of each socket address (protocol/network address/port) is normally permitted

at System.Net.Sockets.Socket.DoBind(EndPoint endPointSnapshot, SocketAddress socketAddress)

at System.Net.Sockets.Socket.Bind(EndPoint localEP)

at System.ServiceModel.Channels.SocketConnectionListener.Listen()

— End of inner exception stack trace —

at System.ServiceModel.Channels.SocketConnectionListener.Listen()

at System.ServiceModel.Channels.BufferedConnectionListener.Listen()

at System.ServiceModel.Channels.ExclusiveTcpTransportManager.OnOpen()

at System.ServiceModel.Channels.TransportManager.Open(TransportChannelListener channelListener)

at System.ServiceModel.Channels….

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Maximum message size quota for incoming messages (65536) has been exceeded.

There are two errors that may be encountered at run time which relate to the amount of data being received by the client application.

1. The maximum message size quota for incoming messages (65536) has been exceeded.

2. Maximum number of items that can be serialized or deserialized in an object graph is ’65536′.

In general, the first error will surface when the total number of bytes that the service is attempting to return exceeds the configuration values (the

default is 65536). To raise the total number of bytes that can be returned, the following changes are required:

In the Binding configuration(s):

<binding name=”YourBindingName”

maxBufferSize=”2147483647″

maxReceivedMessageSize=”2147483647″

…other values…

Note that the values being configured above are the maximums possible. It is advisable to configure only the highest values required. All three values

should be configured to the same values.

The second error (from above) may be encountered after making the first set of changes. The second error is caused by the total number of (.net) objects

being returned exceeding the configured value (default = 65536). This value is set on individual endpoints and is not usually explicitly set in the

configuration file. To increase this value, first create a new (or modify an existing) endpoint behavior.

Then assign this behavior to the endpoint receiving the error.

Note again that the value configured above is the maximum.

Powered by ScribeFire.