Two options… regardless of application type you can always invoke: Assembly.GetExecutingAssembly().GetName().Version If a Windows Forms application, you can always access via application if looking specifically for product version. Application.ProductVersion Using GetExecutingAssembly for an assembly reference is not always an option. As such, I personally find it useful to create a static helper class in projects … Read more
Using PowerShell, you can execute this statement: ([system.reflection.assembly]::loadfile(“C:\..\Full_Path\..\MyDLL.dll”)).FullName The output will provide the Version, Culture and PublicKeyToken as shown below: MyDLL, Version=1.0.0.0, Culture=neutral, PublicKeyToken=669e0ddf0bb1aa2a
To solve this, I ensured all my projects used the same version by running the following command and checking the results: update-package Newtonsoft.Json -reinstall And, lastly I removed the following from my web.config: <dependentAssembly> <assemblyIdentity name=”Newtonsoft.Json” publicKeyToken=”30ad4fe6b2a6aeed” culture=”neutral” /> <bindingRedirect oldVersion=”0.0.0.0-6.0.0.0″ newVersion=”6.0.0.0″ /> </dependentAssembly> If you want to ensure all your Newtonsoft.Json packages are the … Read more
UPDATE: I liked this question so much I made it the subject of my blog on November 18th 2011. Thanks for the great question! I’ve always wondered: what is the purpose of the stack? I assume you mean the evaluation stack of the MSIL language, and not the actual per-thread stack at runtime. Why is … Read more
Utility or helper classes/methods that you would like to access from many other classes within the same assembly, but that you want to ensure code in other assemblies can’t access. From MSDN (via archive.org): A common use of internal access is in component-based development because it enables a group of components to cooperate in a … Read more