assemblies

I get a 404 HTTP status error (not found) on a specific WebResource.axd call inside an ASP.NET 3.5 (AJAX) web application. I guess the error is thrown because a specific referenced assembly is missing in the bin folder/GAC. But I don't know which, since the page which requests the resource is very complex (I'm using third-party controls and ASP.NET Ajax.) Is it possible to know from the encrypted "d" querystring parameter of the query, like: .../WebResource.axd?d=... which assembly should create the content and is possibly missing? Note: There are other WebRequest.axd calls which execute with

I'm trying to use the HTTP functions contained in the System.Web.dll assembly. However, whilst the dll seems to exist in the same directory as every other dll Visual Studio 2010 references in my project, it fails to link in and raises a warning - "The referenced component 'System.Web' could not be found". The dll, however, is definitely there within the same folder as all others referenced by the project and selecting it in 'browse for reference' mode allows me to add it - it then fails to fill in the 'Path' property. Am I doing something wrong? How can I make System.Web available in my

I know how to load an assembly from a filename, and also from the GAC. As My .msi file will put a dll project into the GAC, I'm wondering if it's possible to load it from the GAC unknowing the FullName (I mean just with the assembly name, or even the dll filename), because I have to Load this assembly from another project. Here is a piece of code that allows to do this, and an exemple: string path = GetAssemblyPath("System.DirectoryServices"); Assembly.LoadFrom(path); Note if you need a specific processor architecture, since it supports partial name, you can write this kind of things: // load

I'm trying to get Maven working with ProGuard. What I want to achieve is the following: Run ProGuard over my source files and produce obfuscated classes Create a manifest file that references the main class so that I can execute it as a jar Unpack all of the associated library jars and create one huge jar containing them all. This file should only contact .class and .xml files only. Assemble them into .zip and tar.gz files that include various README.txt files and so on. So far I've got something like this: <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-jar-plugin<

I'm starting deployment of my web application and I need to guarantee that all the assemblies that are going to be deployed were built using Release configuration. Our system was developed using C#/.Net 3.5. Is there any way to achieve this? David Check this . The idea is that you get the list of assembly attributes using Assembly.GetCustomAttributes() and search for DebuggableAttribute and then find if such attribute has IsJITTrackingEnabled property set. public bool IsAssemblyDebugBuild(Assembly assembly) { return assembly.GetCustomAttributes(false).OfType<DebuggableAttribute>().Any(da => da

Is there a Microsoft tool to get the assembly version of a DLL file from a command line? (I know that I can code my own tool.) OregonGhost This is an area where PowerShell shines. If you don't already have it, install it. It's preinstalled with Windows 7. Running this command line: [System.Reflection.Assembly]::LoadFrom("C:\full\path\to\YourDllName.dll").GetName().Version outputs this: Major Minor Build Revision ----- ----- ----- -------- 3 0 8 0 Note that LoadFrom returns an assembly object, so you can do pretty much anything you like. No need to write a program. If you use mono and linux,

I am getting very confused between Namespaces and Assemblies. Are System.Data and System.Web Namespaces or Assemblies? I have noticed these are called namespaces and at the same time they are present in GAC_32 folder. So what exactly are they? System.Data is a namespace , System.Data.DLL (the file) is an assembly . A namespace is a logical grouping of types (mostly to avoid name collisions). An assembly can contain types in multiple namespaces ( System.DLL contains a few...), and a single namespace can be spread across assemblies (e.g. System.Threading ). Namespace is a logical grouping of