My problem and the solution I have a 32 bit third party dll which I have installed in 2008 R2 machine which is 64 bit. I have a wcf service created in .net 4.5 framework which calls the 32 bit third party dll for process. Now I have build property set to target ‘any’ cpu … Read more
This did the trick for me: USE <DATABASE>; EXEC sp_configure ‘clr enabled’ ,1 GO RECONFIGURE GO EXEC sp_configure ‘clr enabled’ — make sure it took GO USE <DATABASE> GO EXEC sp_changedbowner ‘sa’ USE <DATABASE> GO ALTER DATABASE <DATABASE> SET TRUSTWORTHY ON;
DUMPBIN is included with Visual C++ and can provide this information with the /HEADERS switch. Example output from a 32-bit image: FILE HEADER VALUES 14C machine (i386) 6 number of sections 306F7A22 time date stamp Sun Oct 01 22:35:30 1995 0 file pointer to symbol table 1D1 number of symbols E0 size of optional header … Read more
Use the FileVersionInfo object. Here’s an example from the Microsoft website that gets the version info from notepad.exe public void GetFileVersion() { // Get the file version for the notepad. FileVersionInfo myFileVersionInfo = FileVersionInfo.GetVersionInfo(“%systemroot%\\Notepad.exe”); // Print the file name and version number. textBox1.Text = “File: ” + myFileVersionInfo.FileDescription + ‘\n’ + “Version number: ” + … Read more
The exit codes are not documented. The documentation is here: https://learn.microsoft.com/en-us/windows-server/administration/windows-commands/regsvr32 However, the source code for a version REGSVR32.EXE is shipped with Visual Studio 2008. This gives its version as 4.0.0, so is not the same as the one shipped with windows, which reports version 6. http://msdn.microsoft.com/en-us/library/ms177531(v=vs.90).aspx A quick look shows these: #define FAIL_ARGS 1 … Read more
load-time linking is when symbols in the library, referenced by the executable (or another library) are handled when the executable/library is loaded into memory, by the operating system. Run-time linking is when you use an API provided by the OS or through a library to load a DLL or DSO when you need it, and … Read more
Try adding using System.Runtime.InteropServices; to your class, that’s the namespace the DllImportAttribute resides in.
All components in your application must share the same runtime. When this is not the case, you run into strange problems like asserting on delete statements. This is the same on all platforms. It is not something Microsoft invented. You may get around this ‘only one runtime’ problem by being aware where the runtimes may … Read more
According to this page on MSDN, you need to have the corresponding version of Visual Studio (2008 or 2010), or the relevant Windows SDK for the “Platform Toolset” drop down to list those versions: To change the target platform toolset, you must have the associated version of Visual Studio or the Windows Platform SDK installed. … Read more
You’ll have to install a 32bit JVM and you will be able to run your code. If you are going to distribute your application, you will want to build both 32bit and 64bit versions of your DLL. Then use the following technique to have the proper DLL loaded regardless of your customers arch. Append either … Read more