yeon
yeon
CC#
Created by yeon on 3/28/2025 in #help
✅ Dependency restores to incorrect package
Thanks again!
136 replies
CC#
Created by yeon on 3/28/2025 in #help
✅ Dependency restores to incorrect package
Yeah, splitting folders resolves the issue, I guess I'll resort to this for now
136 replies
CC#
Created by yeon on 3/28/2025 in #help
✅ Dependency restores to incorrect package
Hmm, the link is private for me
136 replies
CC#
Created by yeon on 3/28/2025 in #help
✅ Dependency restores to incorrect package
And I thought the CMake alone is enough headache lol
136 replies
CC#
Created by yeon on 3/28/2025 in #help
✅ Dependency restores to incorrect package
Thanks a lot for telling me about this 🙂
136 replies
CC#
Created by yeon on 3/28/2025 in #help
✅ Dependency restores to incorrect package
Hmm, I think I should mess around this out myself
136 replies
CC#
Created by yeon on 3/28/2025 in #help
✅ Dependency restores to incorrect package
Is this the one you've explained?
136 replies
CC#
Created by yeon on 3/28/2025 in #help
✅ Dependency restores to incorrect package
136 replies
CC#
Created by yeon on 3/28/2025 in #help
✅ Dependency restores to incorrect package
Hmm
136 replies
CC#
Created by yeon on 3/28/2025 in #help
✅ Dependency restores to incorrect package
It's a C++ binding, which has some size_t parameters
136 replies
CC#
Created by yeon on 3/28/2025 in #help
✅ Dependency restores to incorrect package
That's why I did this
136 replies
CC#
Created by yeon on 3/28/2025 in #help
✅ Dependency restores to incorrect package
I haven't figure out how the library user can defineconstant on the referenced project without modifying the referenced project
136 replies
CC#
Created by yeon on 3/28/2025 in #help
✅ Dependency restores to incorrect package
Thanks for explaining, it looks pretty handy
136 replies
CC#
Created by yeon on 3/28/2025 in #help
✅ Dependency restores to incorrect package
Because I didn't know that
136 replies
CC#
Created by yeon on 3/28/2025 in #help
✅ Dependency restores to incorrect package
Ugh, I need to reference the source code outside of the folders then
136 replies
CC#
Created by yeon on 3/28/2025 in #help
✅ Dependency restores to incorrect package
Hmm, should I create a seperate folders for each csproj s then?
136 replies
CC#
Created by yeon on 3/28/2025 in #help
✅ Dependency restores to incorrect package
Maybe I should just do it without seperate nuget packages for each configuration? But the code compiles quite differently depending on the constant, some internal class even doesn't exist in some configurations
136 replies
CC#
Created by yeon on 3/28/2025 in #help
✅ Dependency restores to incorrect package
Yep, after dotnet build NalchiSharp.sln, all the *.deps.json points to the same sub project: GnsSharp.Gns.Win32.dll
136 replies
CC#
Created by yeon on 3/28/2025 in #help
✅ Dependency restores to incorrect package
Still, only the Posix64 is restored this way?
136 replies
CC#
Created by yeon on 3/28/2025 in #help
✅ Dependency restores to incorrect package
Directory: D:\...\NalchiSharp\NalchiSharp\obj

Mode LastWriteTime Length Name
---- ------------- ------ ----
-a--- 2025-03-28 오후 8:33 3007 NalchiSharp.Steamworks.Posix64.csproj.nuget.dgspec.json
-a--- 2025-03-28 오후 8:33 1592 NalchiSharp.Steamworks.Posix64.csproj.nuget.g.props
-a--- 2025-03-28 오후 8:33 150 NalchiSharp.Steamworks.Posix64.csproj.nuget.g.targets
-a--- 2025-03-28 오후 8:33 5959 project.assets.json
-a--- 2025-03-28 오후 8:33 638 project.nuget.cache
Directory: D:\...\NalchiSharp\NalchiSharp\obj

Mode LastWriteTime Length Name
---- ------------- ------ ----
-a--- 2025-03-28 오후 8:33 3007 NalchiSharp.Steamworks.Posix64.csproj.nuget.dgspec.json
-a--- 2025-03-28 오후 8:33 1592 NalchiSharp.Steamworks.Posix64.csproj.nuget.g.props
-a--- 2025-03-28 오후 8:33 150 NalchiSharp.Steamworks.Posix64.csproj.nuget.g.targets
-a--- 2025-03-28 오후 8:33 5959 project.assets.json
-a--- 2025-03-28 오후 8:33 638 project.nuget.cache
136 replies