Developer OneNote » Development

TFS How to change the computer name or owner for a workspace

emma — Sat, 21 Jan 2012 14:34:40 +0000

The owner and computer name of the workspace are not editable in Visual Studio 2010. However, you might need it when you renamed your machine or your account is renamed. To do this, open a Visual Studio Command Prompt (2010) from program files, and cd to your workspace, then run following

Change the computer name for a workspace

tf workspaces /updateComputerName:<OldComputerName> /collection:

You need replace to your actual old computer name and to your actual TFS collection URL.

Change the owner for a workspace

tf workspaces /updateUserName: /collection:

Common TFS commands

Highlight the file you work with in Visual Studio Solution Explorer

emma — Wed, 19 Oct 2011 14:15:23 +0000

Visual Studio 2010 Tip – Highlight the file you work with in Solution Explorer Go to Tools->Options->Projects and Solutions->General Check the "Track Active Item In Solution Explorer" checkbox. Related posts: Visual Studio Themes and Color Schemes CopySourceAsHtml for Visual Studio … Continue reading → Related posts:

When should you use var keyword in C#?

emma — Sun, 25 Sep 2011 03:09:24 +0000

When should you use var keyword in C#?

Check out Eric Lippert’s blog article http://blogs.msdn.com/b/ericlippert/archive/2011/04/20/uses-and-misuses-of-implicit-typing.aspx

No related posts.

Kentico CMS Installation issues troubleshooting – SQL Server Connection problems

emma — Thu, 08 Sep 2011 17:46:22 +0000

You may encounter problems when entering the database connection details in the first step of database setup:

Error 1: Establishing connection to the server

Error message:

An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 – Could not open a connection to SQL Server)

Troubleshooting:

Make sure the SQL Server name or IP address is correct. In some cases, using one of the following values may help:
- your computer name
- localhost
- 127.0.0.1
- (local)
Make sure the server has Microsoft SQL Server 2005 or 2008 installed and running.
Make sure you are using the appropriate instance of the SQL Server in case you are using different instances of SQL Server. The instance name must be entered as myserver\myinstance (please note there’s a backslash \).
If you’re using Microsoft SQL Server Express 2005 with default installation settings, the correct server name is .\sqlexpress or computername\sqlexpress .
Make sure the access to the database server is not blocked by some firewall (the default port number for TCP/IP protocol is 1433).
If you’re using SQL Server 2005 (especially the Express Edition), some protocols are disabled by default. You may need to go to Start menu -> All Programs -> Microsoft SQL Server 2005 ->Configuration Tools on the computer where the SQL Server is installed and start SQL Server Configuration Manager. Then, go to SQL Server 2005 Network Configuration and enable the TCP/IP protocol:
You may also need to enable the TCP/IP protocol in the SQL Native Client Configuration –> Client Protocols section:

Error 2: Login failed for user ‘xy’

Error message:

Troubleshooting for SQL Server account

If you’re using SQL Server account with password, make sure you are using a valid user name and password. The login must be created on the server, it must be enabled and permissions to connect to the server must be granted to it. You can check the user account in Enterprise Manager/SQL Server Management Studio -> Server -> Security -> Logins:

Also, check the Server Properties -> Security dialog in Enterprise Manager/SQL Server Management Studio and make sure your server supports SQL Server and Windows Authentication mode:

Troubleshooting for Windows Authentication account

If you’re using Windows Authentication account, the situation may be a little more complex and may require you to contact your network administrator. ASP.NET applications run under some particular local or domain account. This current account is displayed on the screen:

This account must have its own login with Windows authentication in the SQL Server. You can create the login in Enterprise Manager\SQL Server Management Studio -> Security -> Logins and grant appropriate permissions on the server to it. If you SQL Server is located on a different machine than your web server, you may need to configure your web application so that it runs under some domain account, rather than local account so that you can the login in the remote SQL Server.

No related posts.

HTTP Error 404.13 – Not Found Error When Upload Big File using WCF

emma — Sun, 10 Jul 2011 16:38:11 +0000

On IIS 7.5, if you upload big file thru WCF service, you might get http 404.13 error from IIS server.

HTTP Error 404.13 – Not Found
The request filtering module is configured to deny a request that exceeds the request content length.

The solution is set a higher value for maxAllowedContentLength in web.config of application

Generate GUID in PERL

emma — Thu, 30 Jun 2011 16:13:41 +0000

It’s very common for developer to generate a GUID in code to guarantee uniqueness. Here is the sample code to generate a GUID in Perl

my $guid = `uuidgen.exe`;
chomp $guid;

Uuuidgen.exe is a tool from DotNet Framework. You can append "-c" option to generate uppercase letters

Run uuidgen /? to see the detail usage of uuidgen.
Microsoft UUID Generator v1.01 Copyright (c) Microsoft Corporation. All rights reserved.

usage: uuidgen [-xisconvh?]
        x – Generate sequential (V1) UUIDs
        i – Output UUID in an IDL interface template
        s – Output UUID as an initialized C struct
        c – Output UUID in upper case
        o – redirect output to a file, specified immediately after o
        n – Number of UUIDs to generate, specified immediately after n
        v – display version information about uuidgen
        h,? – Display command option summary

MSBUILD Reserved Properties

emma — Fri, 22 Apr 2011 12:43:49 +0000

When you use MSBuild, a handful of properties are available to you out of the box that cannot be modified. These are known as reserved properties. Following table presents all reserved properties in MSBuild 4.

MSBuildExtensionsPath	The full path to where MSBuild extensions are located. This is typically under the Program Files folder. Note that now this always points to the 32-bit location.
MSBuildExtensionsPath32	The full path where MSBuild 32-bit extensions are located. This typically is located under the Program Files folder. For 32-bit machines, this value will be the same as MSBuildExtensionsPath.
MSBuildExtensionsPath64*	The full path where MSBuild 64-bit extensions are located. This typically is under the Program Files folder. For 32-bit machines, this value will be empty.
MSBuildLastTaskResult*	This value holds the return value from the previous task. It will be true if the task completed successfully, and false otherwise.
MSBuildNodeCount	The maximum number of nodes (processes) that are being used to build the project. If the /m switch is not used, then this value will be 1. If you use the /m switch without specifying a number of nodes, then the default is the number of CPUs available.
MSBuildOverrideTasksPath *	MSBuild 4.0 introduces override tasks, which are tasks that force themselves to be used instead of any other defined task with the same name, and this property points to a file that contains the overrides. The override tasks feature is used internally to help MSBuild 4.0 work well with other versions of MSBuild.
MSBuildProgramFiles32 *	This contains the path to the 32-bit Program Files folder. To get the value for the default Program Files folder, use $(ProgramFiles).
MSBuildProjectDefault	Targets Contains the list of the default targets.
MSBuildProjectDefaultTargets	Contains a list of the default targets.
MSBuildProjectDirectory	The full path to the directory where the project file is located.
MSBuildProjectDirectoryNoRoot	The full path to the directory where the project file is located, excluding the root directory.
MSBuildProjectExtension	The extension of the project file, including the period.
MSBuildProjectFile	The name of the project file, including the extension.
MSBuildProjectFullPath	The full path to the project file.
MSBuildProjectName	The name of the project file, without the extension.
MSBuildStartupDirectory	The full path to the folder where the MSBuild process is invoked.
MSBuildThisFile *	Contains the file name, including the extension, of the file that contains the property usage. This differs from MSBuildProjectFile in that MSBuildProjectFile always refers to the file that was invoked, not any imported file name.
MSBuildThisFileDirectory*	This is the full path to the directory that contains the file that is currently being executed.
MSBuildThisFileDirectoryNoRoot *	Same as MSBuildThisFileDirectory without the root
MSBuildThisFileDirectoryNoRoot*	The same as MSBuildThisFileDirectory, except with the root removed.
MSBuildThisFileExtension *	The extension of the file referenced by MSBuildThisFile.
MSBuildThisFileFullPath*	The full path to the file that is currently executing.
MSBuildThisFileName*	The name of the file, excluding the extension and path, of the currently executing file.
MSBuildToolsPath(MSBuildBinPath)	The full path to the location where the MSBuild binaries are located. In MSBuild 2.0, this property is named MSBuildBinPath and is deprecated in MSBuild 3.5 and later. MSBuildBinPath and MSBuildToolsPath have the same value, but you should use only MSBuildToolsPath.
MSBuildToolsVersion	The version of the tools being used to build the project. Possible values include 2.0, 3.5, and 4.0. The default value is 2.0.

* Denotes parameters new with MSBuild 4.0.

This table is copied from the book “Inside Microsoft Build Engine 2.”

How to debug msbuild issues

IIS 7.5 Error The temp directory in chart handler configuration is not accessible

emma — Fri, 08 Apr 2011 17:33:36 +0000

If you build a web application with Chart control for ASP.NET 4.0 and deploy the site to web server. You might get following error on the live site:

The temp directory in chart handler configuration is not accessible

To resolve this, first go to web.config and find the ChartImage directory in appsettings.

The go to the temp chart image directory and grant read and write permission to IIS working process account in share properties – security tab. Note that the account runs IIS working process is different between IIS 7 and IIS 7.5

On Windows Server 2008 has IIS7, grant Read and Write permission to Network Service
On Windows server 2008 R2 has IIS 7.5, grant Read and Write permission to AppPool\. Replace to the actual machine pool your site is running on, for example, if your site is running on pool named ASP.NET v4.0, then the account you need grant permission would be IIS AppPool\ASP.NET v4.0, you can refer this step by step instructions for detail

Remove dead using statements

emma — Sat, 19 Mar 2011 17:24:25 +0000

Visual Studio has a great feature to easily remove all dead using statements in your code.

The steps are pretty straightforward.

Right click anywhere from the code
Select Organize Using and
Select Remove Unused Usings.

Could not load file or assembly TraceWrapper, Version=1.0.523.0

emma — Sat, 19 Mar 2011 15:31:50 +0000

There are two versions of the TraceWrapper.dll in SCVMM install CD. One is x86 version and the other is x64 version. When you build your application on top of SCVMM library Microsoft.SystemCenter.VirtualMachineManager, it’s very important to pick up the correct version TraceWrapper.dll. In general, you should copy the 32 bit dll if you are using 32 bit system, copy 64 bit dll if you are using 64 bit system. Otherwise following BadImageFormatException would occur during runtime.

Could not load file or assembly ‘TraceWrapper, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35′ or one of its dependencies. An attempt was made to load a program with an incorrect format.

However, you should keep using 32 bit TraceWrapper on a 64 bit system for following scenarios:

You need debug your app in Visual Studio directly. In this case, process launched from Visual Studio debugger runs in WOW64 mode.
IIS is configured to run in 32 bit mode. In this case, all working processes run in WOW64 mode.

This is because in 64 bit windows, processes in WOW64 mode are 32 bit processes and can’t load 64 bit TraceWrapper.dll.