January 2004 - Posts

"IIS Not Running ASP.Net 1.1"

posted Wednesday, January 14, 2004 5:35 AM by Fletcher.Dunton

Folks:

Recently,  a student of mine installed VS.Net 2003 on their XP Pro box, then eagerly started developing a new ASP.Net web app and received the message:

 "Visual Studio .Net has detected that the specified Web Server is not Running ASP.Net 1.1”. 

Initially, I questioned how that could happen, since VS.Net 2003 comes with the 1.1 framework.  Then after some investigation (but without rebuilding my PC to verify this) I've come up with the following scenario that might make cause the problem:

  1. I developer installed XP Pro (or Server 2003) and does not explicitly set the IIS option at install time.
  2. They then install VS.Net 2003, which installs the 1.1 framework.
  3. They try to create a ASP.Net web app and receive a nasty gram to the effect “http :Internal Server error, server not found“.
  4. Realizing that IIS is not on there PC, they pull the OS install disk out and run setup, installing  the web server. 
  5. This installs the 1.0 framework on the box, but does not configure the web server and ASP.net for side by side execution of the framework.

Luckily, there's a fix:

  1. If this has happened to you, you may need to run aspnet_regiis with the -r option to replace the current version of IIS and script maps.
  2. If this has happened to you and you DON'T need side by side execution of the framework., please download the 1.1 framework follow the instruction documented at : http://www.asp.net/download-1.1.aspx?tabindex=0&tabid=1
  3. If this has happened to you and you need side by side execution of the framework., please see: http://www.asp.net/faq/SideBySide.aspx

I welcome your feedback...

 

with 0 Comments

Series:Axioms for Good IT Process

posted Tuesday, January 13, 2004 7:24 AM by Fletcher.Dunton

I was recently asked by a client to help them evaluate their current IT process. As I browsed their existing  policy, project notebooks and other artifacts I came to realize just how deceived and misinformed (these) folks were about what “good IT process“ is and is not. 

In fact, some of the comments I received back from both management and developers ranged from “I just hate (any) process” to “Should I go to CMM training?”  (I just love that one) and “We can't afford to have a process.“ (well “boo-hoo-hoo”).  And these were highly paid professionals.

Look, we've all had the displeasure of working on projects that have no requirements, plan or direction. And conversely, many of us have worked for shops that have so much process that one must fill out a leave slip just to take a break for a call to nature!  To the extreme, each of these environments are highly ineffective and introduces risk ($$$), both to the system under development and our collective livelihood.  Surely, there has to middle ground.  There must be way. 

Ah-hah: I see I’ve piqued your interest.  Over the next few weeks, I’ll be expanding on “Axioms for Good IT process”, including the following

1.       “Its not that you have a process, rather it’s what process you have.”

2.       “People are more important than any process.” - Grady Booch

3.        “Good people with a good process will outperform good people with no process every time.”  - Grady Booch

4.       It’s not that you can’t afford to have a process, it’s that you can’t afford NOT to have GOOD process.

5.       Eventually, the Sarbanes-Oxley Act (http://www.sarbanes-oxley.com) will affect you and your IT Shop and the integrity with which each project’s artifacts are maintained.

Listen, your process is not static. It must evolve over time. And it is a living reflection of you and your firm.

I welcome your feedback. By the way, you know that Mom and Pop Shop that just opened down the street? Well they're CMM Level 5.

 

with 2 Comments