Implementing ICommand in OpenWrap

[Ruben Vandeginste]

Hi,

I checked how hard it would be to implement extra commands that can be
called from the openwrap-shell.
It seems one only needs to implement an "ICommand" and add the
"Command" attribute on the class.
But this doesn't seem to work.... what do I miss? How do I get the new
commands registered?

Ruben

[Sebastien Lambla]

Put them in a package in /commands and they'll be avail.

You can auto,stoically change the export name for a project by having <OpenWrap-ExportName>Commands</... In the msbuild file.

--
Seb

[Ruben Vandeginste]

Ah right... the commands folder. Now I have something extra to
complicate things... I will be using SharpSvn which requires x64 and
x86 specific dlls... is it possible to have a x64 and x86 specific
version of the commands? Or how would I go about that?

Ruben

[Sebastien Lambla]

Same as with assemblies. Commands-x86 and commands-x64. Command resolution is the same as assemblies.

https://github.com/openrasta/openwrap/wiki/Using-.net-assemblies


--
Seb

[Ruben Vandeginste]

Nice! I played with x86 and x64 specific assemblies, but how do I make
sure that they end up in the correct bin folder?
Just using the <OpenWrap-ExportName> specific for each build
configuration, I suppose?
In any case, is something to try tonight. :)

Ruben

[Sebastien Lambla]

Nope, just use the export name, the profile should detected automatically at compile time.

You can also do a cross build from the command line, aka build:msbuild;platform=x86;platform=x64, that'll do the build twice, once per target.

--
Seb