Archive for the ‘IT Support’ Category

SVN conflict on all lines (LF), while edit a file using Windows then Unix (Mac, Ubuntu)

November 1, 2010 Leave a comment

This is a work around for a problem of committing changes to subversion using multiple operating system and the end of the line conflict.

If you collaborate on a text file or a source code file while multiple people editing the file using Windows and Unix (or Mac),

you might face a challenge for committing changes to subversion.

The problem is the conflict on all lines each time a file edited with Unix then Windows, and vise versa.

To resolve this issue use the following terminal comments to edit the property of the text (source code) file.

svn propset "svn:eol-style" "native" file1.txt

Reference: Red Bean File Property

Find the version of ubuntu

October 14, 2010 Leave a comment

To find out which version of Ubuntu is installed, type the following command in the terminal: lsb_release -a


$ lsb_release -a
Distributor ID: Ubuntu
Description: Ubuntu 10.04.1 LTS
Release: 10.04
Codename: lucid

Categories: IT Support, Unix Tags:

SVN terminal, list (log) the last (top) ‘n’ transactions

October 7, 2010 Leave a comment

The followings are terminal commands for getting the details of the last ‘n’ changes to a SVN repository:

Step 1: Find the last revision number:

Use tomorrow date to include the transactions for today. If today is 7 Oct then

$ svn log -r {2010-10-08}
601 | amiraryani | 2010-10-07 18:40:23 +1100 (Thu, 07 Oct 2010) | 1 line

Step2: Now that we know the last revision number is 601, we can get the last 10 transaction between 601 and 591

svn log -r 601:591

also we can get more details by adding –verbose parameter.

svn log -r 601:591 --verbose


Categories: IT Support, Unix Tags:

How to change the Ubuntu panel without right click

September 24, 2010 Leave a comment

On the Ubuntu (version 10.04) I changed the properties of the bottom gnome panel: unticked the expand property, then locked the panel.
The result is a short version of the panel which is very difficult to rest to default using right click (at least I could not do it).

One easy way to reset the gnome panel is to remove .gconf/apps/panel folder. This can be achieved by typing the following in the terminal:

rm -r ~/.gconf/apps/panel

Then you should logout and when you login again you will find the panel is changed to default setting.

Note: By resetting panel all the customization of the panel will be lost.


Categories: IT Support Tags: ,

Stop auto closing after ipconfig command

January 28, 2010 Leave a comment

Some minor things can be annoying if you do not know the trick to do it in an easy way. One of them is getting the system IP address using ipconfig, or  executing other Windows commands directly from the Start -> Run. The problem is that the command prompt window will close automatically after execution of the command. So to avoid closing the windows automatically you have two options:

  1. Go to Start -> Run
  2. Type cmd and hit enter.
  3. Type the command (e.g ipconfig) in the opened window.

alternatively you can

  1. Go to Start -> Run
  2. Type cmd /K command and hit enter. (e.g cmd /k ipconfig)

CMD /K will stop the command window from closing after the command.

Categories: IT Support

Visual Studio Setup (deployment) project

August 7, 2009 1 comment

Reading the Microsoft support article about using the Setup project in Visual Studio:

In order to create a Setup deployment project :

  1. Start a new project by doing one of the following:
    • On the File menu, point to New, and then click Project.


    • If you have an project open that you would like to create a setup package for, right-click Solution MyProject (where the name of your project is MyProject) in the Solution Explorer, point to Add, and then click New Project.
  2. In the New Project dialog box, select Setup and Deployment Projects in the Project Type pane, and then select the type of setup that you want in the Templates pane.

    The project is added to the Solution Explorer, and then the File System Editor opens.

  3. In the Properties dialog box, select the ProductName property, and then type the name of your product.

And to add files to the Setup project:

  1. In the File System Editor, select the Application Folder node.
  2. Right-click the Application folder, and then on the Action menu, click Add, File. In the Add Files dialog box, browse to select any files that you need to add to your application.

    NOTE: If you already have an application project in your solution, you can add the project outputs by selecting Project Outputs instead of File.

  3. To add an existing merge module to your setup package (this is not possible for a Cab project), right-click the name of your setup package in the Solution Explorer. Click Add, and then click Merge Module. In the Add Modules dialog box, browse to select any merge modules that you need to add to your application.

To create a shortcut for the installed program:

  1. Open the File System Editor: from the View menu, point to Editor, and then click File System.
  2. Open the application folder that contains the file that you want to create a shortcut for.
  3. Right-click the file that you want to create a shortcut to.
  4. Click Create Shortcut.
  5. A shortcut will be created in the same folder as the original file.
  6. Drag the shortcut to the desired folder. For example, if you want to create a shortcut in your Program menu, drag the shortcut to the Programs menu folder; if you want to create a shortcut on the Start menu, drag the shortcut to the Start menu folder. The folder location of the shortcut can also be changed through the folder field of the Properties Window.

To register COM objects as part of the installation:

  • Add a COM object to your Visual Studio deployment project.
  • In the Solution Explorer, right-click the module that you just added, and then click Properties.

    NOTE: The Properties window contains a table with two columns and x number of rows (the number of rows depends on the project). The left column lists the specific properties. The right column is explained in step 4.

  • Go to Properties for this module (located by default in the upper-right corner of the .NET Deployment project), and then click Registry property.

    NOTE: The Registry property specifies whether a file, assembly, or project output group should be registered on a target computer during installation.

  • There is a list box in the right column of the Registry property, which displays several options for you to choose from. Note the following details for an explanation of these options:
    • For assembly, registration is not normally required, and therefore the default is DoNotRegister (this means that the item will not be registered during the installation).
    • For a COM module, you have the options of COM, COMRelativePath, and COMSelfReg. Any one of those three options will register the COM module during the installation.

      Note the following details about each choice:

    • COM: The module will be registered as a COM object by the Windows Installer engine. The deployment project will update the Class table, ProgID table, and other tables in the Registry Tables group of the corresponding .msi file. This is the recommended way to register a COM module.
    • COMRelativePath: The module will be registered as an isolated COM object by the Windows Installer engine. Note that this module will be used only by the application that the module is installed with.
    • COMSelfReg: The installer calls the DllRegisterServer function of that module at the time that you install the module and the DllUnregisterServer function at the time that you uninstall the module. The deployment project will update the SelfReg table of the corresponding .msi file. It is not recommended that the installation package use self-registration. Instead, the installation package should register modules by authoring one or more of the other tables provided by the installer for this purpose (that is, select the COM or COMRelativePath options). Many of the benefits of having a central installer service are lost with self-registration, because self-registration routines tend to hide critical configuration information.



    Repair .Net 2: missing Netfx20a_x86.msi

    June 30, 2009 1 comment

    In my previous post I mentioned about a repair process for .Net 2 in order to host WCF in IIS . However, after following Microsoft instruction on repair process you may face an annoying issue where Windows installer can not find Netfx20a_x86.msi.

    Netfx20a_x86.msi is a component of .Net 3.5 and it will get extracted to a folder such as “C:\5409af1fab5096fc4d07947959\wcu\dotNetFramework\dotNetFX20” as part of the install process. I tried to extract the file from the folder and use it for repairing .Net 2.0 but it did not work. After providing the msi file it will look for the setup.exe.

    Solution: Ignore repairing .Net 2 and repair .Net 3 (or 3.5 if installed). In my case repairing .Net 3.5 fixed the issue in IIS.