While debugging your application in Visual Studio, you can right-click on a code where you have stopped (using breakpoint) and click “Go to Disassembly”. You can debug through native instructions. As for doing that with *.exe files on disk, maybe you could use NGen to generate native output and then disassemble it (although I never … Read more
I just had the same problem and I solved it by updating the Newtonsoft.Json to the latest version using Update-Package Newtonsoft.Json and then going to Web.config and adding: <dependentAssembly> <assemblyIdentity name=”Newtonsoft.Json” publicKeyToken=”30ad4fe6b2a6aeed”/> <bindingRedirect oldVersion=”0.0.0.0-4.5.0.0″ newVersion=”5.0.8″/> </dependentAssembly>
Resharper shadow copies assemblies for testing by default. If you turn off shadow-copy, it will run in the bin folder and the test should pass. Here are some instructions on turning it off.
It is possible to link to a shared assembly info file in VS 2010. Ashish Jain has a good blog post about it: Sharing assembly version across projects in a solution. After creating the shared assembly info file at the solution level, his instructions for linking to it from a project are: Right click on … Read more
For my scenario, I found that there was a identity node in the web.config file. <identity impersonate=”true” userName=”blah” password=”blah”> When I removed the userName and password parameters from node, it started working. Another option might be that you need to make sure that the specified userName has access to work with those “Temporary ASP.NET Files” … Read more
Versioning is something that I am very passionate about and have spent a long time trying to come up with an easy to use versioning system. From what you have already said in your question it is clear that you have understood one important point, the assembly version numbers are not synonymous with the product … Read more
http://msdn.microsoft.com/en-us/library/7314433t(v=vs.80).aspx From MSDN: In Solution Explorer, select the project. On the Project menu, choose Add Reference. The Add Reference dialog box opens. Select the tab indicating the type of component you want to reference. In the top pane, select the component you want to reference, and then click the Select button. Press CTRL while clicking … Read more
… Could not load file or assembly ‘X’ or one of its dependencies … Most likely it fails to load another dependency. you could try to check the dependencies with a dependency walker. I.e: https://www.dependencywalker.com/ Also check your build configuration (x86 / 64) Edit: I also had this problem once when I was copying dlls … Read more
[AssemblyTitle] is a pretty big deal, it is directly visible when you right-click on the assembly and use Properties + Details. An example to make it more visible. Let’s start with this AssemblyInfo.cs file: [assembly: AssemblyTitle(“AssemblyTitle”)] [assembly: AssemblyDescription(“AssemblyDescription”)] [assembly: AssemblyConfiguration(“AssemblyConfiguration”)] [assembly: AssemblyCompany(“AssemblyCompany”)] [assembly: AssemblyProduct(“AssemblyProduct”)] [assembly: AssemblyCopyright(“AssemblyCopyright”)] [assembly: AssemblyTrademark(“AssemblyTrademark”)] [assembly: AssemblyCulture(“”)] [assembly: Guid(“7da36bdf-39fb-4a4d-b98c-ecefd99b155a”)] [assembly: AssemblyVersion(“1.2.3.4”)] [assembly: … 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