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've started to use a Vista machine for development. In case it is significant: I'm using MSBee so that I can code in the Visual Studio 2005 IDE while still building against the 1.1 framework.On the Vista machine, when I tried to build a particular vb project, I got this error:
error BC30464: Namespace or type'Compatibility' in the project-level Imports 'Microsoft.VisualBasic.Compatibility' cannot be found.
The same project built fine on my old XP machine. I checked in this folder on my Vista machine:
C:windowsmicrosoft.netFrameworkv1.1.4322
...and sure enough, "Microsoft.VisualBasic.Compatibility.dll" was missing. So was "Microsoft.VisualBasic.Compatibility.Data.dll". Copying them from my XP machine to my Vista machine allowed me to build the project successfully.I'm just a bit puzzled as to why this happened. Why was "Microsoft.VisualBasic.Compatibility.dll" missing? I'm also not very comfortable with my chosen solution - copying the DLL manually. It works, but surely there must be a better way.
I have a VB.NET executable program that I've been running nightly as a Windows Scheduled Task on a Windows Server 2003 machine. I have the source code, and it was compiled using VS 2005. Now I want to run it on a Windows Server 2008 R2 machine. If I try to "open" it from Windows Explorer, I get "The version of this file is not compatible with the version of Windows you are running." It is in Program Files(x86), so doesn't the OS know to run it as a 32-bit application? Do I have to load this in VS2008 and recompile it there as a 64-bit app? But all my old VB6 and VBScript scheduled tasks are running fine, why is the OS only complaining about this program?
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...".
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
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?
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]
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'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'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
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?
When I try to install an application to another user's computer I receive a message box that says "Unable to run or install application. The application requires that assembly Microsoft.SqlServer.Pipelinehost version 9.0.242.0 be installed in the global assembly cache (GAC) first.A key feature of the app is to export data from sql server to an excel spread sheet so I have the following import statements
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.
I havnt found any info on this, probably because I expect there is no real way to do it... but does anyone know if there is a way to run an ActiveX control in 'copatibility mode' or some sort ov virtualization WITHIN a .net app?
We have a legacy control that does not work in Vista (and up) If we set the whole app to WinXP SP2 compatibility mode, the control seems to work well enough.
I would like to be able to rig it so we don't need to manually set that on every system.
My next step is to start looking if we can just set the compatibility through install, or the app itself.
Am I still able to develop programs in Visual Basic 6 that will run easily under Windows 7? If no then must I convert to VB.NET? Are there other strategies?
Imports System.Data.OleDb Public Class Form2 Dim Conn As OleDbConnection [code]...
this is my codes in vb?I am thinking what is the error in this code?because everytime I execute this There is an error appearing in this part OleA.Fill (DSSearch, 0) it says that "No value given for one or more required parameters." so, what should i need to do?
I have a small application I wrote in VB with visual studio express. This app uses a timer tick to wait for a certin time, the opens several comm ports, reads data, creates an output string, an sends the string via email. I tested this app for several days on a windows 7 32 bit machine, with no problems. I compiled (published) the program, and am attempting to run it on a windows 7 64 bit machine. However, on the 64 bit machine, it freezes up and can only be stopped with Task Manager.
at the time the app hangs the only things going on are 1. a timer checking to see if it's time to read the comm ports. and 2. a background thread checkig to see if the internet is available to email the string.
I tried ;loading visual studio on the 64 bit machine, and compiling the app there, with the same result. However it seems to run (tested for 1 hour) in debug on the 64 bit machine.
I have an Excel file endowed with a macro written under Office-2007.This file can be opened by Excel-2003, but the macro can't run because 2007-objects can't be recognized.My question is: does it exist a library or some trick to allow the macro running under Office-2003?
