Cyprich.com

Occasionally Relevant Insights from a Software Builder

By

Using Line Numbers in vi

Debugging is easier with line numbers. The default setting for vi and vim is for line numbers in the document to be hidden.

Setting Line Numbers within the Editor

You can turn on line numbers by typing

:set number

or

:set nu

 

The line numbers can also be turned off by typing

:set nonumber

or

:set nu!

 

Making Line Numbers Default in vi

You need to edit .vimrc or .bashrc (which is normally found in the root of the user’s folders). Add the following command:

set number

vi will start with line numbers every time a document is opened.

 

Jump to a Line When Opening vi

If you know which line you would like to edit in vi, you can go right to the line when you open the document in vi from the shell.

$ vi +linenumber file.php

i.e. vi +8 file.php will open the document and place the cursor in line 8.

By

Registering ASP.NET after IIS Installation

If the IIS web server is installed after the .NET Framework was installed, ASP.NET web pages will not work. This issue will also occur if the web server is reinstalled. The reason for this is that the ASP.NET file extensions are not being associated with the IIS mappings.

How To Fix

This can be fixed with the following procedure:

  1. Go to the Windows command prompt by opening the Start menu, select Run, type cmd and press OK.
  2. When your in the command prompt, type

    "%windir%\Microsoft.NET\Framework\.NET_Version\aspnet_regiis.exe" –i

  3. Then register Aspnet_isapi.dll with the following command:

    "regsvr32 %windir%\Microsoft.NET\Framework\.NET_Version\aspnet_isapi.dll"

Example for Registering .NET 2.0/3.0/3.5

"%windir%\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis.exe" –i
"regsvr32 %windir%\Microsoft.NET\Framework\v2.0.50727\aspnet_isapi.dll"

If you running .NET 3.0 or 3.5, you need to use the above example for .NET 2.0. This version of .NET is installed with 3.0/3.5. The newest versions do not have the aspnet_isapi.dll files in their folders. This isn’t a problem because .NET 3.0/3.5 are simply v2.0 with extensions. More appropriates version numbers for the latest Frameworks should be 2.1 and 2.2 since they don’t add a great deal to v2.0.