this means that provided you know OpenGL already you can just read one document describing how the magic structs work and instantly know how to use Silk.NET
i see, i just checked the github project page as well and noticed a lot about SilkTouch, plus i just read more about it on the blog posts, it sounds really cool and i hope more people use silk.net
Hello everyone. I have recently discovered Silk.NET and decided to check it out. I'm using Fedora 36 and I have installed .NET manually from here https://dotnet.microsoft.com/en-us/download/dotnet/6.0 I am currently trying to sharpen my C# skills by making a game that would run on at least windows, linux and android. So far, building and running Hello Window tutorial on linux worked like a charm (and i would imagine running it on windows shouldn't be a problem either), however there are a few oddities when it comes to android.
.NET 6.0 downloads for Linux, macOS, and Windows. .NET is a free, cross-platform, open-source developer platform for building many different types of applications.
So far, I've resolved this by adding <EmbedAssembliesIntoApk>true</EmbedAssembliesIntoApk> into csproj file, but it bloats the apk size to 94 megabytes. It doesn't fix the crashes, however.
For some reason, it needs BLUETOOTH_CONNECT permission? Adding <uses-permission android:name="android.permission.BLUETOOTH_CONNECT" /> to AndroidManifest.xml and then manually enabling it in the settings on my phone resolved the crashes and made the app run properly. But why? And also, how can i resolve missing assemblies error without bloating the app size?
Please keep in mind that I've never used dotnet without visual studio before and that I'm fairly new when it comes to crossplatform C# development in general, thanks c:
Also keep in mind that I've slightly modified the AndroidDemo project. I've included the archive bellow, just in case, but my changes only consist of adding a few lines to csproj and android manifests, and replacing Silk.NET project references with package references from nuget.
both of these issues you can't resolve really, you can attempt to reduce the size issue by enabling linking but fundamentally you kinda need assemblies to run a .NET application!