Is there a Quick and effective way of solving the problem of "Application works fine on 32 bit, but doesn't on 64 bit"?

Is there a Quick and effective way of solving the problem of "Application works fine on 32 bit, but doesn't on 64 bit"?

imagem de Jayant-Akolkar
Jayant-Akolkar
seg, 17/10/2011 - 21:37
Hi, Is there a Quick and effective way of solving the problem of "Application works fine on 32 bit, but doesn't on 64 bit"? All the apps developed using .Net compliant language do run on the Runtime and upgraded version of Runtime always supports the previous version of Runtime. If this is the fact then:::: 1>Why only some apps are getting non-compliant on 64 bit? 2>Even if the compilation option (In Visual Studio) is changed this problem occurs, but not in ALL APPS. Only some of the apps are found to be non-compliant. 3>Is there a Quick and effective way of solving this problem::: without affecting the SDLC 4>Is this problem common? Thanks a lot in advance. Jayant Akolkar
RSS Superior
3 posts / 0 new
Último post
Para obter mais informações sobre otimizações de compiladores, consulte Aviso sobre otimizações.
imagem de Bill Chung
  • Login para postar comentários
Bill Chung
seg, 17/10/2011 - 23:12

Some situations will cause .NET App can runs in 32bits Windows but not 64 bits Winodws.
The situation is most likely to happen when you set your compile target platform to anyCPU, and your application call 32bits process. This will be running in X86 Windows, but not work in 64bits Windows.
For example, if you using OleDb to call Access 2003 DB, you will call OleDb.Jet.4.0 driver, but this driver only for X86, when your compile target platform setting to AnyCPU, it will be failed when running in X64 Windows.
A simple solution is setting your target platform to specific platform, like X86 (if you call X86 process).

Superior
imagem de Jayant-Akolkar
  • Login para postar comentários
Jayant-Akolkar
seg, 17/10/2011 - 23:12

When releasing any product those are the 1st precautions we do. Set the compiler options, move your Connection strings to depend on XML/IO based relocatable files, use .... Syntax so that the actual resource can be actually located during the execution of the app and so on. But the problem here is arising from the Runtime level. If I've an app developed on 3.5 and if it executes well on 32 bit, utilizing the Runtime (Either embedded or installed as SP) then natural progression is that it executes on 64 Bit. Haven't we all noticed the installed paths of Runtime (On developer as well non-developer Computers?) and different physical files/folders on the computers?

Superior

Faça login para deixar um comentário.