An article located at http://etech.eweek.com/content/web_technology/top_web_developer_mistakes.html makes really good reading.  It's a slide show, but below is a condensed list of what the article says!

My additional comments are in dark blue, you got any?

1) Click, Click, Click - This is great, someone is at your site and they're ready to make a purchase. Here they go; one click, two clicks, three clicks, just one more! And.... they're gone. Maybe if they could get to where they wanted to go right away you would have made a sale. (I disagree slightly in that as long as the navigation is logical and correct then it should not matter to the user how many clicks...)

2) Just Click on the Magic Compass - It's great that new web technologies make it possible to add lots of cool new navigation and interaction techniques. But don't put access to important features and content behind a strange graphic or icon. People know how links work on web pages. Some icons might as well be in elvish.

3) Don't be too Graphic - The Following Web Content Contains Massive Image Files and Graphics That May not Be Suitable For Visitors With Anything But the Fastest Possible Internet Connections. Toning Down the Giant Graphics Files Is Advised For Site Developers. (This is becoming an increasing problem given that mobile internet is really taking off!)

4) Registry of Lost Web Sites - The legend of the Invisible Web Site. Unseen by search engines, web users or anyone who might actually use the services of the website. It uses the magic of enforced site registration to keep its valuable content hidden from all who might want to use it, especially those who want to give the owners of the site some business.

5) Sticking to the Script - Scripting languages are so useful. They make it possible to do lots of cool things in web design. Click this link for an example. Mmm, getting a script error. If only there was some other way to link to content, you know like an HTML link. Don't use scripting where HTML will work just fine.

6) Too Rich - Animation is great, when it comes to Saturday morning cartoons. On the web too many animations, Flashy graphics, spinning graphs and windows popping in your face is sort of like a sign saying, "Stay away". (100% agree)

7) Welcome To Our Site "image placeholder" - Here's a great idea for the budding web site and application developer. There's this technology that makes it possible to display information to visitors and users. It's called Text! And unlike images and animations used where text would work just as well, text will always show up.

8) What's Your Color Scheme? - Whoa, trippy man. I love the way the orange text looks on that purple background. Dude, that financial firm is just going to love this site design. Or probably not. Unless you're designing for a jam band or some other client that likes wild colors, stick to color matchings that are pleasing to everyone. (Obviously they didn't see the custom colours that I used on the TtG Brokers site )

9) Directionless Navigation - Wow, this site looks like it has lots of great content and products. But where is everything? Can't find related content? Where's that thing I saw the other day? I'm lost! Users of your web site shouldn't need a trail guide. Make navigation clean, simple and easy to find. (All computer users are very aware of hierarchical navigation [Windows Explorer] and also an address bar 'bread crumb', so play to their strengths!)

10) Can We Table This For Now? - Aren't tables great! They provide so much flexibility when laying out web content. And it looks so nice, at one specific resolution on one specific browser. At other resolutions, yuck! When using tables make good use of percentages and make sure the design looks good on all users screens.

11) Sloppy with Text - Wilcom too my grate neww web apliccatiun. Im a perfessinal web dervelper! The greatest coding skills won't help if your web content is full of misspellings and poor grammar. (Being dyslexic, I have no cammant!)

12) Click Here for Click Here - This is such a nice web application that you've built. It will really help our business deploy content to the web. And look it automatically creates links that say things like "Click Here", "More" and "Continue Reading." Now how do we change those to something more descriptive? We can't? Don't call us, we'll call you. (Use your Tool Tip and Alt tags!!!)

13) Putting up a Velvet Rope - This is such as cool web site, can I come in? Oh, you only let in people from the IE click? Us Safari geeks aren't welcome? And I was going to spend so much money. Don't you know that browser-specific web sites and applications are like so five years ago?

14) This is a Web Site, Right? - Now this is what I call a content rich site. Look at the useful information here. Let me click here, wait, this is a PDF document, and this is a Word document. I thought this was a web site, you know, something I could view in a web browser. (What is the point of providing a content managed Web site when half the content the user wants to view is hidden away in PDF and Word files?  I bet 90% or more of content in Word and PDF that are available on the internet would be easy to provide on a Web page and if it was users would read it more!)

15) Over-crowding - You know, when people say that something is like finding a needle in a haystack, they don't mean that in a good way. On the web, too many links and other components can make it hard for a visitor to find the content that they want.

The Microsoft Learning site has a number of self-paced eLearning courses on current technologies (e.g. .NET 2.0 & 3.0 and VS2005.) This blog pulls a subset of the developer courses that are free and lists them It is worth taking a look at the full developer catalogue as well.

I am personally interested in Clinic 5046 and 5230.

http://blogs.msdn.com/cbowen/archive/2007/06/20/free-microsoft-online-developer-courses.aspx

I do a lot of development on my laptop, both at work and ay home.  Both machines are running Windows XP Professional, and have IIS installed.  I often get the error HTTP 403.9 - Access Forbidden: Too many users are connected".  I have done some digging around this, and found that by default IIS 5.1 on Microsoft Windows XP Professional allows only ten concurrent users connected at any one time.

To get around this, you first need to change your default windows script host to cscript.exe:

cscript //h:cscript

Then you can increase the connection limit to 40.  it can't be increased beyond 40 as this is a hard coded windows limitation:

c:\inetpub\adminscripts\adsutil set w3svc/MaxConnections 40

I would then re-set your default windows script host back to it's default of WScript.exe, by:

cscript //h:wsscript

I thought that I'd bring to your attention a couple of great Internet Explorer toolbars/extensions that I use.

Just released is the official release of the Internet Explorer Developer Toolbar (IEDevToolbar).  It has just come out of beta, and available for download here.  If you do any development on Internet Explorer or want to 'dissect' Web sites then this is the tool for you.  I really love the ability to change the client code (HTML, CSS, etc.) dynamically!

The second tool that I use for Internet Explorer is the IE7Pro toolbar.  I've blogged about it before here, and it has been vastly updated and improved since then.  Despite it's name, this also works on IE6, so if you are still on the old browser, give it a go.  You can download the updated toolbar here.

I am part of a team working on a very exciting MCMS (Microsoft Content Management Server) 2003 SP2 project.  We are using Visual Studio (VS) 2005 and the .NET Framework 2.0.

The solution has been created and we are all using source control and sharing the project among many developers.  This works fine, except when I try to go to the MCMS template explorer.  I get the following error, but no others do, despite having the same build/setup:

No CMS-Enabled Projects are open

After some reading of some news groups and looking up information posted by the MCMS Gurus (Stefan Goßner, Lim Mei Ying, Joel Ward, Angus Logan), I came across the following:

To enable a MCMS project, from the menu "Website" select "Enable as MCMS Project". - This was disabled for me, so...

In the vwb.WebInfo file, make sure that you have the following:

<?xml version="1.0" encoding="UTF-8"?>
<VisualWebDeveloper>
<Globals>
<UserProperties CmsEnabled="1"/>
</Globals>
</VisualWebDeveloper>

Again, my project had this!

Another suggestion was to open the project using HTTP rather than the file system.  I tried this also, but to no avail.

I then closed Visual Studio in lost hope...

Then instead of opening the project via double clicking on the solution/project, I simply opened Visual Studio up and from the "Start Page" tab, I selected the project.

Weird... it worked!

Whilst not the best solution at least it allows me to get to the MCMS Template Explorer.  In order to maintain code and source control, I still have to open the original project the original way.  Perhaps later I can find a proper solution.

Was helping someone install a new New site onto one of their systems earlier today.  The installation went OK, but then when they went to the Web administration console, they simply received a "Service Unavailable" message.  It was all rather confusing.  We checked the installation, and re-installed a couple times, to no effect.  We checked the file and IIS permissions, again, no effect.  I then just happened to notice that the application pool that the Web application was running had not been started.  So, started the application pool, and bob's your uncle, it all worked fine.

So, if you get a simple "Service Unavailable" message from a Web application hosted on a Windows 2003 server.  Check to see what application pool the application is running in, and make sure that it is has started.

Earlier I posted an article about using IIS Diagnostics Toolkit.  I've just remembered another tool that I have used in the past, called 'Fiddler'.

Fiddler is a tool that allows you to find out how Microsoft Internet Explorer interacts with your Web application.  It allows you to track down strange performance bottlenecks, gives you information about which cookies are being sent, what downloaded content is marked cacheable, and more.

It is an HTTP debugging proxy that logs all HTTP traffic between your computer and the Internet. It enables you to inspect all HTTP traffic, set breakpoints, and "fiddle" with incoming or outgoing data. It is much simpler to use than NetMon or other network debuggers because it exposes only HTTP traffic and does so in a user-friendly format.

You can find out more information and download Fiddler from here.

Yesterday, I was helping a colleague with some IIS and MCMS (Microsoft Content Management Server) security issues.  Whilst we resolved the security issues relatively easily, we had trouble putting them to test on the server.  Basically, we needed an IIS box, with a private SSL certificate, in order to secure the login page.

Well, we were having a devil of a time getting HTTPS to work.  If you went to the site using basic HTTP it all worked fine.  However, as soon as you tried to go to the site using HTTPS it failed and came up with a message like "DNS error".

I eventually found this tool called IIS Diagnostics Toolkit (x86), from Microsoft which allowed us to find that the SSL Certificate we generated was invalid, and that we needed to create a new stronger certificate.