The screenshot below shows a file that is dirty on disk (Modified), and one that is changed but not saved to disk yet (Edited). Hitting commit will save both files and commit them as you’d expect.

The toolbar allows users to access most common operations, like update the entire solution, commit the checked files below, and perform other actions on the selected files, like diff, open in Visual Studio (double click), revert etc.

The combobox in the toolbar can be used to switch between branches and trunk.

ShareThis

The screenshot below shows NotificationHandler.cs as “Modified” meaning changes have been persisted on disk, and OutputPaneWriter.cs as “Edited” meaning it was edited, and will probably result in changes on disk when saved.

ShareThis

In 2.0 this is streamlined and also looks a lot more like other Scc providers (Visual SourceSafe/Team Foundation System) and work with the generic documentation

The command is in the File -> Open menu as shown below.

Here you get a pretty default FileOpen dialog, with the exception that you enter urls in the File name: box. (This can be any url that Subversion supports like svn:// http(s):// svn+ssh:// and file:///)

After entering an initial url, you can navigate to the solution file. This acts as a replacement for the repository explorer.

After clicking open on the sln file, the dialog below appears. Here we show a dropdown of the possible directories available for checkout, and we try to take an educated guess about which one is right (by looking at trunk/tags/branches, the top of the repository, the location of the sln file).

The local directory is the default projects directory as set in Options -> Projects and Solutions

When you hit OK, the checkout starts:

And when it finishes, the Solution is automatically opened

ShareThis

Microsoft wants this web site to become the one-stop shop for all Visual Studio extensions, from free VS PowerToys like tools to VSIP products. Any developer is able to post information and add links to their Visual Studio extensions.

We hope this brings AnkhSVN under the attention of a new group of users, and also hope to attract new developers. New developers already joined the team, one works for CollabNet (the company behind Subversion).

ShareThis

The subversion repository has been moved to http://ankhsvn.open.collab.net/svn/ankhsvn/trunk. Unlike before, anonymous access is no longer available, but you can checkout the repository using the username "guest" and a blank password. You can also browse the repository using the web interface.

Hopefully the co-operation with collabNet helps us meet new developers willing to help us out, building more community around Ankh.

ShareThis

Scott Hanselman described how to “spot-weld” new properties on existing types using the types.ps1xml file. When writing your own Cmdlets this might not be the best way to modify the objects you return. In this post I’m going into how to change existing types in code using ETS Properties based on a SharpSvn/Subversion cmdlet. A common use-case would be to fix a function that returns a string instead of a FileInfo or Uri instance (that can be passed along the pipeline).

The main trick is not to return the plain object, but a PSObject wrapping the plain object. The PSObject allows you to add and remove custom properties and methods from C# code.

This is the code before overriding propeties and extending the pipeline object

protected override void ProcessRecord()
{
    Client.Info(
        GetTarget<SvnTarget>(),
        SvnArguments,
        delegate(object sender, SvnInfoEventArgs e)
        {
            e.Detach();

            WriteObject(e);
        });
}

And its output.

Get-SvnInfo | % { $_.Path.GetType() }

IsPublic IsSerial Name        BaseType
-------- -------- ----        --------
True     True     String      System.Object

SvnInfoEventArgs has a Path property of type String. For a Cmdlet it’s more usual to write FileInfo objects to the pipeline, so we need to remove the original Path property, and provide a new one.

The properties/methods that seem to make most sense here are:

• CodeProperty/CodeMethod
  Allows you to write C# code behind a new property or method, this is the most flexible, and can only be added from C# code. In PowerShell you would write a ScriptProperty or ScriptMethod instead, implementing it in PowerShell.
• AliasProperty
  Exposes an existing property with another name, nice for creating a consistent PowerShell API on top of a non-existing API
• NoteProperty
  This is just a readonly Key/Value
   

Adding a new property with the same name overrides the existing one

protected override void ProcessRecord()
{
    Client.Info(
      GetTarget<SvnTarget>(),
      SvnArguments,
      delegate(object sender, SvnInfoEventArgs e)
      {
          e.Detach();

          PSObject obj = new PSObject(e);
          obj.Properties.Add(new PSCodeProperty(
              "Path",
              GetType().GetMethod("GetPath")));

          WriteObject(obj);
      });
}

public static FileInfo GetPath(PSObject obj)
{
    SvnInfoEventArgs e = obj.BaseObject as SvnInfoEventArgs;
    if (e == null)
        return null;

    return new FileInfo(e.Path);
}

The method represented by MethodInfo has to be public, static, non-void and take one parameter of type PSObject to work.

This overrides the Path property:

Get-SvnInfo | % { $_.Path.GetType() }

IsPublic IsSerial Name          BaseType
-------- -------- ----          --------
True     True     FileInfo      System.IO.FileSys...

If you have “spot-welded” on extra properties on FileInfo, those will also be present on $_.Path ofcourse.

ShareThis

Visual Studio 2008 can also be configured to use a Symbol Server that provides source server indexed PDBs for debugging through the .NET Framework source code. SourceServerSharp enables you to produce PDBs for your own assemblies with similar possibilities.

1) Install Subversion Command-line binaries and make sure svn.exe is in the path. This happens automatically when you use the installer.

2) Configure source server inside Visual Studio 2005 or 2008:

• Turn off ‘Enable Just My Code (Managed only)’
• Turn on ‘Enable source server support’

3) You are now set-up, but when you are debugging and step into code outside your solution that is source server indexed, or hit an exception in that code, the following dialog comes up:

To prevent this create a file called srcsrv.ini in %ProgramFiles%\Microsoft Visual Studio 8\Common7\IDE\ containing:

[trusted commands]
svn.exe export

ShareThis

Cabarc to create new cabinet containing the patched files:

CabArc.exe n mypatch.cab c:\patch\*.dll

MsiFiler to correct version information:

MsiFiler.exe -d myinstaller.msi -v -s c:\patch\

MsiDb to insert new cabinet in msi (optional):

MsiDb.exe -d myinstaller.msi -a mypatch.cab

Open myinstaller.msi in Orca and:

• Insert a new Guid into PackageCode because we are changing the msi
  To do this in Orca, go to ‘View ->  Summary Information’ and click the ’New GUID’ button next to the Package Code. It’s also possible to configure Orca to always change the PackageCode when saving, under ‘Options -> Database’
• Insert a new Guid into ProductCode to allow major upgrade
• Change the ProductVersion to a higher version number, and change the Upgrade table accordingly.
• Change sequence in the File table for the patched file(s)
• Add reference to mypatch.cab in Media table:
  • DiskId should be a new unique number
  • Cabinet should be ’#mypatch.cab’ because the cabinet was inserted in the msi.
    It’s also possible to keep the cabinet file external, in that case call it ‘mypatch.cab’
  • LastSequence should correspond to the highest sequence number of the file in the File table
    For example, if the highest number before patching is 72, and we added 3 files, LastSequence should be 75, and 3 entries in the File table should use Sequence 73, 74 and 75. LastSequence and Sequence is the only link between files and cabinets

 Orca, MsiDb, MsiFiler and CabArc are all part of the Windows Platform SDK

ShareThis

ShareThis

This action uploads any image file that you feed into it. Don’t bother to set the title, description and tags, because it extracts them from the metadata in Lightroom (do set them there ofcourse)

 

If you start Automator.app you should see ‘Flickr’ under ‘Applications’, and in Flickr an ‘Upload to flickr’ action that takes images files.

 

I created a workflow that consists of the following steps:

1. Get folder contents
2. Filter Finder items (whose file type is JPEG image)
3. Upload to Flickr
4. Move to Trash (because I export them from RAW, and don’t need to keep the jpegs around after uploading)

Save this workflow as a plug-in (Command,Shift,S) and select Folder Action.

Select and/or create a folder where you will export your jpegs.

 

Then in Lightroom go to File - Export. 

Select the destination folder your you selected for the Folder Action.

I changed my file naming template to ‘custom settings’, and used (Title)-(Orginal File Name), but you can choose anything.

Set the other settings to what you like, and then select ‘Preset -> Save as new preset’ at the top of this dialog. I named mine ‘Upload to Flickr’

 

I clicked ‘Export’ and then there was a problem; the folder action came up after the first image was put up, instead of waiting until all where exported. To solve this I added a ‘wait for user input’ step in front of the first step in automator. Suggestions for a more elegant solution welcome

ShareThis