Friday, May 8, 2009

Quote about understanding

Tell me and I will forget
Show me and I will remember
Involve me and I will understand

- Confucius -

I found this quote on the blog of the problem solver.

(Solution) "Secure channel cannot be opened because security negotiation" (Geneva)

Today, I was doing some tests with the Geneva (Beta) Framework, again.

It took me some time to find the source of the following errors/exceptions my test applications where throwing:

  • Secure channel cannot be opened because security negotiation with the remote endpoint has failed. This may be due to absent or incorrectly specified EndpointIdentity in the EndpointAddress used to create the channel. Please verify the EndpointIdentity specified or implied by the EndpointAddress correctly identifies the remote endpoint.
  • The message could not be processed. This is most likely because the action '' is incorrect or because the message contains an invalid or expired security context token or because there is a mismatch between bindings. The security context token would be invalid if the service aborted the channel due to inactivity. To prevent the service from aborting idle sessions prematurely increase the Receive timeout on the service endpoint's binding.

The problem was that my testclient was using a different bindingtype then my test Security Token Service.

For more information about what type of binding to favour, see:

Perhaps this is usefull for you.

Monday, May 4, 2009

Event ID 1023: Fatal Execution Engine Error (Solved)

For some time I have been trying to solve this error that crashed my Visual Studio 2008 when ever I wannted to "Choose Items" for the Toolbox.

What worked for me was to uninstall Visual Studio 2008 PowerCommands!

Event Type: ErrorEvent
Source: .NET RuntimeEvent
Category: NoneEvent
ID: 1023
Date: 2-5-2009Time: 16:54:41
User: N/A
Computer: TEAMSUIT2008
Description:.NET Runtime version 2.0.50727.3082 - Fatal Execution Engine Error (7A035FC0) (80131506)

Complemeting FxCop with StyleCop!

I guess we all know FxCop by Now. But do you know about StyleCop?

StyleCop is a Source Code Style and Consistency Tool.

... FxCop performs its analysis on compiled binaries, while StyleCop analyzes the source code directly. For this reason, FxCop focuses more on the design of the code, while StyleCop focuses on layout, readability and documentation. Most of that information is stripped away during the compilation process, and thus cannot be analyzed by FxCop. ....


Happy Styling!