That seems like kind of an odd question. Of course I can think of reasons why it should not be done (you could spend time on other things, you like Java better than .NET, etc.), about as easily as I can think of reasons why it should be done. Whether any of those are relevant to you or not is a completely different question. :)
FYI, when I did some .NET work a few years ago, I was not impressed with the state of the .NET equivalent of the Java Collections Framework, upon which JUNG (obviously) heavily depends (and the third-party library I used-Power Collections, IIRC-wasn't that much of an improvement). If it's still that bad, that might cause you some problems.
Joshua
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I was thinking of doing a JUNG port to .NET. Can anyone think of a reason why this should not be done?
Matt:
That seems like kind of an odd question. Of course I can think of reasons why it should not be done (you could spend time on other things, you like Java better than .NET, etc.), about as easily as I can think of reasons why it should be done. Whether any of those are relevant to you or not is a completely different question. :)
FYI, when I did some .NET work a few years ago, I was not impressed with the state of the .NET equivalent of the Java Collections Framework, upon which JUNG (obviously) heavily depends (and the third-party library I used-Power Collections, IIRC-wasn't that much of an improvement). If it's still that bad, that might cause you some problems.
Joshua