The AssemblyName class can parse the assembly name for you, just pass in the string to its constructor. If you have an assembly qualified type name, I think you’ll have to strip of the type part of the string first (ie everything up to the first comma).
No. Not from explorer. It is an intentional move by Microsoft (although I dislike it). You can from powershell though: [Reflection.AssemblyName]::GetAssemblyName(‘full-path-to\xxxx.dll’).Version Also if file version is not explicitly set it will default to assembly version. Here is some info: http://all-things-pure.blogspot.com/2009/09/assembly-version-file-version-product.html
You can share an AssemblyInfo.cs file between all projects in the solution. This shared file should contain the version numbers. To share it, you must use Add Existing File in VS and select Add as Link in the file dialog. Every project has its private and the shared AssemblyInfo.cs. The private one still contains the … Read more
One more thing. When you don’t use the referenced DLL in your code at all, it will ignore the CopyLocal and won’t copy it to your output directory.
I looked through the ASP.NET MVC 2.0 source code and looked up how AreaRegistration.RegisterAllAreas(); is implemented. This line is usually put into the Global.asax Application_Start() method and internally it scans all Assemblies for types that implement the AreaRegistration abstract type. This is kinda the behaviour I’m after. It appears RegisterAllAreas() makes a call to BuildManager.GetReferencedAssemblies(), … Read more
Answer quoted by lubos hasko is good but it doesn’t work for 64-bit assemblies. Here’s a corrected version (inspired by http://apichange.codeplex.com/SourceControl/changeset/view/76c98b8c7311#ApiChange.Api/src/Introspection/CorFlagsReader.cs) public static bool IsManagedAssembly(string fileName) { using (Stream fileStream = new FileStream(fileName, FileMode.Open, FileAccess.Read)) using (BinaryReader binaryReader = new BinaryReader(fileStream)) { if (fileStream.Length < 64) { return false; } //PE Header starts @ 0x3C … Read more
C#: are there any guidelines, best practices when it comes to dividing a solution up into name-spaces and assemblies? For guidelines for namespaces, read the framework design guidelines. For assemblies: an assembly is by definition the smallest independently versionable unit of self-describing shippable functionality in .NET. Are there parts of your software that you intend … Read more
Let’s throw the specific answer up here in case someone comes along later. From article here. Select one of the two assemblies under project references (in my case I selected Castle.Core). Hit F4 to bring up properties and enter alias CastleCore At the top of the problematic cs file put extern alias CastleCore; Reference your … Read more
I had this exact same issue using MVC4 with Ninject built for .Net 4.5 To fix this i had to add a binding redirect to my Web.config file: (at the end of the file, just before the </configuration> tag) <runtime> <assemblyBinding xmlns=”urn:schemas-microsoft-com:asm.v1″> <dependentAssembly> <assemblyIdentity name=”System.Web.Helpers” publicKeyToken=”31bf3856ad364e35″/> <bindingRedirect oldVersion=”1.0.0.0-2.0.0.0″ newVersion=”2.0.0.0″/> </dependentAssembly> <dependentAssembly> <assemblyIdentity name=”System.Web.Mvc” publicKeyToken=”31bf3856ad364e35″/> <bindingRedirect … Read more
I’ve achieved the same results using the GAC in the past, but you should question your reasons for having to reference more than one version and try to avoid it if possible. If you must do it, a binding redirect may help in your case. Also, have you read this yet?