Is there a way to force LinqPad version 5.1 to run in x86 mode? I think I found a way to do it in the past but I have searched for several hours on the internet and cannot find it.
Specially what I want to be able to do is execute Vfp OleDb commands but it is giving me an error that VFPOLEDB.1 provider is not registered on the local machine. I assume this is because I am running in AnyCPU mode (the LinqPad web site says AnyCPU defaults to x64. The crazy thing about it is that I have a saved query for this so it seems like I had to have been able to do it in the past.
What I have is the x86 version as the default. I have both versions on my taskbar.
That is true that the reason is you are running anyCPU version on a 64 bits machine.
Related
I guess the question can't be answerd but at least a advice where I should search. My application works perfecly in debug build and release build inside VS2010, but when I run the release build hangs in a particular point (I don't know where) but the debug exe dose not hang.
When I run the release build in a Win 7 do not hang only in win XP. What could be the difference between the the two build that that make not work properly?
I know is too few info, but I don't know what I should say or can. I can't give the entire code, that why I make the question so general and hope someone know so well the differences between the two builds that could show me the way.
I am using only one static library of mine, might be importan.
UPDATE:
All computers in win 7 64bits works fine all computers in Win xp 32bits don't. The build is 32bits
The problem could be different behavior of the heap when the program is started from the debugger. Check this question, and the answer: Differences between running an executable with Visual Studio debugger vs without debugger
Since, you are saying your Win7 machines are 64 bit (which are working fine). Is it possible that you have got something in your project which is specifically targeting 64 bit ? i.e. some third party tool?
If not, you can build the solution to target specifically for 32 bit.
In your solution properties pages, go to "configuration" tab. Here for select "Release" in the configuration drop-down and in platform select "x86", see if this helps
-Milind
I've got a web application that won't run in debugging mode in Visual Studio. Running on Windows 7 computer with IIS 7 installed.
I've seen the numerous articles on the internet about re-installing the .NET versions, but this has not solved it for me. The project still refuses to compile.
In the Event Log there are several entries when I've started the debug process:
With a corresponding entry above it:
As stated I have run the .NET registration aspnet_regiis -i for both v2, v4 both 32/64 version of the .NET to no avail.
The error seems to point to the ISAPI filters, which I have tried fiddling with and configuring without success:
I'm now at a loss as to what's causing the problem.
This message is saying you're loading the 32bit aspnet_isapi.dll in a 64 bit w3wp.exe process.
You can check the application pool "Advanced Settings" for your 64 vs 32bit settings and select the correct one:
This is interesting, as you mentioned you do registered 32 bit version but your screen shot shows only 64 bit there.
Check my IIS:
Have you checked the configuration manager? I'm wondering would it be possible it was set to compile for certain CPU only.
Whats the correct way to build the setup installers for a Windows Forms app to install and run on a Windows 7 32 bit machine, using Visual Studio 2010 on a Windows 7 64 bit machine ?
I've just brushed the dust off a 3yr old Visual Studio 2008 app, built on Windows XP, using SQL Express 2005.
I've updated it to VS2010, SQL Express 2008, and rebuilt it on a Windows 7 64 bit machine. It needs to run on a Windows 7 32 bit platform.
The setup project for database keeps failing (on startup) when run, saying its only for an x64 machine. (The setup for the app runs ok and installs.)
I've been through every project in the solution and set it to build using x86 (as opposed to Any CPU). I've removed all PreRequisites. The only thing suspect left in there is a DB CustomAction project (which runs the db scripts).
From googling it seems to me building on a 64 bit machine with 'Any CPU', means it should produce setup files that will run on a 32 bit machine via WOW ? and without having to make all the changes Ive been making ? Am I missing something bleedingly obvious ?
Thanks.
Try this:
select your setup project in Solution Explorer
go to its Properties pane
make sure that TargetPlatform is set to x86
I always find it frustrating coming across posts of the same question I have that never had a resolution posted. So I'll post what I found in case it, or even some if it, is of use to others one day. I found a lot of other developers reporting the aimless Windows 7 program 'has stopped working' message.
By the way, I found the easiest way to test deploying the app and the installers was to build a Virtual PC machine with the same configuration as the platform will eventually run on. Then copy that Virtual PC, and test run on the copy. That way, I can just delete the copy at any time, recopy from the original and start over, quickly.
Yes, as Cosmin said, the TargetPlatform Property of the solution also needs setting to x86. Anyway, didnt fix the the problem, the app still produced the 'has stopped working' message.
Next I checked the SQL logs ERRORLOG file (c:\Program Files\Microsoft SQL Server\MSSQL10.SQLExpress\MSSQL\Log) and it was reporting the app was trying to logon using Mixed Mode authentication, whereas SQL was set for Windows Authenication. Now I KNOW I selected Mixed mode when I installed SQL Express, as my app uses a sql service account which my db installer creates the account for. So somehow that was changed by something (dont know what?). To set to Mixed mode via SQL Server Management Studio you just right click on the instance, select Security, and change Server Authentication. Without Management Studio, you need to edit the registry HKEY_LOCAL_MACHINE/Software/Microsoft/Microsoft SQL Server//MSSQLServer, and edit key LoginMode = 2 for Mixed. Once again, didnt fix the problem, the app still produced the 'has stopped working' message.
Next, by chance I stumbled across some posts about this message can be caused during startup by loading 32 bit apps on Windows 7. I put MessageBoxes, and Try/Catchs on the first lines I could, and they never got displayed, and no error was caught.
The next thing I tried was to run DependencyWalker over my exe. It reported 2 x 32 bit files missing: IEShims.dll and GPSVC.dll. There are posts from other devs encountering this, and the end result was I found them in C:\Windows\winsxs (GPSVC.dll was called x86_microsoft-windows-g..licy-base.resources_31bf3856ad364e35_6.1.7600.16385_en-us_c10af1bed239c523_gpsvc.dll.mui_0c160ac2). I dropped them into C:\Windows\System32, recompiled my app, deployed it to my test machine, and it finally ran !
Still dont understand why just putting them into the System32 dir on my dev box made the app run on the test machine ? But anyway, it fixed the problem, and hope this is of help to others.
We are moving to an all-64-bit development environment. Unfortunately VS 2008 and, more importantly, its built-in web server, run in 32-bit mode. When debugging code that references 64-bit assemblies - Oracle.DataAccess, for example - we experience the dreaded System.BadImageFormatException.
Can anyone offer any strategies for debugging code with 64-bit dependencies in VS? I suppose we could use a 32-bit Oracle provider, but we would like to emulate the production environment as closely as possible.
I have a similar setup on 64 bit Vista where I have the web site deployed in IIS - this site has in been successfully run and debugged in both 32 and 64 bit.
The biggest problem I have found is working in a mixed environment where some members on the project team are still on 32 bit Windows (both XP and Vista).
This causes headaches with project references to Oracle.DataAccess which I have only managed to solve with bindingRedirect entries in the web.config file in order to point to the correct version of the assembly.
If you use IIS7 you can choose 32/64 bit mode. You will then have to have your projects kick up with IIS instead of cassini which takes a little bit of work, but I think it will solve the problem with Oracle at least. Honestly I don't know how that would all work when attaching at 32bit debugger to it.
We use VMware hosts to give each of our web site developers their own virtual web server. You can use full IIS (as #KevinWon suggested) and install a 64-bit version of the debugger on them. I don't know the specifics of what our guys do - I found this out over a coffee the other day.
Set up an local IIS on your computer and set it to run in 32bit mode
http://kb.parallels.com/en/2131
If you enable the Debuging mode you can work with it, just like you would with the integrated development server. But you don't have to mess with the 32/64bit assemblies
Can someone tell me why I don't have all of the dev studio windows available to me when I develop on a 64-bit platform? I upgraded my dev desktop box to server 2003 x64 to match our deployment platform. Since then (I'm using VS2005) I've noticed that several windows aren't available. I can't view Processes (which is the most annoying) so I don't know which processes I'm attached to. I can attach to a process fine, but it won't show me what is already running under the debugger. There are others, but that's the one that sticks out in my mind at the moment.
My question is where are these limitations of developing under 64 bit documented (assuming they are)? (Of course, I also get the "Edit/Continue" warning dialog all the time telling me that doesn't work in 64-bit)
Also, is VS2008 any better under 64 bit?
Follow-up: Apparently my question is a little bit vague. I'm developing a 64-bit app on a 64-bit development environment. "Recompile it in x86" doesn't solve my problems.
Follow-up #2: I'm giving it one more shot. I WANT TO DEBUG A 64 BIT PROGRAM ON A 64 BIT ENVIRONMENT AND I DON'T HAVE ALL OF THE VISUAL STUDIO FEATURES SHOWING UP. HOW DO I GET THEM?
Follow-up #3: I just installed XP 64 (previously I was using Server 2003 64-bit) and those features all showed up again (Process window, etc). Apparently the server version of windows doesn't provide all of the dev features.
Can anyone tell me why?
"Edit/Continue" can work if you change the build setting to X86 :)
Here was the suggestion from StackOverflow about it.
I had some problem with NUNIT when debugging code. The solution was to use the special program in the \bin\ folder Nunit-x86.exe for old code built in x86 and use the Nunit.exe for x64 built.