RE: Subversion and .NET

news wrote:
> Hi
>
> Arild Fines wrote:
> [...]
>> o Managed C++ - MC++ allows us to write mixed assemblies - eg,
>> assemblies containing both managed and unmanaged code. This means we
>> can write a single DLL which links to the SVN .libs, and that
>> exposes a managed interface for consumption by managed languages.
>> This approach works equally well with both dynamic and static
>> libraries.
>>
>> Currently, we are leaning towards the last solution, but we would be
>> very interested in hearing input from other people on this. [...]
>
> If you like to hear my 2c ...

Wouldn't have asked if we didn't :-)

> I think there are two alternatives: with or without peer classes.
> I would recommend to read the following article about how the Eclipse
> team solved this problem for SWT:
> http://www.eclipse.org/articles/Article-SWT-Design-1/SWT-Design-1.html
> Just replace "widget" with SVN/APR resource (pool, token, etc.).

I have read that article before, but hadn't thought of it in this context.
It is an interesting approach.

I'm starting to think that maybe a 2 layer API would be the way to go: A
very low level API that merely maps the svn_client_* calls to managed
methods, and a higher level API on top of that modelling SVN managed
resources such as files and directories, as well as remote repositories.

--
Arild
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org