What happened to the .Net API Kit?
Hmmmm... I have the .Net API in production use so I'm a little concerned about the critical bug issue, can you elucidate?
The porting of one of the other solutions does rely on the .Net dev understanding the source language and idioms well. It's a disappointing development.
The main problems are that it doesn't deal with ampersands and UTF-8 properly, so for example it is not possible to set a UTF-8 title using .net or add a ampersand to a title or description.
Please Help me .I am not able to use your .Net API kit to upload video directly to your server.Please Help me as soon as possible..
I 've download your .Net API Kit and want to integrate with my application.So please can you provide me any demo or example...
I couldn't get any demo on the site.
Thanks
We no longer support the .Net API kit, so I'm afraid I can't help you.
Wow, talk about bad timing. I was just about to roll out a Mindtouch extension using the .net library to a very large international car manufacturer. Now I have to redo their entire video hosting implementation for their marketing department and affiliated agencies. This is almost a deal-breaker for us.. :(
Also, it's entirely possible to parse UTF-8 and HTML entities in .net languages.
Hell, for the sake of maintaining my current epicly-large client project that was relying on it, I'd be happy to maintain the lib for you if you can give us access to the source code for it.
Hi Wes, it would be awesome if you could steward the lib for us.
I can send you all of the kit kit as we have it in our SVN if you send me a mail to remco [at] our domain name.
It will probably be best to subsequently host the code on a service like google code.
Hello,
Did anything come of Wes's offer to maintain the .NET API kit? I was just evaluating BOTR for our firm and our developers all work in .NET...
Yes, there is an unofficial .Net kit in which the urgent issues are fixed here: https://github.com/bitsontherun/botr-api-dotnet
We discovered that the kit contained a number of critical bugs that made it impossible to support. Given that we have no .Net developer inside the Bits on the Run team and that the kit is used very little, we have decided to discontinue the kit.
For a .Net developer that is familiar with this kind of material it will be better to port one of our bug-free implementations than to start with the buggy kit that we had before.