15,894,132 members
Sign in
Sign in
Email
Password
Forgot your password?
Sign in with
home
articles
Browse Topics
>
Latest Articles
Top Articles
Posting/Update Guidelines
Article Help Forum
Submit an article or tip
Import GitHub Project
Import your Blog
quick answers
Q&A
Ask a Question
View Unanswered Questions
View All Questions
View C# questions
View C++ questions
View Javascript questions
View Visual Basic questions
View Python questions
discussions
forums
CodeProject.AI Server
All Message Boards...
Application Lifecycle
>
Running a Business
Sales / Marketing
Collaboration / Beta Testing
Work Issues
Design and Architecture
Artificial Intelligence
ASP.NET
JavaScript
Internet of Things
C / C++ / MFC
>
ATL / WTL / STL
Managed C++/CLI
C#
Free Tools
Objective-C and Swift
Database
Hardware & Devices
>
System Admin
Hosting and Servers
Java
Linux Programming
Python
.NET (Core and Framework)
Android
iOS
Mobile
WPF
Visual Basic
Web Development
Site Bugs / Suggestions
Spam and Abuse Watch
features
features
Competitions
News
The Insider Newsletter
The Daily Build Newsletter
Newsletter archive
Surveys
CodeProject Stuff
community
lounge
Who's Who
Most Valuable Professionals
The Lounge
The CodeProject Blog
Where I Am: Member Photos
The Insider News
The Weird & The Wonderful
help
?
What is 'CodeProject'?
General FAQ
Ask a Question
Bugs and Suggestions
Article Help Forum
About Us
Search within:
Articles
Quick Answers
Messages
Comments by TheOneTrueMongoloid (Top 6 by date)
TheOneTrueMongoloid
20-May-19 16:32pm
View
Thanks Dave. I'll give that a try. Out of curiosity, are you installing libsodium-net through the NuGet manager in Visual Studio, or are you downloading the Git Repository and manually installing?
TheOneTrueMongoloid
20-May-19 13:00pm
View
At the end of my post I had addressed why they're in the Sys32 and SysWOW64 directories. That had solved this problem for someone else, so I gave it a try and it didn't work for me. As for where libsodium is installed, I installed it through the Visual Studio NuGet manager so it installed libsodium to wherever the NuGet manager downloads them to.
TheOneTrueMongoloid
20-May-19 9:24am
View
It originally said "Any CPU" When I did the first build a few weeks ago but then I created the x86 and x64 build platforms (By copying from from ANY CPU because I didn't see any configurations other than Copy from... and <empty> which didn't seem like a good idea) and no matter if I build to x86 or x64, I still get the same error.
TheOneTrueMongoloid
20-May-19 8:54am
View
I didn't think so, but when grasping at straws... So, is there a way to tell if I'm pulling from the x64 or x86 bit versions of libsodium from the code editor? I'm still very new to software development at this level (I'm not a dev by trade, so I'm largely self-taught) and as a result, I'm sort of groping in the dark when it comes to defining whether an app is x64 or x86. I have an x86 and x64 platform build profile set up, but since I didn't see where to actually set them up, I had to use the "Copy settings from Any CPU" option when setting them up, and I don't know if that actually did anything. Google hasn't been much help in that department either. Do you have a link to an article that explains that in detail?
TheOneTrueMongoloid
20-May-19 8:45am
View
Deleted
I didn't think so, but when grasping at straws... So, is there a way to tell if I'm pulling from the x64 or x86 bit versions of libsodium from the code editor? I'm still very new to software development at this level (I'm not a dev by trade, so I'm largely self-taught) and as a result, I'm sort of groping in the dark when it comes to defining whether an app is x64 or x86. I have an x86 and x64 platform build profile set up, but since I didn't see where to actually set them up, I had to use the "Copy settings from Any CPU" option when setting them up, and I don't know if that actually did anything. Google hasn't been much help in that department either. Do you have a link to an article that explains that in detail?
TheOneTrueMongoloid
20-May-19 8:37am
View
Thanks for the info on the Visual C++ version. That makes me feel slightly better at least. Do you think completely uninstalling and reinstalling the Sodium-Core and libsodium NuGets would do anything to solve the problem?
Show More