MWha
MYou mean a list that can have any type of object?
Pa
List<T> can only have TIf you really want to have a workaround you’d have to make T an
MI did not format that well
PDownside of that is you'd need runtime type checking to actually do anything useful with the item
P
LList<Any object>PList<object>Pbut as said above, that removes any and all benefits of using generics
TPiirc
List<object> is actually prefered over ArrayList :dTyes
MIndeed it is, also this is outside the scope of this post but how does the ArrayList.Sort function even work
MLike it can have different type of objects what’s it sorting based on
PWho knows 
Lnew List<object>() { "something" };no worky
L:(
MWith collection initializers you have to omit the ()
Tno you don't
PI'd like to know why you need a list with several different types in it, @Livid
Li don
MGenuinely surprising
MReading the docs it was always omitted so I assumed it was a necessity
MWhyd you ask then
L comboBox1.DataSource = new List<object>() { "something" };LError Code: CS0246 -> Description: The type or namespace name 'List<>' could not be found (are you missing a using MSystem.Collections.Generic
MAdd a using statement for that namespace
Lyay
