Call Us:  (877) 513-3113

E-Mail:  info@tellagostudios.com

tellago studios

Fixing .NET Configuration Hell with TeleSharp: Authoring Configuration Files

The configuration authoring experience remains one of the main challenges of .NET applications. Every time we need to create a new configuration files, we find ourselves going to MSDN or similar websites and trying to figure out the structure of different configuration sections and the sad thing is that we 


Fixing .NET configuration hell with TeleSharp: Versioning configuration sections

Story:Bob is an IT Professional (ITPro) responsible for maintaining dozens of enterprise .NET applications. One day, Bob gets a call informing him that one of the applications he is responsible for have stopped working after some changes in the configuration were applied. After hours troubleshooting the application without any positive results, Bob decides to involve the developers who built the new version of the applications.


Tellago Studios forums are here!

 

Now you can give us feedback about our product directly on our website using our new forums


Fixing .NET configuration hell with TeleSharp: Reusing configuration sections

Reusability, or the lack of it, is one of the main problems with the .NET configuration experience. How many times do we find ourselves creating the same configuration sections over and over again as part of our .NET applications? And then when those configuration settings change we have to go change it on 20 different places.


Why .NET configuration management sucks and what can you do about it

Configuration management is one of the biggest problems of enterprise .NET applications. Since the first release of the .NET framework, configuration has been the main mechanism used by developers to model aspects of applications in a declarative way.

So what’s wrong with .NET configuration?

Reusability

Do you find yourself copying the same configurations sections over and over and over again to the different applications in your enterprise? You are not along.


Load Testing your WCF service in two clicks

A few months back I was talking to a VP of Architecture from one of our customers about service testing practices and he expressed a very blunt viewpoint about load testing: “Developers don’t load test their web services because it's to F…. difficult”.


How fast are my services? Comparing basicHttpBinding and ws2007HttpBinding using the SO-Aware Test Workbench

When working on real world WCF solutions, we become pretty aware of the performance implications of the binding and behavior configuration of WCF services. However, whether it’s a known fact the different binding and behavior configurations have direct reflections on the performance of WCF services, developers often struggle to figure out the real performance behavior of the services. We can attribute this to the lack of tools for correctly testing the performance characteristics of WCF services under different load profiles.


Using a service registry that doesn’t suck part II: Dear registry, do you have to be a message broker?

 

Continuing our series of posts about service registry patterns that suck, we decided to address one of the most common techniques that Service Oriented (SOA) governance tools use to enforce policies.


Using a service registry that doesn’t suck part I: UDDI is dead

This is the first of a series of posts on which I am hoping to detail some of the most common SOA governance scenarios in the real world, their challenges and the approach we’ve taken to address them in SO-Aware. This series does not intend to be a marketing pitch about SO-Aware. Instead, I would like to use this to foment an honest dialog between SOA governance technologists.

For the starting post I decided to focus on the aspect that was once considered the keystone of SOA governance: service discovery

Scenario


Syndicate content