Visual Studio

Visual Studio 2003 Find in Files in Windows Vista

Rodolfo Finochietti — Sun, 05 Aug 2007 02:08:09 GMT

To avoid Visual Studio 2003 freeze in Windows Vista when using find in files function, go to properties in the the Visual Studio 2003 shortcut, select "Compatibility" tab, check "Disable visual themes", check "Disable desktop composition" and select "Windows XP (Service Pack 2)" in the "Run this program in compatability mode for" combo.

Technorati tags:Visual Studio, Windows Vista

Visual Studio 2005 Web Application Projects

Rodolfo Finochietti — Sun, 18 Jun 2006 22:13:00 GMT

Today I finally found the form of using projects web in Visual Studio 2005.

First it is necessary to install this:

Microsoft Visual Studio 2005 - Update to Support Web Application Projects

And then this:

Visual Studio 2005 Web Application Projects Add-In

Enjoy!

Technorati tags:Visual Studio

Visual Studio Code Snippets Error

Rodolfo Finochietti — Mon, 17 Apr 2006 14:48:00 GMT

Yesterday after reorganizing my code snippets the code editor of visual studio still show the same snippets folder that no longer exist. The solution for this problem was to eliminate the file C:\Documents and Settings\[UserName]\Local Settings\Application Data\Microsoft\VisualStudio\8.0\1033\ExpansionsXML.xml

Technorati tags: Visual Studio

Ctrl-Tab in Visual Studio 2005

Rodolfo Finochietti — Tue, 21 Mar 2006 11:13:00 GMT

Yesterday accidentally I pressed the combination of keys Ctrl+Tab in Visual Studio 2005, I was surprised with the result. This combination of keys allows to change between documents and windows without using the mouse and help me to work more quick. Try it!.

Technorati tags: Visual Studio

Visual Studio Setup and Deployment Project, Unattended installation and Custom Properties

Rodolfo Finochietti — Sat, 11 Feb 2006 22:31:00 GMT

When execute an installer made with Visual Studio in the following way:

msiexec /i ProgramInstaller.msi /q TARGETDIR=C:\Program CUSTOMPROPERTY1="SomeValue"

The custom property CUSTOMPROPERTY1 didnt't take the value "SomeValue". After look at the log of the installation (generated with msiexe /log) I saw that Visual Studio always generates a custom action for each property to assign the default value. These custom actions (that have the name CustomTextA_SetProperty_EDITx) are excecute after Windows Installer assigns the properties with the values of the parameters. The solution was eliminated those custom actions, first using Orca and then with this script:

Option Explicit

Dim WI, DB, DelCustom, DelCustom2
Dim Path_MSI_File
Const msiOpenDatabaseModeDirect = 2

Set WI = CreateObject("WindowsInstaller.Installer"): CheckError
Path_MSI_File = " "

Path_MSI_File = Wscript.Arguments(0)
Set DB = WI.OpenDatabase(Path_MSI_File,msiOpenDatabaseModeDirect):CheckError

'Remove VS Custom Actions
Set DelCustom = DB.OpenView("Delete From CustomAction WHERE `Action`='CustomTextA_SetProperty_EDIT1'"):CheckError
DelCustom.Execute : CheckError

Set DelCustom2 = DB.OpenView("Delete From InstallUISequence WHERE `Action`='CustomTextA_SetProperty_EDIT1'"):CheckError
DelCustom2.Execute : CheckError

'Finish
Set WI = Nothing
Wscript.Quit 0

Sub CheckError
Dim message, errRec
If Err = 0 Then Exit Sub
message = Err.Source & " " & Hex(Err) & ": " & Err.Description
If Not installer Is Nothing Then
Set errRec = installer.LastErrorRecord
If Not errRec Is Nothing Then message = message & vbLf & errRec.FormatText
End If
Fail message
End Sub

Sub Fail(message)
Wscript.Echo message
Wscript.Quit 2
End Sub

Technorati tags: Visual Studio