oscWorldOfWarcraft Releases Rss Feed

Updated Release: Release v2.2b (Apr 27, 2013)

KaelumYodi — Sat, 27 Apr 2013 17:08:48 GMT

This is a minor update to include subclass data that wasn't properly documented. Plus, I added the WPF Application that I use to test the code, for those who would like to take a test drive.

If you discover any issues with this release, please check the existing Discussions to see if the issue has already been reported, and if not, create a new discussion with the details of the issue.

Released: Release v2.2b (Apr 27, 2013)

Sat, 27 Apr 2013 17:08:48 GMT

Updated Release: Release v2.2b (Apr 27, 2013)

KaelumYodi — Sat, 27 Apr 2013 17:07:04 GMT

This is a minor update to include subclass data that wasn't properly documented. Plus, I added the WPF Application that I use to test the code to make easier for those who just want to try things out.

If you discover any issues with this release, please check the existing Discussions to see if the issue has already been reported, and if not, create a new discussion with the details of the issue.

Updated Release: Release v2.2a (Feb 18, 2013)

KaelumYodi — Mon, 18 Feb 2013 17:45:14 GMT

This is a minor bug fix to correct the data type of a few the expertise fields in character stats. I also found some undocumented additions/changes to this object that were also updated.

If you discover any issues with this release, please check the existing Discussions to see if the issue has already been reported, and if not, create a new discussion with the details of the issue.

Released: Release v2.2a (Feb 18, 2013)

Mon, 18 Feb 2013 17:45:14 GMT

Updated Release: Release v2.2 (Dec 28, 2012)

KaelumYodi — Sat, 29 Dec 2012 00:30:59 GMT

This is a minor update to reflect recent changes made by Blizzard, and minor refactoring changes to a few objects for consistency. Blizzard hasn't updated their documentation as of writing of these release notes, but the changes are related to battle pets and character items. Please read the Community Platform API forum for more information.

If you discover any issues with this release, please check the existing Discussions to see if the issue has already been reported, and if not, create a new discussion with the details of the issue.

Released: Release v2.2 (Dec 28, 2012)

Sat, 29 Dec 2012 00:30:59 GMT

Updated Release: Release v2.1 - Mists of Pandaria (Oct 20, 2012)

KaelumYodi — Sat, 20 Oct 2012 22:52:48 GMT

This release supports all of the new API features and changes that come with the Mists of Pandaria release. None of the previous method calls have changed, though some of the response objects have, as Blizzard made some changes to the response objects. Some objects were either removed, or renamed and their purpose slightly changed. Read the Community Platform API release notes MoP Changes to determine what has changed.

If you discover any issues with this release, please check the existing Discussions to see if the issue has already been reported, and if not, create a new discussion with the details of the issue.

Released: Release v2.1 - Mists of Pandaria (Oct 20, 2012)

Sat, 20 Oct 2012 22:52:48 GMT

Updated Release: Release v1.4 (Mar 25, 2012)

KaelumYodi — Tue, 09 Oct 2012 01:34:08 GMT

This release includes the recipe API, new 'Raw' versions of all the API calls, dual access enums in several of the data objects, and significant internal refactoring. Existing applications based on the previous library should work as they are without any changes. The 'Raw' versions of all the method calls only return the JSON response as a string. They should be used when you don't need to do any processing in your .NET code and just need to pass it to the javascript on your page.

If you discover any issues with this release, please check the existing Discussions to see if the issue has already been reported, and if not, create a new discussion with the details of the issue.

Released: Release v1.4 (Mar 25, 2012)

Tue, 09 Oct 2012 01:34:08 GMT

Updated Release: Release v2.0 (May 20, 2012)

KaelumYodi — Tue, 09 Oct 2012 01:33:51 GMT

This release replaces the JavaScriptSerializer with the DataContractJsonSerializer, which was needed to support the battleground status additions that Blizzard made to the realm status API. The JavaScriptSerializer doesn't support aliasing key names, whereas the DataContractJsonSerializer does. It also allows this library to continue to work on any system that has the 4.0 .NET Framework installed without requiring any additional libraries.

Microsoft is adding the Json.NET serializer to the ASP.NET Web Stack with its next release and this library will switch over to using the Json.NET serializer once that is released. By changing the serializer with this release, the transition to using Json.NET will be much simpler and should not require any major interface changes when it is released. The down side is that these changes have forced a significant refactoring of the previous interface, which is why I changed the release of this version from 1.5 to 2.0.

With this release, every API method call that returns a deserialized object, contains a JsonResponse property on that object, which is the raw JSON response string received from the API. Several undocumented elements were discovered in the result sets, and have been added to the response objects. A few bugs in the previous interface were discovered and fixed as well.

If you discover any issues with this release, please check the existing Discussions to see if the issue has already been reported, and if not, create a new discussion with the details of the issue.

Released: Release v2.0 (May 20, 2012)

Tue, 09 Oct 2012 01:33:51 GMT

Updated Release: Release 2.0 (May 20, 2012)

KaelumYodi — Mon, 21 May 2012 16:32:31 GMT

Released: Release 2.0 (May 20, 2012)

Mon, 21 May 2012 16:32:31 GMT

Updated Release: Release 2.0 (May 20, 2012)

KaelumYodi — Mon, 21 May 2012 05:41:28 GMT

This release replaces the JavaScriptSerializer with the DataContractJsonSerializer, which was needed to support the battleground status additions that Blizzard made to the realm status API. The JavaScriptSerializer doesn't support aliasing key names, whereas the DataContractJsonSerializer does. It also allows this library to continue to work on any system that has the 4.0 .NET Framework installed without requiring any additional libraries.

Microsoft is adding the Json.NET serializer to the ASP.NET Web Stack with its next release and this library will switch over to using the Json.NET serializer once that is released. By changing the serializer with this release, that transition to using Json.NET will be much simpler and should not require any major interface changes when it is released. The down side is that these changes have forced a significant refactoring of the previous interface, which is why I changed the release of this version from 1.5 to 2.0.

With this release, every API method call that returns a deserialized object, contains a JsonResponse property on that object, which is the raw JSON response string received from the API. Several undocumented elements were discovered in the result sets, and have been added to the response objects. A few bugs in the previous interface were discovered and fixed as well.

If you discover any issues with this release, please check the existing Discussions to see if the issue has already been reported, and if not, create a new discussion with the details of the issue.

Updated Release: Release 2.0 (May 20, 2012)

KaelumYodi — Mon, 21 May 2012 05:40:07 GMT

This release replaces the JavaScriptSerializer with the DataContractJsonSerializer, which was needed to support the battleground status additions that Blizzard made to the realm status API. The JavaScriptSerializer doesn't support aliasing key names, whereas the DataContractJsonSerializer does. It also allows this library to continue to work on any system that has the 4.0 .NET Framework installed without requiring any additional libraries.

Microsoft is adding the Json.NET serializer to the ASP.NET Web Stack with its next release and this library will switch over to using the Json.NET serializer once that is released. By changing the serializer with this release, that transition to using Json.NET will be much simpler and should not require any major interface changes when it is released. The down side is that these changes have forced a significant refactoring of the previous interface, which is why I changed the release of this version from 1.5 to 2.0.

With this release, every API method call that returns a deserialized object, contains a JsonResponse property on that object, which is the raw JSON response string received from the API. Several undocumented elements were discovered in the result sets, and have been added to the response objects. Several bugs in the previous interface were discovered and fixed as well.

If you discover any issues with this release, please check the existing Discussions to see if the issue has already been reported, and if not, create a new discussion with the details of the issue.

Updated Release: Release 2.0 (May 20, 2012)

KaelumYodi — Mon, 21 May 2012 05:38:25 GMT

This release replaces the JavaScriptSerializer with the DataContractJsonSerializer, which was needed to support the battleground status additions that Blizzard made to the realm status API. The JavaScriptSerializer doesn't support aliasing key names, whereas the DataContractJsonSerializer does. It also allows this library to continue to work on any system that has the 4.0 .NET Framework installed without requiring any additional libraries.

Microsoft is adding the Json.NET serializer to the ASP.NET Web Stack with its next release and this library will switch over to using the Json.NET serializer once that is released. By changing the serializer with this release, that transition to using Json.NET will be much simpler and should not require any major interface changes when it is released. The down side is that these changes have forced a significant refactoring of the previous interface, which is why I changed the release of this version from 1.5 to 2.0.

With this release, every API method call that returns a deserialized object also returns JsonResponse property, which is the raw JSON response string received from the API. Several undocumented elements were discovered in the result sets, and have been added to the response objects. Several bugs in the previous interface were discovered and fixed as well.

If you discover any issues with this release, please check the existing Discussions to see if the issue has already been reported, and if not, create a new discussion with the details of the issue.

Updated Release: Release 2.0 (May 20, 2012)

KaelumYodi — Mon, 21 May 2012 05:37:54 GMT

This release replaces the JavaScriptSerializer with the DataContractJsonSerializer, which was needed to support the battleground status additions that Blizzard made to the realm status API. The JavaScriptSerializer doesn't support aliasing key names, whereas the DataContractJsonSerializer does. It also allows this library to continue to work on any system that has the 4.0 .NET Framework installed without requiring any additional libraries.

Microsoft is adding the Json.NET serializer to the ASP.NET Web Stack with its next release and this library will switch over to using the Json.NET serializer once that is released. By changing the serializer with this release, that transition to using Json.NET will be much simpler and should not require any major interface changes when it is released. The down side is that these changes have forced a significant refactoring of the previous interface, which is why I changed the release version from 1.5 to 2.0.

With this release, every API method call that returns a deserialized object also returns JsonResponse property, which is the raw JSON response string received from the API. Several undocumented elements were discovered in the result sets, and have been added to the response objects. Several bugs in the previous interface were discovered and fixed as well.

If you discover any issues with this release, please check the existing Discussions to see if the issue has already been reported, and if not, create a new discussion with the details of the issue.

Updated Release: Release 2.0 (May 20, 2012)

KaelumYodi — Sun, 20 May 2012 21:25:47 GMT

This release replaces the JavaScriptSerializer with the DataContractJsonSerializer, which was needed to support the battleground status additions that Blizzard made to the realm status API. The JavaScriptSerializer doesn't support aliasing key names, whereas the DataContractJsonSerializer does. It also allows this library to continue to work on any system that has the 4.0 .NET Framework installed without requiring any additional libraries.

Microsoft is adding the Json.NET serializer to the ASP.NET Web Stack with its next release and this library will switch over to using the Json.NET serializer once that is released. Making the current serializer changes with this release will make that transition to using Json.NET much simpler. The down side is that these changes have forced a refactoring of the library's interface, thus the 2.0 release.

With this release, every API method call that returns a deserialized object also returns JsonResponse, which is the raw JSON response string received from the API. Also, several undocumented elements were discovered in the result sets, and have been added to the response objects. Several bugs were discovered and fixed during the refactoring of the library as well.

If you discover any issues with this release, please check the existing Discussions to see if the issue has already been reported, and if not, create a new discussion with the details of the issue.