w35

All my plugins and callouts will be updated soon if they aren't conformant now. As far as I see they conform to most of this specification. BTW great idea :)

Yes, It was. As of 0.36 or even 0.34 its no longer memeber of Ped but instead a member of ped.inventory In 0.33 it was marked as deprecated as far as I recall.

Greetings form Poland then :) I'm web developer (that's my specialisation, also in back-end - PHP, MySql etc. ) but I like more Windows development (as of my preference), also I'm doing some coding for Windows, for living. In recent years I was more involved in more coding for Web, though. As of referenced external dll's I must completly agree. Just wanted to add some information of special case - getting version of self referenced assembly, so people don't get it as general rule, in topic of getting assembly version. However topic is about getting external assemblies versions, so that was my 2 cents, and thats it.

Frankly speaking I would not use this for referenced external dll without checking its existence - if its missing in assembly path, I would get NullReferenceException or the like. Sell referencing with use of typeof, on class from the same assembly itself, that's the only use of this in this case I might think of. Refrection is quite new, but very important part of .NET langauages, it gives .NET lanuages more flexibility and simplicity in syntax known from C/C++, and more abilities. In c/c++ getting self reference in similar way, or type casting was available for many years ago. I have experience in .net coding at least a few years back, also native languages, in short - everything what was needed to get that basic level degree in Computer Science in my country. Looking at your code you have posted, you're also person with formal IT education I guess. For example this code : might be handy

I thought so. I use it this way Version ver = typeof(MY_ALREADY_LOADED_SELF_CHECKING_DLL_CLASS).Assembly.GetName().Version To get self-reference to my dll, and then get its assembly properies (version). Its more C/C++ way a bit.

I completly agree, but what if you're checking version using Assembly.getName().Version, on assembly from inside its code, I mean on-self checking version of assembly, It should not load twice, as its already loaded ?

@Albo1125 - Your Amazing work has been awarded now - its good to see that, greetings, and congratulations. What else can I say. And keep up the good work. :)