Visual Studio

Visual Studio 2003 Find in Files in Windows Vista
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

posted @ Saturday, August 04, 2007 11:08 PM | Feedback (13)
Visual Studio 2005 Web Application Projects
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

posted @ Sunday, June 18, 2006 7:13 PM | Feedback (0)
Visual Studio Code Snippets Error
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

posted @ Monday, April 17, 2006 11:48 AM | Feedback (0)
Ctrl-Tab in Visual Studio 2005
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

posted @ Tuesday, March 21, 2006 8:13 AM | Feedback (2)
Visual Studio Setup and Deployment Project, Unattended installation and Custom Properties
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 =...

posted @ Saturday, February 11, 2006 7:31 PM | Feedback (0)