RE: Compact SQL - Any CPU Build
- From: Smurfman-MSDN <smurfman@xxxxxxxxxxxxxxxx>
- Date: Fri, 6 Mar 2009 11:11:01 -0800
Colbert, thank you very much this helps a great deal.
So, I downloaded and installed SQL Compact 3.5 SP1 x64 (x86 was apparently
already installed according to my attempt to install it).
My quesiton is this - suppose I want to compile for both platforms - as I
may never know which OS a person might have.
Do I have to have two projects, or do I have to compile the same one 2 times
one each, can I automatically build both.
Which leads me back to my question - if I compiled for x64, do I understand
correctly, that my logic that was looking for
HKLM/SOFTWARE/Manufacturer/Program would automatically be re-directed to the
Wow6432Node
I worked around this by changing project to compile for x86 yesterday, but I
don't know if this is the correct solution.
Much appreciated.
J
"Colbert Zhou [MSFT]" wrote:
Hello Jeff,.
Thanks for using Microsoft Newsgroup Support Service, this is Colbert Zhou
[MSFT] and I will be working on this issue with you.
The following are some explanations for what the Wow6432Node is in the
registry and why we encounter the first issue. And later I will give my
solutions to both of your questions.
*The Wow6432 registry entry indicates that you're running a 64-bit version
of Windows. The OS uses this key to present a separate view of
HKEY_LOCAL_MACHINE\SOFTWARE for 32-bit applications that run on a 64-bit
version of Windows. If a 32-bit application queries or writes a value under
the HKEY_LOCAL_MACHINE\SOFTWARE\<company>\<product>, it is redirected to
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\<company>\<product> by system.
*In our situation, by default our MSI install program is 32 bit and it
tries to write a value to HKLM\SOFTWARE. As a result of we are running on
64 bit system, this registry writing is redirected to
HKLM\SOFTWARE\Wow6432Node. But, our application is compiled as 64 bit
application. So later when it tries to read the registry key, it reads from
HKLM\SOFTWARE directly where the written key does not exist.
THE SOLUTIONS (It depends whether you want to compile your application as
32 bit or 64 bit)
*If we want to compile it as 32 bit just like we did in the XP system.
Changing the option from Any CPU to x86. This will resolve both the issue 1
and issue 2.
*If we want to compile it as 64 bit application.
1) To resolve the first issue, we need to select the deployment project.
And in the Properties window, we change the TargetPlatform from x86 to x64.
This makes your registry key is written in HKLM\SOFTWARE instead of the
Wow6432Node.
2) To resolve the second issue, please download and install the SQL Server
Compact 3.5 SP1 x64 version,
http://www.microsoft.com/downloads/details.aspx?FamilyId=DC614AEE-7E1C-4881-
9C32-3A6CE53384D9&displaylang=en#filelist
Please also not the Additional Information in that link,
"Due to changes in SQL Server Compact SP1 and additional 64-bit version
support, centrally installed and mixed mode environments of 32-bit version
of SQL Server Compact 3.5 and 64-bit version of SQL Server Compact 3.5 SP1
can create what appear to be intermittent problems. To minimize the
potential for conflicts, and to enable platform neutral deployment of
managed client applications, centrally installing the 64-bit version of SQL
Server Compact 3.5 SP1 using the Windows Installer (MSI) file also requires
installing the 32-bit version of SQL Server Compact 3.5 SP1 MSI file. For
applications that only require native 64-bit, private deployment of the
64-bit version of SQL Server Compact 3.5 SP1 can be utilized."
If you have any future questions or concerns, please feel free to let me
know! Have a nice day!
Best regards,
Colbert Zhou (colbertz@xxxxxxxxxxxxxxxxxxxx, remove 'online.')
Microsoft Online Community Support
Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
msdnmg@xxxxxxxxxxxxxx
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/en-us/subscriptions/aa948868.aspx#notifications.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://support.microsoft.com/select/default.aspx?target=assistance&ln=en-us.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
- Follow-Ups:
- Re: Compact SQL - Any CPU Build
- From: Colbert Zhou [MSFT]
- Re: Compact SQL - Any CPU Build
- References:
- Compact SQL - Any CPU Build
- From: Smurfman-MSDN
- RE: Compact SQL - Any CPU Build
- From: Colbert Zhou [MSFT]
- Compact SQL - Any CPU Build
- Prev by Date: Re: Used Space 99%, Unallocated 1%
- Next by Date: Windows Mail
- Previous by thread: RE: Compact SQL - Any CPU Build
- Next by thread: Re: Compact SQL - Any CPU Build
- Index(es):
Relevant Pages
|
Loading
