Posts Tagged ‘$.fn’

Top 10 Takeaways from DevConnections Day Three

November 12, 2009 1 comment

November 10th 2009 | Jimmy Bosse

Top 10 Takeaways from DevConnections Day Three

Wednesday seemed to go at a breakneck pace. The sessions I attended on Tuesday were all given by Microsoft employees and only one
presenter used VS 2008. These presentations were all about how I was going to get things done when VS 2010 launches (allegedly in March 2010.)
The sessions I attended on Wednesday had more to do with how to get things done, today (or when we get home from the conference), and everyone was using VS 2008.

My biggest complaint about DevConnections is there are too many good sessions. There were several sessions that I wanted to attend that were in conflict with one another.
The sessions I managed to settle on were:

  • What ASP.NET Developers Should Know About JavaScript by Scott Allen
  • Introduction to jQuery with ASP.NET by Rick Strahl
  • WCF the Manual way… the Right way by Miguel Castro
  • .NET Rocks!- SQL Server Reporting Services by Carl Franklin & Richard Campbell with guest Paul Litwin
  • Refactoring Today’s .NET Code to Good Design Practices by Dino Esposito

And so, without further ado, the top 10 takeaways from day three:

  1. Get the FireBug plug-in.

    It seems like every presenter uses FireBug in Firefox, even the Microsoft team. It is very useful when working with your web UI. Go get it if you haven’t already.

  2. Use $.fn to create your own jQuery plug-ins.

    jQuery is such an amazingly fluent framework and so easy to extend to your own needs.

  3. You can create pseudo namespaces in JavaScript.

    For example, if you want to create a Point object in a Geometry namespace:
    var Geometry = {};
    Geometry.Point = function(x, y) {…

  4. Use “JavaScript-Behind” for your pages.

    It is easy to inline your JavaScript, but for anything other than the most trivial tasks you should move your JavaScript to .js files.

  5. Don’t make any new .asmx pages.

    Use WCF. Microsoft no longer supports WSE (.asmx) web services. Your existing services will work, but don’t make any new ones.

  6. Write your own WCF services without the project templates.

    Although the WCF project types are helpful to get you up and running quickly, they are full of stuff you don’t need and can make your job harder in the long run. Miguel Castro has a good article on this topic here.

  7. Microsoft has merged the Matrix , Table, and List regions into a Tablix.

    A silly name but a very useful change. How many times have you wanted to add a static column to a Matrix or otherwise mix a table with a Matrix? Many times, I know. Now it is possible with the Tablix.

  8. The Code window in Reporting Services still sucks.

    Sorry, I wish I had better news.

  9. Single Responsibility Principle is a Principle, not a Law.

    You are striving to give a class one reason to change, not extract every line of code into its own class. A Principle means that you aim to code towards a goal but have to also balance that with the needs and design of your system and the problems you are trying to solve.
    Shameless Plug: Dino Esposito, IDesign software architect and author,  asked me about our Single Responsibility blog post by my colleague David Cooskey.

  10. Service Locator is good. Dependency Injection is better.

    With service locators, the “injection” of the dependency is being done from within the class itself. This makes it hard to identify
    these dependencies from outside the class. With dependency injection, these dependencies are easy to identify.

    Today promises to be another flurry of fantastic sessions. Check back tomorrow for more highlights from DevConnections.

    Jimmy Bosse is a Team Lead at Thycotic Software, an agile software services and product development company based in Washington DC. Secret Server is our flagship password management software product. On Twitter? Follow Jimmy