Skip to content

Official jQuery 1.3.0, 1.3.1 Visual Studio Intellisense Files

It looks like this weekend while I was at the South Florida Code Camp the jQuery team has posted the official jQuery 1.3.1 Visual Studio intellisense file. You can get it from the jQuery downloads page, or more directly from the jQuery Google Code download page.

The official 1.3.0 documentation was posted this weekend as well and is also available from the downloads link above, or this Google Code download page.

Keep your eyes peeled for a jQuery 1.3.2 release anytime in the next few days as John Resig has mentioned there is still one last 1.3 regression they are working on fixing.

For those interested, the regression has to do with the $(document).ready() function waiting until images are fully loaded in Internet Explorer 6 & 7. The jQuery bug ticket ID is #3988 and here’s a Stack Overflow question in which John Resig talks about the issue in some detail.

  • email
  • DotNetKicks
  • Digg
  • del.icio.us
  • Technorati
  • StumbleUpon
  • LinkedIn
  • Facebook
  • Twitter
  • Google Bookmarks
  • Live

Making ReSharper Play Nice With StyleCop

I’ve been toying with StyleCop more and more as of late and ran into some situations where ReSharper and StyleCop were fighting each other over code formatting issues. Some manual tweaking reduced the problems, but it got me curious. So I did some research and uncovered a wonderful tool, StyleCop for ReSharper.

StyleCop for ReSharper is a ReSharper 4.1 plug-in that allows Microsoft StyleCop to be run as you type, generating real-time syntax highlighting of violations. StyleCop for ReSharper also contains a collection of Quick-Fixes and Code Clean-Up Modules to help you easily fix StyleCop code styling violations.

StyleCop for ReSharper also comes with a ReSharper Code Style Settings File which you can import into ReSharper to make ReSharper’s auto formatting features compliant with StyleCop’s recommendations. If you don’t want to import a whole code style settings file and would rather just tweak some specific formatting settings that are responsible for most of StyleCop’s complaints about ReSharper, I recommend reading these 2 blog posts at Hock Blogs:

Navigating around the StyleCop for ReSharper project page on CodePlex also turns up a lot of additional useful information:

All in all, I’m enjoying this ReSharper plug-in. It has taken a lot of the pain out of being compliant with StyleCop’s rules.

  • email
  • DotNetKicks
  • Digg
  • del.icio.us
  • Technorati
  • StumbleUpon
  • LinkedIn
  • Facebook
  • Twitter
  • Google Bookmarks
  • Live

Update for .NET Framework 3.5 Service Pack 1 Available

Microsoft has released an update for .NET Framework 3.5 Service Pack 1.

Taken from the update page:

An update for the Microsoft .NET Framework 3.5 Service Pack 1 (SP1) is available. This article describes information about the issues that the update for the .NET Framework 3.5 SP1 fixes.

The update for the .NET Framework 3.5 SP1 fixes the issues that are described in the following articles in the Microsoft Knowledge Base:

  • 958481  List of the breaking issues with the .NET Framework 2.0 Service Pack 2 after you upgrade to the .NET Framework 3.5 Service Pack 1
  • 958483  List of the breaking issues with the .NET Framework 3.0 Service Pack 2 after you upgrade to the .NET Framework 3.5 Service Pack 1
  • 958484  List of the breaking issues with the .NET Framework 3.0 Service Pack 1 after you upgrade to the .NET Framework 3.5 Service Pack 1

Joe Healy has blogged about this update and mentions some of the important fixes:

Interesting items fixed (note a full list can be found via the KB) – dynamic data one to one relationships – ASP.NET BrowsCap being broken of FPSE are installed – some broken UpdateProgress control issues – changes in the AutoCommit behavior for Oracle transactions – problems with WPF generating images on the fly via ASP.NET on IIS – and some other fairly freaky stuff – read the kb for all details.

I installed this update today on my Vista x64 work machine and it is actually 3 seperate updates which have to be downloaded and installed in a specific order. Please be sure to read the KB documention as to the order in which to install the updates.

  • email
  • DotNetKicks
  • Digg
  • del.icio.us
  • Technorati
  • StumbleUpon
  • LinkedIn
  • Facebook
  • Twitter
  • Google Bookmarks
  • Live

New Links: Google AJAX APIs Playground and Microsoft SDKs

I came across two very cool links today that I thought I would save so I could find them later:

  • Google AJAX APIs Playground - http://code.google.com/apis/ajax/playground/
    • This page is located on the Google Code website and provides example javascript code and documentation links for what seems to be all of Google’s AJAX web services. It includes an interactive code window that allows you to modify the example code, run it, and see the results in a preview pane. Looks to be exceeding useful as a reference for experimenting with and implementing Google web services.
  • Microsoft SDKshttp://msdn.microsoft.com/en-us/dd299405.aspx
    • This page has links to all of Microsoft’s SDK downloads. Azure, Visual Studio, Office, XNA, Mobile, Silverlight, etc. You name, it’s got it.
    • You can find out more information about this new page by reading this blog post from a member of the Windows SDK team.

 

These links have also been added to the links collection in the right sidebar of this blog for quick access.

  • email
  • DotNetKicks
  • Digg
  • del.icio.us
  • Technorati
  • StumbleUpon
  • LinkedIn
  • Facebook
  • Twitter
  • Google Bookmarks
  • Live

jQuery 1.3.1 Released

The jQuery team has just released jQuery 1.3.1. This is mainly a bugfix release. You can view the fixed bugs on the jQuery bug tracker. You can download this release by visiting the jQuery Downloads page, or more directly, the 1.3.1 Release Download page

The blog post regarding this release makes a few important points to be aware of:

  • jQuery support for Safari 2 is being phased out. 
  • Packed versions of jQuery will no longer be available.
    • Packed scripts make debugging more difficult, cause platform incompatibilities (e.g. Adobe Air, Caja), and can actually increase loading times in many cases versus a plain minified script.

 

This update should not contain any breaking changes. Happy jQuerying!

  • email
  • DotNetKicks
  • Digg
  • del.icio.us
  • Technorati
  • StumbleUpon
  • LinkedIn
  • Facebook
  • Twitter
  • Google Bookmarks
  • Live