Skip to content

Conversation

mattleibow
Copy link
Contributor

  • Added Xamarin.iOS (Unified API)
  • Updated MonoTouch (Classic API)
  • Changed MonoDroid to Android as this is more correct and supports the newer build/projects

 - Added Xamarin.iOS (Unified API)
 - Updated MonoTouch (Classic API)
 - Changed MonoDroid to Android as this is more correct and supports the newer build/projects
@mattleibow
Copy link
Contributor Author

Just updated the project files to the latest format for Xamarin platforms. We are doing an update on the 5th of Jan and it would be great if we could just pull down this repo and build. Also, even better, if you package these assemblies into the NuGet. Then we can use those.

@hallem
Copy link
Member

hallem commented Jan 6, 2015

Matt can you send me a detailed description of what the removals were for either her or in a separate email? I just want to make sure I completely understand what you did before I merge everything in. This isn't an area of expertise for me so I need to be careful.

@hallem hallem added the inquiry label Jan 6, 2015
@mattleibow
Copy link
Contributor Author

no Prob,

The removals were two parts:

  • the old solution files: RestSharp.MonoDroid.sln and RestSharp.MonoTouch.sln are now in the RestSharp.Xamarin.sln solution.
  • the duplicate code "ResponseStatusExtensions.cs" are just copies of the same file in the RestSharp/Extensions directory. I just deleted the copies and use the one in the main directory.

The major changes in the MonoTouch project file was just because the file was quite out of date.

Hope this helps.

hallem added a commit that referenced this pull request Jan 16, 2015
Added and updated the Xamarin projects
@hallem hallem merged commit d72d3a7 into restsharp:master Jan 16, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants