WebLog of Ken Cox - All Comments

re: Testing Sites Against IE 6, IE 7, and IE 8 (beta 2)

Joe Chung — Fri, 29 Aug 2008 19:00:13 GMT

I would rather test against the real thing than a simulation. Hacking multiple versions of IE to work in a single OS instance also isn't reliable.

re: Testing Sites Against IE 6, IE 7, and IE 8 (beta 2)

dukebaby — Fri, 29 Aug 2008 16:22:21 GMT

I've found DebugBar's IETester to be very hand for this scenerio.

It is a simple program that simulates all versions of IE.

www.my-debugbar.com/.../HomePage

re: IE6 Hanging after Clearing the Cache: Remove AJAX Script Compression Too

StormSilver — Fri, 29 Aug 2008 16:00:03 GMT

We had the exact same problem, although we are doing a Ruby on Rails installation totally unrelated to ASP. We discovered that a "Virgin" IE, as you say, would hang for about 5 minutes per chunk of content that we were loading. Although we had disabled gzip compression in Apache for IE6, we found the problem still occurred intermittently. We are using Akamai in front of our servers and it turned out that even with Akamai set to never serve gzipped content, if the origin server sent the content gzipped, that is how Akamai would serve it. Therefore if a user were to hit our server using Firefox, they would receive compressed scripts, and then subsequent users using IE6 would also receive those compressed scripts. The solution was to turn off gzip compression for everyone, everywhere, all the time.

re: Converting VB LINQ to C# LINQ

Dave Doknjas — Mon, 25 Aug 2008 05:05:48 GMT

Kudos to Dave at VB Conversions (our honorable competitor) for getting the jump on us regarding many types of LINQ conversions, but a simpler conversion is just:

var q = from c in dc.categories

from p in dc.products

where c.CategoryID == p.CategoryID

group p by c.CategoryName into g

select new {cgname = g.Key, prdcts = g};

re: Converting VB LINQ to C# LINQ

Dave — Sat, 23 Aug 2008 19:14:38 GMT

Ken, thanks for pointing out the equal sign problem in the LINQ Where clause conversions.

It turns out that this bug only happens when there's a "Select New With" clause in the LINQ statement. The converter thought the Where clause equal sign was one of the equal signs in the With clause (which should be converted to "=").

This has been fixed in the latest version of the VB.Net to C# Converter, which was just released today. If you find any more problems, please let me know and I'll get a fix out asap. Thanks!

re: Visual Studio 2008 SP1 Adds JavaScript Formatting

Edward Ng — Tue, 19 Aug 2008 02:46:01 GMT

The VS2008 SP1 JScript formatter sucks !

Enabling JavaScript Intellisense In External Libraries Using Microsoft Visual Studio 2008 Service Pack 1

mandown — Sun, 17 Aug 2008 08:56:49 GMT

This is pretty easy to get working in Microsoft Visual Studio 2008 Service Pack 1. In order to get this working you need to tell Intellisense the location of the libraries you are using. Ken Cox has written a great article on how to get this working.

Enabling Javascript Intellisense In External Libraries

DotNetKicks.com — Thu, 14 Aug 2008 18:57:43 GMT

You've been kicked (a good thing) - Trackback from DotNetKicks.com

Enabling JavaScript IntelliSense in External Libraries - WebLog of Ken Cox

Enabling JavaScript IntelliSense in External Libraries - WebLog of Ken Cox — Thu, 14 Aug 2008 18:22:04 GMT

Pingback from Enabling JavaScript IntelliSense in External Libraries - WebLog of Ken Cox

re: Visual Studio 2008 SP1 Adds JavaScript Formatting

Ken Cox [MVP] — Thu, 14 Aug 2008 18:07:51 GMT

@Dominic: See this post for enabling JavaScript IntelliSense:

weblogs.asp.net/.../enabling-javascript-intellisense-in-external-libraries.aspx

Ken