Entries:
Comments:
Posts:

Loading User Information from Channel 9

Something went wrong getting user information from Channel 9

Latest Achievement:

Loading User Information from MSDN

Something went wrong getting user information from MSDN

Visual Studio Achievements

Latest Achievement:

Loading Visual Studio Achievements

Something went wrong getting the Visual Studio Achievements

Comments

Santosh Benjamin santosh_b Benjy
  • endpoint.tv - Making of The Lab - Intro to WF4

    Ron, Thanks. Very informative video. This is a must watch for anyone getting into Feature Builder. I shall definitely be using your word templates for my own feature extensions.

  • endpoint.tv - Meet SO-Aware (Part 1)

    This is a brilliant tool. I really like the way the Service Hosts can dynamically retrieve configuration info using OData. This will definitely simplify configuration management. Looking forward to the other episodes.

  • Workflow TV - WF4 Designer in the Browser

    Very nice. I liked the suggestion of sending the XAML to the server for server-side execution.

    cheers

    benjy

  • 10-4 Episode 26: Creating Extensible Applications with the Managed Extensibility Framework

    Spring is an IoC container while MEF is for plugins. An IoC is used when you know your dependencies at design time and typically deals with "one" dependency (for that area of the app) while MEF deals with many.

     

    For example, with IoC, at design/debug time you may inject a simple console logger for your app or even a mock logger while at production/runtime you will replace it with a proper logger that writes to a file or database but with MEF at runtime you are looking to discover "all loggers" that are available and call them (of course you can just pick up a single logger using the catalog) so your output can be piped to many.

     

    You could use MEF to wire dependencies like an IoC but it is not meant for or optimized for such behavior. MEF also has advantages with the way stuff is exported and imported in that it is not tied to types which means that your app can be opened up to plugins written in dynamically typed languages.

     

    HTH,

    Benjy

  • How We Do It: Building the Visual Studio Product Line

    I think the book referrned to is : The Build Master: Microsoft's Software Configuration Management Best Practices 

    Cheers,

    benjy

  • 10-4 Episode 15: Model-First Development with the Entity Framework 4.0

    .NET Framework 3.0 was released before the VS23008 IDE. Some extensions were added to VS2005 for WCF and WF but you could always use notepad Smiley

  • 10-4 Episode 7: No More Planning Black Box

    I had this issue with missing episodes too. Basically if you look at the Tags page : http://channel9.msdn.com/tags/10-4/  (with the thumbnails/icons view, then Episodes 6 and 12 are not there, but if you look at the list on the shows page : http://channel9.msdn.com/shows/10-4/  then you can see them  Scared

  • 10 mest användbara orchestration patterns - del 1 av 2

    Excellent video and a great explanation of the importance of the message box and about convoys. Looking forward to the second part.
  • Infosys Blueprints Screencast

    Hi,
    The plans for the mapping wizard sound interesting. Just one thing to be careful of, IMO you would need to store what the user entered the first time somewhere because if things change, especially in complex mappings, the user wouldnt want to go through all the steps again from the beginning. The Service Factory Modeling Edition with its targeted /selective updates was definitely superior to the ASMX edition where we had to re-step through the wizard from the beginning.

    I'll watch this space. Keep up the great work.

    Cheers
    Benjy
  • Infosys Blueprints Screencast

    Very interesting video. Infosys has done a nice job in demonstrating the use of Blueprints and the amount of stuff generated without resorting to manual plumbing code is very nice.

    The one issue I had with the implementation of the solution was the generation of WCF wrappers directly from the DAL classes. Farukh mentions that mapping classes will also be generated to map the service entities to data entities and vice versa, but this seems rather pointless when you have already generated the service entitites from the data (unless you are just putting in a placeholder to handle maps if the service entities change in future. But in general, this pattern is only good for 'data interfaces' (ie) vanilla wrappers over the data entities. For more 'business' oriented services, the messages tend to have a flatter schema rather than the deep inheritance trees that a domain model might generally use. The contracts in turn could be very different from the business entities so a full fledged translation is important.

    I think a better approach would have been to have a separate model for the service contracts and data contracts like the P&P Service Factory and then show how a mapping cartridge could be built to map the two.

    Speaking of models, I would like to know how this implementation handles changes in the contracts. Do you regenerate the entire code base (like the first ASMX version of the Service Factory) or can you update only portions? Would be cool to see another video on this Infosys factory to see how updates and changes to entities/contracts are handled.

    Debates on patterns aside, this is still good work.

    Cheers
    Benjy