Does Microsoft.Sharepoint.dll come in both 32bit and 64bit flavors?
So if I develop on a 64bit machine. Do you think if I install MOSS 32bit, I will be able to deploy successfully to a 32bit server. Or can I just copy the 32bit DLL's inplace of my 64bit DLLs?
Looks like it: http://support.microsoft.com/kb/970359
Yes but be careful when writing code and referencing the dll from two different machines. You may be dealing with version differences for instance writing code against MOSS 2007 and using that dll will not work when porting that over to MOSS 2003.
Yes, there is a 64 bit version of that dll to build against - you can download from here:
http://www.microsoft.com/downloads/details.aspx?FamilyId=0A50DA0F-7C94-4814-BBFE-2B66FE4A9087&displaylang=en
Related
I am hoping to gather some clarification and a better understanding of an issue I'm currently dealing with.
I wrote some simple test code which pulled in a 32bit dll file using FFI. My simple tests worked fine. Now, I started this project on a 32bit computer. When I went to continue the project, I was using a 64bit computer with 64bit Ruby installed.
I've tested this both on the 64bit production server and my 64bit laptop. I've done some research and I think I've gathered the issue, but I need a better understanding and verification.
So, for clarification, the dll file I need to utilize is 32bit. I've gotten a simple application functioning on a 32bit computer, but I am unable to get it running on the either of two 64bit computers.
In order to tie in with a 32bit dll, do I have to be running 32bit ruby? Will FFI only tie in with a dll of equal (32/64) architecture?
Also, best I can find, there is no 64bit version of the dll file as it's essentially legacy support. And, most production environments are 64bit (windows).
I am building up my VS2010 project using "any cpu configuration" so that the executable can work for both 32 bit and 64 bit versions.
But after using ILMerge to generate a bundled exe, the resultant exe is only working in 64 bit system and for 32 bit system its showing
This version of output.exe is not compatible with the version of Windows you're running. Check your computer's system information to see whether you need a x86 (32-bit) or x64 (64-bit) version of the program, and then contact the software publisher.
The ILMerge command used:
C:\BuildTools\ilmerge.exe /out:proj1.exe output.exe 1.dll NLog.dll 2.dll targetplatform:v4 /ndebug
I tried to figure out any option in ILMerge to fix this, but do not find anything useful.
Any help on this will be of great help.
Figured out is the issue with Nlog.dll which was built in 64 bit environment. Fixed after converting it to Any Cpu
How to install activeperl for windows 32 bit pc? Facing issues in installing as the vversions 5.16.3.1603 and 5.18.1.1800 supports 64 bit and not 32 bit.
You can download the 32-bit version for Windows at http://strawberryperl.com/
The 32bit community binaries are now behind a paywall. You have to be part of the ActiveState Platform, teams tier, to gain access to legacy builds.
The site states: "if you need 32-bit or other older/legacy versions, they are available through our new ActiveState Platform by subscribing to at least Team Tier. See pricing here."
Since the teams tear is $912/yr. I would suggest using strawberry Perl as #kurdtpage mentioned for 32bit.
The download page for ActivePerl has links for 32-bit (x86) and 64-bit (64-bit, x64) installers for both 5.16.3.1603 and 5.18.1.1800, with the 32-bit versions apparently differentiated by the presence of "x86" in the name of the downloadable file for 32-bit systems.
I don't have a 32-bit machine to try installing these files on, but unless I'm missing something, it looks like they do have separate 32-bit versions available for download.
I would recommend this site: https://softradar.com/activeperl/
I use that site for much downloads.
We've got an ancient of days VB6 app which sometimes needs to be updated and installed on our user's machines. We've begun using Inno, and especially InnoIDE, to make the setup.exe, to get this onto our user's PCs. However, I'm wondering about 64-bit Windows, and Inno setups. We've got a couple of machines in-house, which are 64-bit versions of Windows 7 Professional. I've successfully installed our app, using the setup from Inno, onto a 32-bit Windows XP machine. Can I use the same setup on our 64-bit Windows 7 machines? Will it put the .exe into the C:\Program Files (x86)\ directory structure automatically, or do I have to make allowances for 64-bit versions of Windows?
If your app is only 32-bit, then Inno will automatically take care of doing everything correctly.
Only if your app is mixed or 64-bit do you need to do anything special as rushman says.
There is a very good section in the help file that explains the changes needed.
If you're installing any 64-bit device drivers, the calls to most newdev and setupapi entry points will fail with error code 0xE0000235 (ERROR_IN_WOW64). Those calls only work when invoked from 64-bit code, and Inno doesn't compile 64-bit installers yet. You may work around by using pnputil.exe, by adding a 64-bit stub executable, or by switching to WiX.
For 64-bit INNO intallations you generally only need to add one setup section directive and, obviously, add the 64-bit versions of DLL's and EXE's to the compiled installer.
The setup section directive is:
ArchitecturesInstallIn64BitMode=x64
I'm wondering if I can still develop 32-bit apps using a 64-bit machine (64-bit Windows Vista with Visual Studio 2008 SP1)? Because I am planning to buy a laptop with 64-bit Vista. Im asking just to make sure. Thanks!
64-bit Windows runs 32-bit Visual Studio just fine. Unless you specify you wish you use the x64 development tools, it will still compile 32-bit applications.
Straight from the page:
Visual Studio uses the 32-bit cross
compiler even on a Windows 64-bit
computer. You can, however, use devenv
commands to create a command line
environment to call 64-bit hosted
tools.
Further Information: http://msdn.microsoft.com/en-us/library/ms246588(VS.80).aspx
With Visual Studio you are able to target what platform. By default it will run on "Any CPU" (read 32 or 64 bit), but you can specify if you desire. Look under Project>Properties>Build and look for the "Platform Target" property.
Yes. 64-bit vista will run 32-bit executables, so if you have a 32-bit compiler, it will still work.
Within visual studio you can tell it what to compile to under the Configuration Manager - (Build Menu - Configuration manager) - this allows you to target 32 or 64 bit.
64bit of consumer hardwares is usually "amd64" architecture which can run both 32bit apps and 64bit ones natively. Windows Vista 64bit edition supports both 32bit and 64bit system libraries, so basically you can run both type of applications as well. (Note that IA-64 architecture does not allow this.)
Compiling a program in 64bit is not much related to the platform that the compiler runs. But, of course, to run and test the result binary requires the corresponding architecture.
As many mentioned above, VS2008 let you choose the target architecture, so there's no problem.
I've found that just the setup.exe created by Visual Studio 2012 Express won't work on XP, but if you go ahead load MS 4.0 .NET Framework from the Microsoft Website then the *.application will load and install without using the setup.exe at all.