Articles Written by Jeffrey Juday

Creating OData Entries in WCF Data Services

To fully exploit Open Data Protocol (OData) with WCF Data Services there are classes and interfaces a .NET app must instantiate or implement. Using a sample WCF Data Services application, this article explains how to implement data creation on an OData Endpoint.

Navigating OData and WCF Data Services

Understanding OData conventions are important to building an OData client and testing an OData Endpoint. Of all the OData conventions the most important convention a WCF Data Services developer must understand are the OData URI conventions. This article explains how OData URI conventions map to code living inside of WCF Data Services.

WCF Data Services Providers

OData's simplicity and common underlying Web standards have made it a popular Data protocol in the Microsoft stack. WCF Data Services includes several Providers that surface OData from .NET classes.

SpinWait.SpinUntil and the Task Parallel Library

Often blocking and checking is combined with some sort of timeout. SpinUntil, a static method on the SpinWait structure, combines blocking, waiting, and timeouts. New in the .NET Framework 4.0, SpinUntil simplifies many different scenarios involving the Task Parallel Library (TPL). Jeffery Juday shares some common recipes employing SpinUntil alongside TPL.

Top White Papers and Webcasts

  • Instead of only managing projects organizations do need to manage value! "Doing the right things" and "doing things right" are the essential ingredients for successful software and systems delivery. Unfortunately, with distributed delivery spanning multiple disciplines, geographies and time zones, many organizations struggle with teams working in silos, broken lines of communication, lack of collaboration, inadequate traceability, and poor project visibility. This often results in organizations "doing the …

  • With JRebel, developers get to see their code changes immediately, fine-tune their code with incremental changes, debug, explore and deploy their code with ease (both locally and remotely), and ultimately spend more time coding instead of waiting for the dreaded application redeploy to finish. Every time a developer tests a code change it takes minutes to build and deploy the application. JRebel keeps the app server running at all times, so testing is instantaneous and interactive.

Most Popular Programming Stories

More for Developers

Latest Developer Headlines

RSS Feeds