TortoiseSVN Proxy Exceptions for Local Host

18 01 2013

Today I found some strange behavior in TortoiseSVN (1.7.11, Build 23600 – 64 Bit).

I tried to configure the proxy settings so that I can both access SVN repos hosted on the internet behind an HTTP proxy and also local repositories hosted on the dev machine. It was unclear what to enter into the „Exceptions“ field.

„localhost“ didn’t work. „“ as well as the local IPv4 or local IPv6 addresses didn’t work either. The hostname as printed by the „hostname“ command (here: „XPS15z“) in a command shell did also not work.

The only thing that worked was the hostname in lowercase letters (here: „xps15z“)!

TortoiseSVN Proxy Exceptions

Maybe this worked because the SVN URL for the local repo also used lowercase letter. Strange bug. Host names should be case insensitive.

Mouse Without Borders

13 09 2011

Nice little tool which allows you to control multiple (up to four) computers with one keyboard and mouse, including Copy&Paste support between these machines.

This is a very cool alternative to using Remote Desktop when you want to use the physical screens of the remote controlled machines.

Hint: If you have problems connecting the machines, make sure their hostnames can be resolved from each other. Seems to use the hostname for communication even when you specify an IP address during connect.

Windows 7 Remote Desktop Logon with empty password

11 08 2011

By default, Windows will not allow the logon over a network with a blank password.

You can disable blank password restrictions by using a policy. To locate and change this policy:

Click Start, point to Run, type gpedit.msc, and then click OK to start the Group Policy Editor.

Open Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options\Accounts: Limit local account use of blank passwords to console logon only.

Double-click Limit local account use of blank passwords to consol logon only.

Click Disabled, and then click OK.

Quit Group Policy Editor.
NOTE: By default, this policy is on (enabled).

Copied from:

Installing SQL Server Compact Edition 3.5 SP2 with ADO.NET Entity Framework locally

2 09 2010

When using SQL Server CE as a local database engine the SQL Server CE components need to be installed locally. This could easily be done using the SQL Server CE setup package provided by Microsoft. But this requires the end user to manually install the SQL Server CE .msi as a prerequisite component.

As an alternative one could create a setup bootstrapper to include and automatically run the SQL Server CE installer during setup of the custom application. But this requires additional development effort.

What I wanted was to completely include the SQL Server CE runtime components with the setup installer of my application. All components should be installed locally. I managed to solve this with the help of several blog posts, namely:

I applied a combination of the techniques described in the previous blog posts. Essentially I did the following:

  • Installed the following files from the %ProgramFiles%\Microsoft SQL Server Compact Edition\v3.5 directory to the application’s target directory. These are the files from SQL Server CE 3.5 SP2 which came with Visual Studio 2010, though the application was created using Visual Studio 2008 SP1 (targeting .NET Framework 3.5 SP1). The version number of the files is displayed as 3.5.8080.0.
  1. sqlceca35.dll
  2. sqlcecompact35.dll
  3. sqlceer35EN.dll
  4. sqlceme35.dll
  5. sqlceoledb35.dll
  6. sqlceqp35.dll
  7. sqlcese35.dll
  • Installed the following files from the %ProgramFiles%\Microsoft SQL Server Compact Edition\v3.5\Private directory to the application’s target directory. It is important to use the files from the Private directory and not from the base and Desktop directories, otherwise other problems will arise.
  1. System.Data.SqlServerCe.dll
  2. System.Data.SqlServerCe.Entity.dll
  • Added the following section to the application’s app.config file. This was taken from the before mentioned blog post.
  <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
      <assemblyIdentity name="System.Data.SqlServerCe"                            publicKeyToken="89845dcd8080cc91" 
      <bindingRedirect oldVersion="" 
  • Added the following section to the application’s app.config file. This was copied from the machine.config file of a development machine where the SQL Server CE runtime was installed. The remove tag is required to make the configuration work on machines, where this entry is already contained in the machine.config file.
    <remove invariant="System.Data.SqlServerCe.3.5" />
    <add name="Microsoft SQL Server Compact Data Provider"
         description=".NET Framework Data Provider for Microsoft SQL Server Compact"
         type="System.Data.SqlServerCe.SqlCeProviderFactory, System.Data.SqlServerCe, Version=, Culture=neutral, PublicKeyToken=89845dcd8080cc91" />
  • Done.

To figure this out it was helpful to add the following entry to the registry to enable assembly binding logging. This entry causes detailed error information to be included with the exceptions thrown when assembly binding errors occur.

  • HKLM\SOFTARE\Microsoft\Fusion\EnableLog=1 (DWORD)

This solution has been tested only on Windows XP SP3 so far. Additional steps might be required to make it work on 64-bit platforms.

Visual Studio Macro for Tab Settings

10 06 2010

I’m still dreaming of integrated support for project specific tab settings in the Visual Studio editor. This would allow me to work on my own projects with my preferred tab settings (TabSize=2, Insert Spaces) and also to work on open source projects which mostly use the default settings (TabSize=4, Insert Tabs).

As a workaround I use the following macros to quickly switch the tab settings from within Visual Studio.

Imports System
Imports EnvDTE
Imports EnvDTE80
Imports EnvDTE90
Imports EnvDTE90a
Imports EnvDTE100
Imports System.Diagnostics

Public Module TabSettings

    Dim category = "TextEditor"
    Dim language = "AllLanguages"

    Sub TabSize2_InsertSpaces()

        Dim props = DTE.Properties(category, language)
        props.Item("IndentSize").Value = 2
        props.Item("TabSize").Value = 2
        props.Item("InsertTabs").Value = False

    End Sub

    Sub TabSize4_InsertTabs()

        Dim props = DTE.Properties(category, language)
        props.Item("IndentSize").Value = 4
        props.Item("TabSize").Value = 4
        props.Item("InsertTabs").Value = True

    End Sub

End Module

Access Network Share on Windows XP or Windows Server 2003 from Windows 7

29 04 2010

Heute hatte ich das Problem, dass der Zugriff auf einen unter Windows Server 2003 R2 freigegebenen Netzwerkordner von Windows 7 aus nicht funktioniert hat (access denied). Die umgekehrte Richtung, also der Zugriff auf einen unter Windows 7 freigegebenen Ordner von Windows Server 2003 R2 aus, hat jedoch geklappt.

Das Problem lässt sich lösen, indem man unter Windows 7 den Local Group Policy Editor (gpedit.msc) startet und unter Windows Settings – Security Settings – Local Policies – Security Options die Einstellung Network security: LAN Manager authentication level auf Send LM & NTLM responses setzt.


Die Lösung habe ich hier gefunden:

EASEUS Partition Master 5.5.1 Home Edition

22 04 2010

Habe heute ein nettes, kostenloses(!) Tool gefunden, mit dem man u. a. auch Partitionen verkleinern kann: EASEUS Partition Master 5.5.1 Home Edition.


Die neue Partitionsgröße lässt sich bequem und übersichtlich über eine GUI einstellen. Anschließend muss neu gebootet werden. Dabei wird die eigentliche Operation erst ausgeführt.