-
Notifications
You must be signed in to change notification settings - Fork 909
SteamAuth 2.0.0 issue #1115
Comments
I will try to go over it now and find the issue. I believe it is to do with referencing the SteamAuth DLL. Sorry for the inconvenience that I have caused. |
Next pull should hopefully fix the current issues. I accidentally updated the wrong number but now it should all work. |
@nightfuryninja Ok perfect, i will test that and tell you if this is issue is resolved or not. |
@greggameplayer Here is my private repo: https://github.com/nightfuryninja/SteamBot . Seeing as the pull request has not been merged yet, can you test this one for me? (I am not using VS2013) I just need to see if the pull I have actually made does work properly for everyone. |
Currently, you will have to install the SteamAuth package version 2.0.0 using NuGet Package manager. I will try to update to the Latest one but I have found there to be a removal of a line of code that is used in Steam Bot which causes compile errors. SteamBot also uses a different version of Newtonsoft JSON, so one will either need to be updated or backdated. |
@nightfuryninja ok I'm going to test your repo |
@nightfuryninja NuGet Client 2.12 version is required in order to get Newtonsoft.Json 11.0.1. currently the NuGet version is 2.8.60717.93. |
You need to compile it twice. There is an issue going on that I have no idea why. If not, can you tell me the version of visual studio you are using? |
@nightfuryninja No it's do that no matter the number of compilation |
@nightfuryninja The NuGet Client version and NuGet version are not the same that the problem |
I think you need to either update you NuGet Version https://stackoverflow.com/questions/42045536/how-to-upgrade-nuget-in-visual-studio-2013 or completely update to a newer version of Visual Studio. I could not change the version as SteamAuth requires that latest version of Newtonsoft JSON. Until I find a fix for this (I have posted on Stack Overflow and I am just waiting for a reply) you may have to use a newer version. |
@nightfuryninja I have verify my NuGet Version and it's above 2.12 |
@nightfuryninja so what is the problem ? |
@nightfuryninja I'm gonna do the Update 5 of vs 2013 and see if it's change anything |
The .dll "SteamAuth" is required for login and trade confirmation. Recently SteamAuth was updated to use JSON v 11.0.1, so SteamBot required updating to that version which I had done. However, it keeps giving off that error of "Wrong nuget version". I posted it onto stack overflow and I am waiting to see if anyone knows how to fix it. |
@nightfuryninja ok, the error appear also on the others VS versions ? |
Sadly, yes. This issue has been getting rather irritating now. But I am slowly beginning to make progress. |
@nightfuryninja ok |
Same problem, no way to compile it. |
https://github.com/nightfuryninja/SteamBot-1 - My repo here was updated for .NET 4.6.1 and no longer has package issues (As it was entirely reworked with the core files being re-added). The main issue that you should be having is that Newtonsoft.json has to different versions wanting to be used. To fix that just update the Newtonsoft.json |
Sooo... in conclusion. What do I have to do to fix the problem? |
@greggameplayer Is there a reason to use SteamAuth 2.0.0? I am using 3.0.0 and have no problems. |
@TimoKruth you comment an issue which was written in March |
This issue can be closed for reference to anyone else with the issue. It was fixed with SteamAuth 3.0.0 which I uploaded (there was a lot wrong with this project and conflicts with NuGet Packages). It was secretly changed without consideration for Steam-Bot I believe. But please close the issue as it should no longer exist with SteamAuth 3.0.0. |
@greggameplayer ok, because it is still open I can't know if it is still relevant. |
Can you guys please help me compiling ? is it still working ? |
There is some issue with this SteamAuth version because visual studio express 2013 can't find the steamauth, but the steamauth is downloaded on correct location. so I can't compile
The text was updated successfully, but these errors were encountered: