Original Post
Hello,
I'm not sure I'm posting in the right place, but there wasn't really anything better suited.
So this is the thing,
I'm currently working on an application that I would really like to apply to SteamWorks when I get the beta build done in about a couple of weeks.
However, looking at their FAQ just now brought me to a statement that SteamWorks doesn't offer a built in wrapper for .NET languages to the SDK.
My project is heavily dependant on the .NET functionality in it, which brings me to ask the following few:
- Having no wrapper means that it wouldn't have support to be published through Steam at all, or would it only mean that I would have no support for the SteamWorks' functionality the SDK has to offer?
- My project is actually composed of 2 executables, one is for designing, the one done in .NET, and has no actual need of the SteamWorks' functions (except for it being the main executable that I would need to be the one opened by Steam when it's clicked to play), and the other is a native application that should be able to incorporate SteamWorks' API in it, and in which they are needed.
The question being, will it be possible to support running of the .NET application from the Steam menu using this? And will it be possible to boot the other executable that utilizes the API through this .NET application, and still maintain support from SteamWorks?
Again, I don't know if this is the right place, but I'm just hoping there might be some people around here that actually have access to SteamWorks, that can help and answer my question? SteamWorks' site has no support page, so there's no where I can ask this there =\
Thank you very much for your time to reading and acknowledging my problem.
I'm not sure I'm posting in the right place, but there wasn't really anything better suited.
So this is the thing,
I'm currently working on an application that I would really like to apply to SteamWorks when I get the beta build done in about a couple of weeks.
However, looking at their FAQ just now brought me to a statement that SteamWorks doesn't offer a built in wrapper for .NET languages to the SDK.
My project is heavily dependant on the .NET functionality in it, which brings me to ask the following few:
- Having no wrapper means that it wouldn't have support to be published through Steam at all, or would it only mean that I would have no support for the SteamWorks' functionality the SDK has to offer?
- My project is actually composed of 2 executables, one is for designing, the one done in .NET, and has no actual need of the SteamWorks' functions (except for it being the main executable that I would need to be the one opened by Steam when it's clicked to play), and the other is a native application that should be able to incorporate SteamWorks' API in it, and in which they are needed.
The question being, will it be possible to support running of the .NET application from the Steam menu using this? And will it be possible to boot the other executable that utilizes the API through this .NET application, and still maintain support from SteamWorks?
Again, I don't know if this is the right place, but I'm just hoping there might be some people around here that actually have access to SteamWorks, that can help and answer my question? SteamWorks' site has no support page, so there's no where I can ask this there =\
Thank you very much for your time to reading and acknowledging my problem.