Today I released two new videos providing information on how to create a RESTful web service by keeping c# as the tech stack (.NET Core) and also how to consume web services by using the UnityEngine.Networking namespace.
I also show how to use the JsonUtility to serialize and deserialize objects and debugging of both the game and web services as we run the test project.
Creating RESTful web services in .NET Core for your indie games while using Unity3d
Consuming RESTful web services in Unity3d and learn how to use the Unity Engine Networking API
I hope you enjoy it as much as I enjoyed creating the videos.
Your topics seem to be repurposed enterprise software stuff. Not so much about games, game mechanics and the Unity game engine. Consuming restful services. Jeesh. Consuming steak and ice cream. Yes.
I appreciate the feedback and yes I agree this topic is not directly about some of the areas you mentioned but I do use web services in my own games and I am sure many others do as well, I also believe it applies to unity.
Also I will definitely add more topics around the areas you suggested and I also have a lot more content in my channel in specific to what you suggested.
Consuming web services is kinda important, especially when you’re talking Unity as a general purpose rendering engine (but even still in the Unity-as-a-game-engine side). Consider this a vote that this kind of content is definitely useful.
While I agree wholeheartedly that connecting to a backend server and sending and retrieving data is essential I am not inclined to review the video as by its title it looks like yet another C# enterprise programmer winging it through Unity and is not a Unity centric headspace. By default I find these coder types to be jargon heavy and solutions shy. Unity is secondary to their knowledge of .NET core…yet Unity is a C++ engine and actively works against best practices of .NET C# programmers in its use of C# as a scripting language. Don’t let my idiosyncrasies sway your path if you are so inclined.