I got warnings on my project, does somebody know how to reference this assembly. this is probably because the project has these crm.mytextbox type textboxes and other controls instead of normal system.windows.forms.textbox.Warning1Could not find type 'crm.Mycombox'. Please make sure that the assembly that contains this type is referenced.If this type is a part of your development project, make sure that the project has been successfully built.00
I 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]
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?
Everything was fine but suddenly appeared this error when I built a project. Warning 1 The referenced component 'stdole3' could not be found. Warning 2 The referenced component 'stdole2' could not be found. [URL]
I have a VB project that has a referenced to other project in the same Solution. I want to use Type.GetType() in order to obtain a type object from the referenced project but the method keeps returning Nothing.[code]...
I would like to enumerate an assembly's referenced assemblies and determine what should or should not possibly be included as a dependency in deploy scenarios.For obvious reasons I would want to exclude those assemblies that would be included by the CLR install.Is there any way to track back an assembly to being part of the default install of the CLR?
I am loading an assembly using LoadFrom method on a file located in another folder. The assembly is called VisualCronAPI.dll. The assembly that I load has references to another assembly (VisualCron.dll) which contains some general type definitions used in VisualCronAPI. The file VisualCron.dll resides in the same folder as isualCronAPI.dll.When using LoadFrom I see in the output that VisualCron.dll is loaded. I am able to retrieve all methods in VisualCronAPI that uses parameters from VisualCron.dll. I am able to see parameter values However, when trying to create a Type using the following code I get an exception:
Dim t As Type = assem.GetType("VisualCron.NetworkCredentialClass, true) Exception: Could not load type 'VisualCron.NetworkCredentialClass' from assembly 'VisualCronAPI, Version=1.0.3.32487, Culture=neutral, PublicKeyToken=55f7a52402de1c04'.
Is it possible to load a referenced assembly only if the .NET Framework version is lesser than a specific number? I'm using a selfmade LINQ library on .NET 2.0, but if the framework is 3.5+, it should use the M$ LINQ library, and ignore the selfmade one. Here's my library: [URL]
I have a simple application, that was working just fine then all of the sudden I open the file and the design pages will not show up and I get the following warnings:
Warning 1 Could not load type 'System.Object' from assembly 'mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' because the parent does not exist. G:ProgramsCONNS v 1.0ConnectionsFrontPage.Designer.vb 149 0
I created an application using VS2008. I am having a problem on only one PC. If I log on to the PC as the domain administrator, it deploys and runs just fine. If I log on as the user I get an error that basically says "The referenced assembly is not installed on your system. (Exception from HRESULT: 0x800736B3)". The error comes when running Venodr.appref-msl. VENDOR is the name of the application. The source is System.DeploymentSystem.Runtime.InteropServices.COMException I upgraded the user to a domain administrator and it still will not run. The PC is XP SP3
I have a stand-alone WinForms application, let's call it "Program A." Program A let's a user create a file and save some information to it. Program A also exposes some public classes.Another stand-alone WinForms application ("Program B") references Program A, and uses some of its public classes.
However, some of Program A's classes need to open the file the user created in order to retrieve data from it. In Program A, the location of the user's file is saved in the "Settings" (as user-scope settings of course) and are retrieved (this is a VB.NET app) via My.Settings.
This is all well and good until Program B runs - when it runs and uses the classes from Program A that need to read from Program A's My.Settings, the settings are blank - it's as if they were reset (as when you run Program A for the first time or under a new user account). Any application-scope settings are kept, but any user-scope settings are reset to their default values (whatever they were set to in the IDE when Program A was written).
[Code]...
Assume that the user has already run Program A at least once and opened a file, so Program A's My.Settings.UserFileName should be set.
When Program B calls Foo.GetStuff(), it doesn't return anything because My.Settings.UserFileName doesn't contain the user's file name - more accurately, it contains whatever the "default" value for that setting was (as set in the IDE when you set up the setting in the first place). But, if you turn around and launch Program A, it remembers the user's setting for UserFileName.
So - the question is: When calling a function in a referenced assembly, why are the user's settings not retained? Is there an explanation for the behavior I'm seeing, or am I missing something terribly obvious? Or perhaps I'm just going about this all wrong, and I shouldn't have made any of the public classes in Program A rely on anything in My.Settings in the first place?
I have created an application and a setup application for it.The application references Microsoft.mshtml.dll and another custom dll.The problem is that despite the fact that i added to the setup project the output of the application, these two dlls were not added in the setup project's "detected dependencies". Do i have to add them manually ? Do you know if Microsoft.mshtml.dll (C:Program FilesMicrosoft.NETPrimary Interop AssembliesMicrosoft.mshtml.dll)will work both on Windows XP and Windows Vista no matter what version of Internet Explorer is installed ?
Using VS 2005, I create a new VB .NET class library project. The project created is automatically populated with an "Any CPU" build target. I create a COM visible object, check the register for com interop and build the project. The resultant assembly is NOT registered in HKEY_CLASSES_ROOTCLSID. Instead it goes into HKEY_CLASSES_ROOTWow6432NodeCLSID. I have a 64 bit machine and 64 bit OS. I would swear that with VS 2003 on such a setup, I got an entry in the 64 bit registry hive.So I went to the configuration manager and specifically created a x64 config, copying from the (only) Any CPU config. But when I build I get two BC40010 warnings. One was for System.Data.dll. So I went to the project properties/References tab and then removed "System.Data.dll" (no mscorlib entry there - the other BC40010 warning) and then ran the add command and re-added System.Data.dll thinking that since I was working on the x64 config, the IDE would bring in the correct assembly.Still I get the warning. Why doesn't the IDE understand the meaning of the "x64" configuration the wizard created? The MSDN tells me I have to fix this:
To correct this error Examine the quoted error message and take appropriate action.Compile the program again to see if the error recurs.If the error recurs, reinstall the Visual Basic compiler.If the error persists after reinstallation, gather information about the circumstances and notify Microsoft Product Support Services.
When you download the .msi from our website and try to run it, you are presented with this very unfriendly message (attached). I'm using an Installer deployment project in VB.Net 2005 Pro - is there something I can do to avoid this error?
I have . VB.NET DLL that I have made COM visible and it works fine.However, I've now added another class which I also want to expose to COM but I am now getting an erro when I build it:
Quote:
Error1The assembly {...} could not be converted to a type library. Type library exporter encountered an error while processing 'TOPSMileageLookup.JobMileage, TOPSMileageLookup'. Error: Type 'JobMileage' and type 'Job' both have the same UUID.
JobMileage is the name of the original class I had that is COM visible and it worked fine when it was on it's own. Job is the name of the new class.Now, the obvious suspician is that I have copied over my COM GUID's but I can assure you that they are most certainly different. But what else could it be?
I am a java developer that inherited a vb.net web application. This app relies on a VB class assembly that builds in to a dll. I have made some changes to this class assembly but I cant seem to get the vb.net app to pick up the changes. I thought that using regsvr32.exe or regasm.exe would do the trick but after reading a bit more they don't appear to do what I need.
When vb.net uses code such as this import where is it getting the reference to "MyClassName"?
I am referencing a DLL in my project which works OK on both inside and outside of the IDE on my development machine but when I deploy to another machine, I get an error "Could not load file or assembly...".
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?
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?
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 :
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?
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?
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.
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"
sorry 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
