our target production environment is Win2003 + SQL2005 + .NET 2.0 (all 32 bit);
Currently We have new developing PCs comming in and they are 64 bit capable.
As a developer PC, we want real raw installation instead of VM solution.
I know 64 bit IDE installation (win7 X64 + VS 2010 X64) will give us bigger RAM and faster response and I know 32 bit application can run in 64 bit environment through WOW (windows 32 on Windows 64) .
My concerns:
(1) 3rd party DLLs are 32 bit and might give us debugging troubles in 64 bit environment.
(2) The production target platform is 32 bit, it might give us some troubles to adjust 64 bit develoment environment to fit the target.
(3) Because the WOW is the mechanisim for 32 bit process running under 64 bit environment, No big performance gain (testing & developing the 32 bit code) just because it's 64 bit IDE environment.
Are my concerns valid?
I really want to know if the 64 bit PC development environment could improve our developing process (for 32 bit target) or might just end up giving us a bunch of troubles instead.
Thanks a lot.
Support for 32 bit development on a 64 bit platform has in my experience been flawless. That said, with a modern computer I doubt you will notice much difference in responsiveness and speed of the development process between the two. You would probably know this better than me, though, as only you know the details of what you are going to develop and how resource hungry said development will be. If you are just writing code, you could probably do that on a Commodore 64.
If you really think there is a reason to pick 64 bit, then I doubt you will run into much trouble. Installing a virtual machine is easy as a backup solution. Even if the 64 bit installation turns out to be a bad decision, you could always set up a dual boot, or just reinstall the OS. To be honest I think you are worrying too much :)
Sorry to contradict you, but information in your question is wrong. VS 2010 is 32-bit IDE. Support for 64-bits is provided by a set of compilers&tools. You can just select an options of not installing them.
You might have some issues with COM servers registration (like necessity to use SysWOW64 version of regsvr32 and use corresponding regedit), but again - if you have more than 3GB of RAM then x64 environments are worth a bit of pain caused by x64 redirection.
But I'd suggest you to move only if you feel that your current performance is not good enough. It might be more reasonable to perform cheap h/w upgrades rather than buying all that expensive stuff like new OS, new Visual Studio, etc
64-bit machine will let you catch virtualized registry errors easier. And also, only commercial virtual machines support 64 bit OSes if I'm not mistaken. I'd recommend 64 bit machine for development. You can really use more RAM too.
Related
Is it possible to run an application on a 64 bit Weblogic 10.3.2 Server instance with a 32 bit JDK?
The reason for me to doing this is getting an exceptions while running my program using 64 bit JDK.
UCFWin32JNI.dll: Can't load IA 32-bit .dll on a AMD 64-bit platform
The error is gone when using 32 bit JDK.
If it is possible, then how?
Thanks!
A 32-bit version of a library cannot be loaded and used by a 64-bit JVM, and vice versa.
Moreover, UCFWin32JNI.dll does not appear to be a WebLogic library at all. In fact, it appears to be a library from Documentum. You ought to be looking for a 64-bit version of that library (if it is available) as it appears to be a 32-bit version going by the name and the error message produced. Finally, you'll need to place the 64-bit version in one of the directories constituting java.library.path.
No problems at all running a 32bit JVM on a 64bit platform. In fact, for some applications it can actually be more efficient, due to the fact that certain data types are innately larger on a 64bit JVM (ints I think are an example of this from memory)
A 64bit JVM provides all sorts of advantages for an application requiring access to a larger heap, but there's no harm at all in running a 32bit JVM.
I'm planning a test environment in several platforms include both 32/64 bits but I'm not sure about the hardware 32 bit could be virtualize through HyperV or not?
SUre it can. Hyper-V simulates a 64 bit environment. You can install a 32 bit operating system on a 64 bit processor, or? ;) I did not see any 32 bit normal processor (outside some low poewer stuff) in the last years.
Short of buying a SPARC processor, what emulators are there? Thanks.
Pickup a second hand Power Mac G5 and you can run a fairly recent version of a mainstream OS (ie. OS X 10.5.8) and a modern development environment (Xcode 3.1.4).
You get a pretty fast, modern RISC machine running an OS that is still highly used (for the time being, I admit.)
You could also install Linux onto it if that would be better for your needs.
Probably a lot easier to find and cheaper than a SPARC machine.
You could also install the SPIM emulator for MIPS
On revisiting this, it's worth noting that nearly all modern smartphones run on ARM processors, which is short for 'Acorn RISC Machine'. So, an easy answer is 'Android Studio' or anything else targeting phone applications.
Similarly, there's a plethora of simple development boards available inexpensively, such as the BeagleBone Black and the Raspberry Pi, that also carry ARM processors.
After referring to many posts, opinions and feedback from SO, I have just bought a Lenovo Thinkpad T410 . x64 Win 7 Prof, 500 GB # 7200 RPM , Core i7 620M processor, 4GB DDR3 RAM.
I am now setting up my development environment on the new machine. I need your suggestions in setting up a clean, structured and risk-free Development Environment.
Something about what I intend to do on this machine:
I am Entrepreneur bootstrapping my Startup. So I will have business related purposes (presentations) other than Coding.
I do coding on Microsoft stack currently for some of my other projects. But will start coding in other technologies such as RoR. So I need to have MS products (VS, IIS) and other OSS'
This machine also doubles up as production environment on top of Development Environment.
I don't have a separate Desktop for doing heavy lifting. This is my whole and sole workstation.
I have read a lot about VMwares here and how they help to keep the machine clean and ordered which you can just wipe out clean and have reinstalled as you wish. Is it a good thing to have VMs each for Microsoft stact, RoR stact and so on or have all of them installed on my main machine itself.
Also, apart from this, it would be great if someone can suggest some good options for Firewall+Antivirus+Malware stack (considering that this is a Win 7 machine)
ThanQ
This machine also doubles up as
production environment on top of
Development Environment.
You are setting yourself up for a world of hurt.
Aside from that, it is just common sense that you should use some form of VCS (I recommend Git) and store all your code NOT on your development machine. You should be able to checkout out your code, run a script, and be up and running. You are bootstrapping a startup; pay the $12/month to keep your code safe.
VMs are a good idea if you need to support different environments, for example Win7, Win Vista, and perhaps some flavor of linux. If you take my suggestion and use a remote VCS setup, you can checkout from the remote source onto your VMs.
Another benefit of VMs is you can set up a base install, with all the software you need, and create an image of it, so from that point on you can pass the image around, and you won't need to install the baseline software again.
we are thinking about buying and setting up a new PC to use as a nightly build PC. We are planning to install Visual C++ 2005/2008, SVN etc. However we need to compile our app:
for 32 and 64 bit
on 2 different linux distros
so we think we can setup a Windows Xp/7 and use VMWare to run linuxes.
But how to build for 32 and 64 build targets on the same Windows ? Should we rather install a 64bit windows from the beginning ?
Do you have any other suggestions/best practices for dedicated build computers ?
Thanks,
Paul
First, separate 2 logical parts: build system architecture and physical implementation.
For example, architecture may be based on hudson: One server runs hudson and hudson manages builds on any number of other servers (running any OS'es you may need).
Now it doesn't matter if you have multiple PCs running single OS or have everything virtualized or a mix of both.
For physical implementation, I would recommend complete virtualization: it has several pros while the list of cons is basically one item - performance penalty.
I'm not sure about 2005, but 2008 can compile for both x86 and x64 on a 32bit system.
Not sure what you planning on using to do the builds, but if you configure a x86 and x64 configuration in your project MSBuild works just fine.
msbuild /property:Platform=<platform target> <project or solution file>
I would be tempted to install 64-bit Windows, not necessarily so you can build 64-bit executables but because it'll allow you to use more RAM without jumping through unnecessary hoops. And being able to use more RAM means you can give the Linux build VMs more RAM, run them in parallel etc.
I personally would go with x64 so u can test... Plus it will obviously be faster