extern means that the entity has external linkage, i.e. is visible outside its translation unit (C or CPP file). The implication of this is that a corresponding symbol will be placed in the object file, and it will hence also be visible if this object file is made part of a static library. However, extern … Read more
As others indicated, stdole.dll is a Primary Interop Assembly for a bunch of Office COM interop components. You can determine why it’s getting included in your project by doing the following. In Visual Studio, go to Tools > Options > Projects and Solutions > Build and Run. Change the “MSBuild project build output verbosity” setting … 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
I ran into this issue as well. However my fix was much easier. My file names and paths were too long to be zipped. There was no warning. I resolved it by copy-pasting the directory to another with a shorter path. e.g. from /this/path/is/way/too/ooo/ooo/oo/long to /home/Desktop
You may try this: Add/Existing Item, instead of Add Reference. Use Add As Link. Make sure the item is to be copied in build folder. In the property of the library in VS, set Build Action to Content and Copy to Output Directory to Copy if Newer. Done. Rebuild and test. Suggested in the link … Read more
The problem is likely you try to register a 32-bit library with 64-bit version of regsvr32. See this KB article – you need to run regsvr32 from windows\SysWOW64 for 32-bit libraries.
Have a look at BoxedApp. Good luck!
I think you’re looking for GetModuleFileName. http://www.swissdelphicenter.ch/torry/showcode.php?id=143: { If you are working on a DLL and are interested in the filename of the DLL rather than the filename of the application, then you can use this function: } function GetModuleName: string; var szFileName: array[0..MAX_PATH] of Char; begin FillChar(szFileName, SizeOf(szFileName), #0); GetModuleFileName(hInstance, szFileName, MAX_PATH); Result := … Read more
The same error happens when Visual Studio solution has selected the wrong Startup Project. The bold project is the designated startup project. Go to the Solution Explorer > Right click on the correct project and select “Set as StartUp Project” in the context menu.
Just Install : this nuget package Because there are some unmanaged code and you have to add those references on your project See the ChangeLog