December 2008 Entries
Just wandering around, reading whatever I come across.
Using Callback Contracts in WCF for Asynchronous Publish/Subscribe Event-Style Communication
http://dotnetaddict.dotnetdevelopersjournal.com/wcf_alarmclock.htm
How to Write High-Performance C# Code (Kind of old but still useful.)
http://dotnet.sys-con.com/node/46342
WOA for the Enterprise : Web Oriented Architecture (worth a read) SOA + WWW + REST
http://dotnet.sys-con.com/node/771173
What is Cloud Computing
http://www.youtube.com/v/6PNuQHUiV3Q
http://www.youtube.com/watch?v=QJncFirhjPg
posted @ Saturday, December 13, 2008 11:29 AM |
I saw this over on TechRepublic and though it was good for a response.
Sanity check: 10 dirty little secrets you should know about working in IT
It includes many comments with more dirty secrets. I'm interested in finding out what else people have to say about this.
Here's a few things from the training part of IT which I'm very familiar with:
1. Some tech training managers will encourage a trainer to lie about their experience. Let's face it, experienced trainers are hard to find, and harder to compensate for what the industry pays out to training companies. Let's just say, you...
posted @ Thursday, December 04, 2008 11:57 AM |
It's important to first understand what defines a service contract. Basically a service contract defines the group of operations in a service, the operation's signatures and message datatypes. It also defines the location of the operations and the specific protocols and serialization formats that support communication with the service.
In WCF, we define a service contracts with method and class attributes. The following is a simple service with it's associated attributes:
// Step 1 Import the necessary namespaceusing System;using System.ServiceModel;namespace myHoakyService{
//Step 2 Use the ServiceContract attribute to //identify a class or interface that defines a ...
posted @ Wednesday, December 03, 2008 8:04 AM |
So I was working on this Windows Communication Foundation tutorial. The tutorial came as a pre-existing solution that you would update via WCF tasks. I'd successfully done the C# version after many attempts. Most of my problems stemmed from typos during the tutorial. Then came the VB version of the tutorial. Well, there actually wasn't much VB or C# in the labs so I can't use the excuse that I work mostly in C#. That sucks.
So what was the error? I kept running the lab and got an error that the Internet endpoint did not exist. I'd run it...
posted @ Tuesday, December 02, 2008 9:17 PM |
What we're looking at is at it's basic level a Service Oriented Architecture. It basically allows you to write services for other applications to use. It combines COM, COM+, and MSMQ, .NET Remoting, ASMX, System.Messaging, and .NET Enterprise Services. The basic concepts of interoperability, performance, transactional support as well as security differ from client application to client application. WCF strives to meet the needs of different client applications.
Basically a WCF client and a WCF service use the WCF which addresses communication challenges between a service and a diverse range of client requirements. Microsoft identifies the following as the most important aspects...
posted @ Monday, December 01, 2008 12:25 PM |
The more I learn, the more I know I don't know. As an MCT, it's my job to continually update my skills. To that end, I've been delving into things that aren't covered in the courses I teach. Things like Unit Testing.
What's A Unit Test?
With Visual Studio 2005 and 2008, you get the ability in some versions like Team System to create a Test Project to do Unit Testing. Before I start talking about creating a unit test, let's review the basics. A unit test verifies that a function actually performs it's duties. Now, there are black box and white...
posted @ Monday, December 01, 2008 12:50 AM |