Problem in accessing Capability API

[mkmurali]

"Could not load file or assembly 'Newtonsoft.Json.Net35, Version=4.0.2.0, Culture=neutral, PublicKeyToken=30ad4fe6b2a6aeed' or one of its dependencies. The system cannot find the file specified.

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.IO.FileNotFoundException: Could not load file or assembly 'Newtonsoft.Json.Net35, Version=4.0.2.0, Culture=neutral, PublicKeyToken=30ad4fe6b2a6aeed' or one of its dependencies. The system cannot find the file specified."

Rest of the API is working fine.

[johnsheehan]

What version is the project that you're adding the reference to?

[mkmurali]

Twilio 3.1.0
Twilio.Client 3.1.0

[johnsheehan]

Is your project .NET 4 or 3.5? If it's 4, you can delete the reference and re-add it from the packages folder NuGet created.

[djenryte]

Ran into same issue today. Thanks for the fix.

[mkmurali]

I have a .NET 4 project. Deleted the reference to net40 file and added reference to net35 file. It works. Thank you.

[johnsheehan]

I'm reopening because I can fix the reference issues and this will remind me to

[drewf]

Hey John, I'm having this issue too, though removing the Nuget installed reference to the Newtonsoft .Net 4 dll and switching to the .Net 3.5 version isn't fixing the problem. It looks like Newtonsoft Json v4.0.3 is now being packaged. Easy to fix by going out and getting the older version from codeplex, but if someone needs the current version of Newtonsoft Json, it'll be trouble. Thanks!

[nSource]

I second drewf's motion. This is a problem for me.

[nSource]

By the way... Json.Net changed assembly naming conventions in recent versions, and that means the fix mentioned here no longer works (referencing the 3.5 by hand that's supplied by NuGet will now give you an error at runtime since it wants the old name, and you can't just change the file name because that breaks the assembly manifest. Maybe there's a way, but if I don't know it most other people are probably lost).

I wasn't able to rely on NuGet. To get this to work I had to go find the particular release in question and drop it in by hand. It's here: http://json.codeplex.com/releases/view/64935

This is pretty annoying and has probably turned off some people who tried to play with the Twilio client. This is my first interaction with the C# apis so I guess that includes me.

[dannycabrera]

Thanks nSource, exactly what I did. For those having issues, just need to download v4.0.2 and change the Newtonsoft.Json references to Newtonsoft.Json.Net35.dll in your twilio-csharp project. Hopefully they update the package soon.

[johnsheehan]

the next nuget version should have all the restsharp/json.net issues resolved. coming this week. thanks for your patience

[dannycabrera]

Awesome!