> We are a group of 3 students who are working on integrating Subversion into
> Visual Studio. NET for our final year project at Oslo University College.
> Some of you may remember the initial posts made to the list about this a
> couple of months ago. Since then, CollabNet has agreed to fill the role of
> employer for our project.
>
> After a period of exams and of doing administrative stuff related to the
> project(academia...:-|) we are now at the stage where we can actually begin
> to write some code(woohoo!). Since the addin itself is going to be written
> in C#, we need to make the Subversion client API available to .NET
> languages. We believe there are three alternatives for doing this:
>
> o SWIG - From several discussions on this list, we have received the
> impression that SWIG is the preferred way to wrap the Subversion client API.
> However, for us this approach has several disadvantages:
> - .NET/C# is not (yet?) a supported target for SWIG. This means we might
> have to implement this support ourselves, and this is probably not
> achievable within our timeframe.
FYI, the latest release of SWIG now supports C#.
Regards
William
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Mar 25 20:02:06 2003