Remote debugging from Visual Studio 2008 on a domain machine to a machine not on the domain

  • There must be a user account with the same username and password on the remote machine and the local machine (MACHINE account, not domain account).
  • Visual Studio 2008 Remote Debugger must be installed and running on the remote machine under the user account in point 1
  • Create local machine account

    1. Right click My Computer > Manage
    2. Expand Computer Management > System Tools > Local Users and Groups
    3. Right-click Users under Local Users and Groups and choose New User…
    4. Enter in the username e.g. DebugUser
    5. Enter and confirm the password
    6. Un-check “User must change password at next login” and tick “Password never expire”
    7. Click Create
    8. Click Close

    Create remote machine account

    1. Log on to the remote machine and repeat the steps for “Create local machine account”
    2. You must use the same username and password
    3. Find the user in the Users list and double-click to edit them
    4. Go to the Member Of tab
    5. Click Add…
    6. Type in Administrators and hit Enter or click OK
    7. Click OK

    Run Visual Studio 2008 Remote Debugger

    You have several options for launching the Remote Debugger.
    1. If you install Visual Studio 2008, the Remote Debugger folder can be found in %ProgramFiles%Microsoft Visual Studio 9.0Common7IDE. In the Remote Debugger folder are separate folders for the x86 and x64 versions. Perhaps the easiest solution is to share this folder over the network, allowing you to launch the debugger over the network without having to install anything on the remote machine.
    2. Alternatively, you can find the Remote Debugger setup on the first disc for the Visual Studio 2008 setup, in a sub folder called Remote Debugger.
    3. Or, you can download it from here
    It’s a good idea to run this as a Windows application as recommended by the Visual Studio 2008 Remote Debugger Configuration Wizard (and in my opinion easier to troubleshoot). At this point if you’re not logged in as the new user you created, you might want to do that now so that you can run the Remote Debugger under them. Once you’ve followed instructions for installing, run the remote debugger if it isn’t already by going to Start > Programs > Microsoft Visual Studio 2008 > Visual Studio Tools > Visual Studio 2008 Remote Debugger. It should say that it’s running an instance similar to DebugUser@RemoteMachineName

    Connect to the remote machine with Visual Studio

    1. In Visual Studio on your local machine, go to Debug > Attach to process…
    2. Make sure the Transport drop-down at the top is set to Default
    3. In Qualifier, type in the name of the Remote Debugger instance e.g. DebugUser@RemoteMachineName and hit Enter
    4. You should then see the list of remote processes in the list and can select the one you want and click Attach.
    ]]>

    Set up IP filtering in uTorrent and keep your ipfilter.dat up to date easily

    The IPFilter Updater application now has its own page: http://www.davidmoore.info/ipfilter-updater/ uTorrent is one of the most popular BitTorrent clients out there. In my opinion it’s the best. You can set up IP filtering in uTorrent to block bad seeds and peers from a list maintained by the community.

    How to set up IP filtering in uTorrent

    1. Open up uTorrent and go to Options > Preferences from the menu or click the Preferences button in the toolbar
    2. Select the Advanced option in the tree
    3. Find ipfilter.enabled in the list and make sure it’s set to true
    4. Click OK

    How to get and update the ipfilter.dat

    I’ve written a simple program that will download the ipfilter.dat from SourceForge and copy it into the file where uTorrent expects it. uTorrent IPFilter Updater [ Requires .NET 3.5 ]
    UPDATED  26 Jan 2010: Now requires .NET 3.5, and allows mirror selection
    1. Extract the files to a folder, and run IPFilter.UI.exe
    2. Wait for it to download the mirrors, select the one you want, and click Go
    3. Once the file has downloaded and extracted, you can close the window

    Enhancements

    Done:
    • Download and extract zip file to speed up the download time and minimize the download usage
    • Allow selection of mirror you want to use
    To Do:
    • Automation through command-line arguments, for scheduled tasks
    Source Code: http://github.com/DavidMoore/IP-Filter-Updater/

    How to get uTorrent to pick up the new ipfilter.dat

    You have two options:
    1. You can simply exit and restart uTorrent to load theIPFilter or
    2. You can leave uTorrent open and reload the IPFilter by selecting the Peers tab, right clicking in the list and choosing Reload IPFilter. Annoyingly you need a selected torrent for this to work.
    Looking in the Log should show a message similar to “Loaded ipfilter.dat xxxxxx entries)” Because IP ranges and addresses change often, it’s a good idea to update your filter list often too.]]>

    Could not load file or assembly ‘x’ or one of its dependencies. Strong name validation failed.

    Make sure that you check the dependencies of the assembly named in the exception message when troubleshooting. The problem may be with one of the dependencies. In my case the exception isn’t a surprise because of what’s being done to the assembly. But until I resolve that, how can I get around this for now? You can exclude an assembly from strong name validation for development purposes using the Microsoft (R) .NET Framework Strong Name Utility tool aka sn.exe: "%ProgramFiles%Microsoft SDKsWindowsv6.0Abinsn.exe" -Vr "C:PathToAssembly.dll" Make sure you change the sn.exe path depending on which version of the .NET Framework SDK you have installed. If you’re having trouble, get into the  “%ProgramFiles%Microsoft SDKsWindows” dir and search for sn.exe, and use the newest one you can find. You might find it handy to add this as a Post-build event command-line for your project from within Visual Studio in Project Properties > Build Events: "%ProgramFiles%Microsoft SDKsWindowsv6.0Abinsn.exe" -Vr "$(TargetPath)" So how do you switch the strong name validation back on for your assembly? Use the -Vu switch: "%ProgramFiles%Microsoft SDKsWindowsv6.0Abinsn.exe" -Vu "C:PathToAssembly.dll"]]>

    Disabling the Opera Bit Torrent support

    uTorrent To disable the Torrent support in Opera so that uTorrent or your default torrent client will be used instead:

    1. In Opera, type in opera:config in the address bar and hit enter
    2. Click the Bit Torrent section to expand it
    3. Untick Enable
    4. Hit Save
    5. Click OK at the message box
    You won’t have to restart Opera for this change to take effect]]>

    Configuring NLog for your application when NLog is in the Global Assembly Cache (GAC)

    <configuration> <configSections> <section name=”nlog” type=”NLog.Config.ConfigSectionHandler, NLog”/> </configSections> <nlog> </nlog> </configuration> Because you are not using the strong name for the Assembly-qualified name of ConfigSectionHandler, it’s impossible to do a GAC lookup, therefore NLog won’t be found and you’ll get an application error (even if NLog is actually in the GAC). This means your application will throw an exception when the configuration is loaded; there will be no NLog.dll in your application folder and it can’t check the GAC as it doesn’t have the strong name of the assembly you want. You can fix this by including the strong name: <section name="nlog" type="NLog.Config.ConfigSectionHandler, NLog, Version=1.0.0.505, Culture=neutral, PublicKeyToken=5120e14c03d0593c" /> ]]>

    Visual Studio: Cannot add project to source control; it overlaps a project that is already bound to source control at a lower root

    The project <ProjectName> cannot be added to source control. In folder <SolutionDir>, it overlaps a project that is already bound to source control at a lower root. To avoid this problem, add the project from a location below the binding root of the other source controlled projects in the solution. The cause of this was that I had linked files within the new project that were pointing to existing files higher up in the solution folder (in this instance, in the solution root). In this case I was linking to the strong name key from the solution root: <SolutionRoot>MyKey.snk <SolutionRoot>MyProjectMyProject.csproj <= Was linking to the key in the root To add the project to source control, you have to remove these links first, add the project to source control, then you can put your links back in.]]>