what I meant was anything written is bound to be used for ASP.NET
what I meant was anything written is bound to be used for ASP.NET
Ai cannot think of a single worse thing in .net than ASP
RI can
Rwinforms
R:)
Aah
i see what you mean
in that case
yes
i see what you mean
in that case
yes
Lwinforms is fine to work with tbh
Laside from Mono's shit cross-platform impl of it
Aplus
Rohhhkay
Ayou can make a damn table with it
Llike from a developers perspective winforms is simple
Rwinforms is fine
Rif you use it in C#
Rbut
Rwinforms + VB
Awhy is it so hard to make a damn table in other libraries
AEWWWW VB
Nvisual basic is generally bad
Lfor audio i just use the really nice ManagedBass bindings
Rbut WinForms + VB is especially bad
Lim not commertial so i can use it for freeeee
Rbecause the VB compiler turns all WinForms forms into singletons
Nmanagedbass is actually really good but my goal is to not use restrictive licenses
Afixed the sentence for youbut WinForms +VB is especially bad
Nunfortunately im writing for commercial use 
Lall the good easy audio libraries are paid pretty much
Lat least for C#
Nopenal seems okay-ish
ANbut then you have to supply your own audio file readers
LOpenAL doesnt handle file loading
Lyeah
RHonestly I just stick to vorbis and WAV for my in-game audio
ROnly two file formats I need
NI'm looking into supporting just wav, mp3 and vorbis
Nsince those are the most commonly used
Li cant do that, i have to support a multitude of file formats that the user shoves in
RWhich means it's trivial to use a vorbis library and a simple custom-written WAV importer
Naac, aiff, wma 
Ndon't forget every audiophile's favorite
Nflac
Rm4a
Aflac has good reason to exist
Rat3
Rbecause sony
Nthere's no reason to support flac inside a game engine tbh
Nyou just get better sounding audio but at the cost that its probably more costly to decode that format
Aflac will sound no different to wav
RA lot of the big engines are just going to decode and re-encode into an optimized format anyway
