Call Us:  (877) 513-3113

E-Mail:  info@tellagostudios.com

What We're Talking About

Some Thoughts on Employer Employee Relationships

People are a key element of the success or failure of a software startup.


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.


Telesharp - An Application Repository for .NET applications

A year ago, we released SO-Aware as our first product in Tellago Studios. SO-Aware represented a new way to manage web services and all the related artifacts like configuration, tests or monitoring data in the Microsoft stack.


SO-Aware and the Microsoft Technology Stack

Since the launch of SO-Aware, we’ve been pleasantly surprised by the number of times other Microsoft partners in the middleware & integration space have positioned our product together with the rest of Microsoft’s Service Oriented (SO) technology stack when responding to competitive engagements against traditional J2EEvendors such as Oracle, IBM, SoftwareAG or Tibco.


Extending the SO-Aware repository with custom metadata

One of the main features that SO-Aware provides is the central repository for storing service artifacts (WSLD, schemas, bindings) and configuration that any organization generates. This central repository is completely exposed as an OData service that third party applications and tools can easily consume using Http.


Making WCF load testing so simple a caveman can do it

 

As I mentioned in previous posts, during the development of the SO-Aware Test Workbench we literally obsessed about making performance testing as simple as it gets. One of the aspects that make performance testing so simple with the SO-Aware Test Workbench is that it leverages SO-Aware’s WCF centralized configuration capabilities.


Overstanding the SO-Aware Test Workbench Test Types (part 1: Unit & Simple Load Testing)

Introduction

SO-Aware, allows you to create unit tests for WCF SOAP, and WCF REST based web services. These tests can be executed using the standard web based user interface that SO-Aware provides. The tests can also be executed using a PowerShell script. There is also a automated windows service that runs that can schedule a test to run every so often. The results of these tests are stored inside the SO-Aware repository.


Syndicate content