Browse by Tags

• .NET
• .NET Framework 3/WinFX
• Agile
• Agile and Extreme Programming
• Agile Development
• Avalon
• C#
• CLR
• Data
• Extreme Programming
• LINQ
• LINQ and OR/M
• NANT
• NET Framework 3
• New and Notable
• OR/M
• SOA
• Software Architecture
• TDD
• WCF
• WCF/Indigo
• Windows Communication Foundation
• Windows Presentation Foundation
• WPF

• CTP and Diagnosing WCF, CAB and other Exceptions

  In the last post , I talked about how we had reached Iteration 33 and gone to CTP with a large International bank. I alluded to some problems. Of course, one of the CTP's main purposes was to find problems and learn from them. We ended up having a variety of problems. There were initial problems in the Click-Once deployment. We built a WIX MSI (great work done by mostly Aaron & Brad) that installs our database scipts, sets up our config files, installs our WCF Services and sets up the service for the Click-Once Deployment of our client. This is installed server-side. The Click-Once deployment failed, our excellent person on the scene went to an xcopy deployment, and as you will see later, that caused some funly issues, although far from being the only and main cause. (Note: I have just split the post into two and the next part will talk about our solutions with the Service Factory, Exception Management and Logging Blocks). The gist of it is that our client never came up (-. Trying to find out why proved to be a two-day somewhat intense struggle for Steve and I who were the main leads dealing with our man in Paris. The first major realization is that all of us on the whole team had done a real crappy job dealing with Indigo Service exceptions not catching the variety of exceptions that could come up including the service not being there. We did have a Global Exception Handler and had a custom dialog with the nice error message. While realizing our shortfalls, the immediate mystery was why the Global Exception Handler did not catch and show these particular exceptions. Left to their own devices, these exceptions would bubble up and evetually show themselves as CAB exceptions. Our global handler handled the Application.ThreadException. What we forgot was to handle the AppDomain.UnhandledException event. It would be something like this: Application.ThreadException += new ThreadExceptionEventHandler(Application_ThreadException); AppDomain.CurrentDomain.UnhandledException Read More... Posted Saturday, August 05, 2006 8:09 AM from Sam Gentile : WCF/Indigo | 0 Comments Filed under: WCF/Indigo, Software Architecture, SOA, Windows Communication Foundation, WCF, Agile, Agile and Extreme Programming, Smart Clients, WinForms and WPF, Microsoft, .NET Framework 3/WinFX, TDD, Extreme Programming, Agile Development, NET Framework 3

• New and Notable 103

  Happy Father's Day to all other Fathers! My son made me breakfast and in a letter said "I was smarter than Einstein" and "are you sure you didn't invent E = mc2 and Albert E. copied you?" -)) Data/ORM/ADO.NET 3 Ayende has been reading the docs for the ADO.Net Entities Framework and Next-Generation Data Access - June 2006 : and comes back far from impressed. Some choice comments: The problem is that I don't like this solution. The framework should be flexible enough that I could plug in at all the important points and replace the functionality with my custom one. Using two ways to acess the data has a big "Don't Do Unless You Know What You Are Doing And Have Fasted For Three Days" sign over it with red blinking lights. Oh joy! Three ORM frameworks. Linq to SQL, Linq to Dataset, Linq to Entities. This is a new record. They managed to piss me off on the very first page. The code example that they give as the desired state doesn't even make sense. Sigh. It looks like this is much about providing a mapping layer between the database and the logical model, and getting un-typed results back. I'm not excited about this at all. This is where they are putting quite a bit of emphasis. Given that they create a new language to work with the data, why not make it compatible with the way Linq work and use from-select-where ? WCF/SOA/WSE/WinFX Clemens has recorded a new episode of MSDN TV on WCF bindings Clemens weighs in on the whole WinFX vs. .NET Framework 3.0 naming mess The Indigo group has finally released the source code for the infamous Magic8Ball service C# Variance and Generalized Constraints for C# Generics . A paper pointed to by this LtU thread. Also see Discussion of previous C# GADT paper on LtU. WPF/Avalon Check out the new WPF Blog site and the new WPF section of the new .NET Framework 3.0 site! [via Mike Taulty ] Also see Mike's WPF: Adventures in Virtualiza tion Technorati Tags: CLR , .NET , Data , OR/M , NANT , WPF , Avalon , Windows Presentation Foundation , New Read More... Posted Sunday, June 18, 2006 10:45 AM from Sam Gentile : WCF/Indigo | 0 Comments Filed under: .NET, CLR, WCF/Indigo, SOA, LINQ and OR/M, New and Notable, Data, Windows Communication Foundation, WCF, LINQ, OR/M, Smart Clients, WinForms and WPF, Microsoft, Avalon, WPF, C#, NANT, Windows Presentation Foundation