2009 - January/February
The Jan/Feb 09 issue covers .NET Productivity Tools.
Note: If you recently signed up for a subscription and are now creating a new account, please make sure to use the same email address.
Note: If you recently signed up for a subscription and are now creating a new account, please make sure to use the same email address.
The Jan/Feb 09 issue covers .NET Productivity Tools.
At the JAOO conference in Aarhus, Denmark this year, domain specific languages came up in virtually every conversation. Every keynote mentioned them, a lot of sessions discussed them (including a pre-conference workshop by Martin Fowler and myself), and you could hear “DSL” in most of the hallway conversations. Why this, and why now?
jQuery is a small JavaScript library that makes development of HTML-based client JavaScript drastically easier. With client logic getting ever more complex and browsers still diverging in features and implementation of features, jQuery and other client libraries provide much needed normalization when working with JavaScript and the HTML DOM.
All applications are dependent on data in some form and most developers find themselves writing reams of data access code.Microsoft has been building databinding frameworks for years. Each one promises to solve our databinding woes forever. We’re still waiting for the perfect one.In the Nov/Dec 2008 issue of CoDe Magazine you were exposed to programmatically controlling data binding mechanisms of WPF. Along with a programmatic interface, WPF also provides a declarative databining interface. This second article will introduce you to using the declarative data binding mechanisms contained in WPF.
No, the title isn’t a misprint-this installment of the Baker’s Dozen will visit both sides of the planet. These days, many .NET user group meetings focus on database and business intelligence topics as well as hardcore .NET content. Over the last several months, I’ve spent roughly half my time modifying my own development framework for WCF. The result is some basic but functional factory classes I’d like to share. The other half of the time, I’ve been looking at different capabilities in the SQL Server 2005 and 2008 Business Intelligence stack, and solving requirements that BI developers often face. So rather than pick one side and make the other side wait two months, I decided to combine the two.
I read somewhere that nearly 80% of all data has some location-related aspect to it. Common business questions in data include: Where do we ship these orders? Where are flood plains located and what rainfall amount are problematic for them? Where are vendors and/or customers located? What delivery route should we use? Can we track using GPS? Where are voting districts located? Where are the best hospitals located? Where are the sales regions that produce the most revenue? And so on. It is highly likely that a significant portion of the data you work with has a location-related aspect to it. Visually presenting this information could lead to better management decisions or possibly uncovering trends that were not evident before. A good application can present this information using a location-oriented approach. That is where Microsoft Virtual Earth fits in.