I've got an exception when I deployed my application: "the located assembly's manifest does not match the assembly reference" What I remember is changing the project name from the previous source code, does it affect that much?
View 1 Replies
I am loading an Assembly using Assembly.LoadFrom() as the assemblies are located in a different path from Application Base directory.
Dim oAssembly As Assembly = _
Assembly.LoadFrom("C:\MyFolder\" + ddlXlate.SelectedItem.ToString() + ".dll")
And I consume a Type from that assembly without any problem:
oXML = CType(oAssembly.CreateInstance(sBaseType + ".XlateContainer"), _
XlateBase.XlateContainer)
However, the problem occurs when I try to use a Type from this assembly from within another method like the one below:
oComboBox.DataSource = _
[Enum].GetValues(Type.GetType(sType + "+ItemEnum," + sAssemblyName))
sAssemblyName is the one I loaded using LoadFrom() actually. After it said it cannot find the assembly, I used AssemblyResolve event which solved my problem :Subscribing AssemblyResolve event :
AddHandler AppDomain.CurrentDomain.AssemblyResolve, _
AddressOf MyResolveEventHandler
Event Handler Method:
Private Shared Function MyResolveEventHandler(ByVal sender As Object, _
ByVal args As ResolveEventArgs) As Assembly
Return Assembly.LoadFrom("C:\PSIOBJ\" + args.Name + ".dll")
End Function
And I thought maybe the error occurs because it cannot find a dependent assembly defined in assembly manifest file I loaded using LoadFrom() already but when I checked the args.Name, I saw it was trying to load same assembly and after that it worked without any problem. So basically a type in the loaded assembly cannot be found before the event adding change.
My old code was using AppDomain.CurrentDomain.Load() and Assembly.Load() methods and they were working fine without the AssemblyResolve event. I was able to reach types in dynamically loaded Assembly from every where within the same AppDomain.
LoadFrom() can find dependencies automatically within the same requested assembly path and that couldn't be problem as everything this dll needs was there. So at first it looked like a AppDomain problem to me as it looks like it seems it can reach assemblies from Load context instead of LoadFrom context and I am now using LoadFrom context.But now it seems I should pass oAssembly instance evertwhere to use any type from the loaded assembly?Doesn't it load the assembly where I can reach it everywhere (same AppDomain) using simple Type.GetType(...) method?
When ever I finish simple programs no matter what it is and i click to debug it it comes up"Error while trying to run project:could not load file or assembly"project name" or one of its dependencies.the module was expected to contain an assembly manifest"
View 4 RepliesI have used Express for a while and am running the 2010 trial full version at the moment. So I am pretty new to all the tools in the full version, and I am building my first dll that I need to embed a manifest in.If I add a strong name to a support dll I get this message
xx.dll is a strong-name signed assembly and embedding a manifest invalidates the signature. You will need to re-sign this file to make it a valid assembly.If I don't sign it I am told it is unabale to emit assembly because my support dll doesn't have a strong name.I found the post below in the c++ archives, and the thread sounded like what I was running into. I can't seem to find where to access Linker.
[Code]...
I've been having an error with my Visual Studio 2008 with .net framework 3.5 Sp1. I am creating a project, and it would run properly until after a while when I try debugging the project I would get a error message that says:
"Error while trying to run project: Could not load file or assembly 'Name_of_Project' or one of its dependencies. The module was expected to contain an assembly manifest."
Also the .exe file that it creates in the bindebug folder gives and error that says:
"The application failed to initialize properly (0xc000007b). Click OK to terminate the application."
These errors after a format of the machine would disappear for awhile but not indefinitely.
I am using source safe to maintaine my code.Recently I copied my code to another machine.But everytime i build my project i am getting below error:Problem generating manifest. Could not load file or assembly
'D:WorkingFolderProjectSubFolderobjReleaseSubFolder.exe.manifest' or one of its dependencies. An attempt was made to load a program with an incorrect format.When i check above manifest file is empty (0k).I tried rebuilding (after cleaning solution) , also tried with copy pasting previus manifest file content.None of above solution worked.
When running setup to install published program, the following message occurs: System Update Required: Unable to install or run the applicaiton. The application requires that asssembly CrystalDecisions.CrystalReports.Engine Version 10.2.3600.0 be install in the Global Assembly Cache (GAC) first. This version is listed in the references of the program and in my mind, be included in build. How do I get by this error?
View 23 RepliesWhen running setup to install published program, the following message occurs: System Update Required: Unable to install or run the applicaiton. The application requires that asssembly CrystalDecisions.CrystalReports.Engine Version 10.2.3600.0 be install in the Global Assembly Cache (GAC) first. This version is listed in the references of the program and in my mind, be included in build. How do I get by this error?
View 2 RepliesI have recently upgraded an VB6 project to vs2008. I was almost finished when the following error occured. Unable to emit assembly: Referenced assembly AxInterop.MSFlexGridLib does not have a strong name Prior to this error appering, I tested my app several times and it was fine. Only after publishing it did the error appear. I have tried all solutions I could find, but nothing helps. I have read [URL]
View 1 RepliesI receive this error as "Assembly Load Error" whenever adding a form or other object that has to be inherited.
"Unable to load assembly. Ensure that the file is a valid .net Framwork assembly"
I'm wanting to include a system tray icon in my WPF project, and found this resource:[URL]..which looks like it will work beautifully, but it's written for C# and I'm using VB.net for this project. I downloaded his project and built the notifyicon as a DLL, then added as a reference to my project.
It throws up an error: Unable to emit assembly: Referenced assembly 'Hardcodet.Wpf.TaskbarNotification' does not have a strong name So I'm trying to figure out the best way to proceed. Do I need to strong name it, or is there a better way to do this?
I have created several DLL (.NET) libraries that are used in several projects. In these DLL libraries I want to know/retrieve which assembly (EXE) calls/uses the library, so if possible I want to know info like assembly name (EXE), strong name, version number, etc.
NB: Examples may be in C# or VB. I use both languages.
I have written a .net assembly which plugs into to a third party COM application. The .net assembly is COM visible to the third party application. However this .net assembly references other regular assemblies. If I put these assemblies in the GAC the COM visibile assembly sees them without a problem. However for various reasons I do not want to put them into the GAC but I cannot get my COM visible assembly to see the other assemblies when they are in other locations. I have tried putting them in the same directory as the COM visible assembly. I have tried putting them in the same directory as the third party app's exe but neither of these work.
View 5 RepliesI made my first WPF control:
[code]...
On the DataGrid control it says: "the type datagrid was not found, Verify that you are not missing an assembly refernece" I'm creating the control within a Win Forms app. What assembly to I need to include and how do I do that in XAML?
I have VS 2005. I am creating a VB .NET class that will interop with a COM app. I want to add a reference to a type lib file (.tlb). So I run the add reference command and use the browse button. I browse to the .tlb file I want and ok out. When I am done, the reference I have is to an assembly in the GAC. But I don't want that assembly as a reference. I want to have the IDE create a private interop assembly that I will deliver with my .NET object.
So how do I avoid hvaing VB .NET pull in an assembly from the GAC instead of creating an interop asm from the typelib I have browsed to?
I have a pretty complicated project with lots of class files, code modules, etc. There was a changed to one of my referenced DLLs that requires an isolated change in a single Sub within my solution. Unfortunately, this new Sub is not compatible with most of my clients' configuration but is required by some of my other clients. So now I must keep two versions in Source Safe of my solution - which I do not want to do. What I would like to do is to be able to determine which DLL is running and flip a switch to use the either the old Sub or the new Sub. Currently the sub is in a class, but I could break it out. Is it possible to determine which assembly version DLL is running? Also, if I reference the new DLL, the old Sub will not build. If I reference the old DLL, the new Sub will not build. So is there a way to keep both Subs in the same project?
Can I use reflection to know what is the assembly version of a loaded DLL?
I have created a shared assemby MyLibray version 1.0.0.1 and installed it in gac. Again I created MyLibrary version 1.0.0.2 and installed it in gac.
See the gac screen shot.
But in Add Reference dialog box only older version 1.0.0.1 is available.
See the screenshot.
Reference Assembly outside the AppBase-Directory
View 1 RepliesI have an industrial control program that we install on OEM equipment. This equipment falls into one of two categories; those WITH a special piece of IO hardware installed on the computer and those without.
This IO hardware has .NET 3.5 support assemblies, and is easy to program for. In my program, I reference the assemblies under the Project Properties and I'm good to go. Here's my problem... my program now seems to NEED this assembly to even start up, even if I'm not directly accessing anything in it until much later in the programming. When we ship any version of this equipment; I need to install the IO hardware assemblies whether the equipment needs it or not just for my program to run. The assemblies are bundled onto a hardware driver disk, and this sucker is 3gig.
What I would like to do is alter my program so that it runs no matter if it finds those assemblies or not. If not, then it will automatically close off certain functionallities (you can't use that because your computer don't have the hardware installed); and ideally, Visual Studio won't have 100 errors about a "missing reference". If found, then it will call them and use them normally as the program currently does.
I have a pretty complicated project with lots of class files, code modules, etc. There was a changed to one of my referenced DLLs that requires an isolated change in a single Sub within my solution. Unfortunately, this new Sub is not compatible with most of my clients' configuration but is required by some of my other clients. So now I must keep two versions in Source Safe of my solution - which I do not want to do. What I would like to do is to be able to determine which DLL is running and flip a switch to use the either the old Sub or the new Sub. Currently the sub is in a class, but I could break it out. Is it possible to determine which assembly version DLL is running? Also, if I reference the new DLL, the old Sub will not build. If I reference the old DLL, the new Sub will not build. So is there a way to keep both Subs in the same project?
View 1 Repliessorry for my English, I don't speek well... I need to compile assembly in memory, that can compile another one. There is a form with one button. Here is a code of the form
Imports System
Imports System.Threading
Imports System.CodeDom
Imports System.CodeDom.Compiler
Imports System.Collections
[Code]...
Since, it's possible for anyone to name an assembly starting with 'System', checking for 'System' is not a satisfactory solution.
Alternatively, if that's not possible, how about checking the modules in an assembly?
I am building a dll-Assemby A which references another Assembly B. Assembly B is strongly named and installed in the GAC of my development computer. An other computer will not have assembly B installed in the GAC.
Question: If i handle strongly named assembly B like a private assembly and copying it into the bin-directory by specifying local copy = true in the properties-window, will the programm run on the other computer?
One of them is giving us trouble in only 1 spot out of the 4 spots we use it at:The trouble spot is a windows form project that uses reflection to dynamically load some DLLs that run long running processes. One of these long running processes is an agent that relies on one of our vender DLLsWe're getting the missing assembly exception at the point where we first enter a function that references the library. I already checked the silly things such as if we had forgotten to move a reference from the old version to the new version, but that's not the case. I also checked the bin directory of the project and the assembly is there.
View 3 RepliesI have managed to get ASP.NET Membership mainly working with my SQL server.The problem i'm having is I get an error in VS2010 in my code behind file when attempting to create a user. I get a Red Exclamation mark appear on .CreateUser on the code below.
Error Message:Reference required to assembly 'System.Web.Security.ApplicationServices, Version=4.0.0.0, Culture=neutral,PublicKeyToken=31bf3856ad364e65' containing the type 'System.Web.Security.MembershipUser'. Add one to your project.
Code:
Protected Sub Button1_Click(ByVal sender As Object, ByVal e As System.EventArgs) Handles Button1.Click
Try
Membership.CreateUser(r_user_name.Text, r_password.Text)
Label1.Text = "User created"
[code]....
I've tried adding the following to the web.config:Not sure if thats correct!! but i get an error message when I open the page:Parser Error Message: Could not load file or assembly 'System.Web.Security.MembershipUser, System.Web.ApplicationServices, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e65' or one of its dependencies. The given assembly name or codebase was invalid. (Exception from HRESULT: 0x80131047)
How to I reference my own .dll after i add it to the GAC? I successfully added my .dll to the GAC, have seen it in the list. However, when i try to reference in Visual Studios..... i am lost.
View 2 Repliesim building an application i started it in VB 2008 and i upgraded to VB 2010
then i made some mods and tryed to run the application and then
i get this error
Error2Reference required to assembly 'System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' containing the type 'System.Windows.Forms.Form'. Add one to your project.C:UsersAdminDesktop
[Code].....
Currently, when I want to use Microsoft Chart Controls on a website, I need to add the following onto every aspx page where I want to use it:
[Code]...
Is there any way to move this to the web.config file, so that I don't have to put it on every page ?
I have a Visual Studio 2008 solution with project A referencing project B as a project reference. Project B references System.Data.Linq, but project A does not. Everything compiles and runs fine. I like this arrangement because avoiding a reference to System.Data.Linq in project A ensures that it uses project B methods instead of directly accessign System.Data.Linq methods, which I want to avoid.
View 3 RepliesWe have upgraded our project from Visual Studio 2008 to Visual Studio 2010 without any issues until now. Our project contains a folder call Libraries which contains different versions of Oracle ODP.NET DLL's as well as different versions of Telerik DLL's. Our project contains references to one of the versions of each. The problem is once we remove the reference and re-add it by browsing to the new version, again inside the Libraries folder inside the project, it adds the reference, but to the same version we just removed. We can even copy the DLL to our desktop, remove the reference and add to the new one on our desktop and it still will point to the Libraries folder version???. The only we we can actual change the reference to the new DLL is by manually changing the path in the .vbproj file, which is obviously not going to work for us. The same behaviour worked perfectly in VS 2008. We switch our references quite often, when new versions come out, but also far more often to QA different versions of ODP.NET and Telerik Control DLL's, so manually editing the .vbproj file is becoming quickly cumbersome. If I browse to a specific version at a specific path, Visual Studio should ALWAYS do what I'm telling it to do..
I did some seaching and came across a few other people with the same issue. This better not be as designed and if it's a bug, which I believe it to be, when will it be fixed?[URL]..
