We Keep Coding

Unable to debug .NET after VS 2019 upgrade

I was using the VS 2019 to debug a SQL Server CLR C# .NET code. I got an upgrade notification from VS which I did and rebooted. I now get the error when trying to debug
Unable to debug .NET code. Could not attach to SQL Server on '....'. The 64 bit version of the Visual Studio Remote Debugger (MSVSMON.EXE) can not be used to debug 32-bit process or 32-bit dumps. Please use the 32-bit version instead.
Now my SQL Server (2019) is 64-bit and the SQLCLR Platform target is x64, so what is going on to make it think that a 32 bit process is involved?
Also the SQL Server and the VS 2019 are on the same machine do it not a remote machine issue.

I needed to run VS 2019 as an administrator - that fixed the issue. The error message is very misleading.
I tried changing the firewall settings but did not work.

Looks like you are trying to debug using the 64 bit remote debugger tools instead of the 32 remote bit debugger tools.
The connection component to SQL is likely 32 bit that's why it is crapping out.
https://visualstudio.microsoft.com/downloads/#remote-tools-for-visual-studio-2019

Program not working on 64 bit Windows

I have programmed (with Visual Studio, C#) an application that connects to an Oracle database and does stuff. It works fine on my pc with sample database, my Windows is 32 bit, but as soon as I upload it to the server which has a 64 bit Windows, I get an error:
The provider is not compatible with the version of Oracle client
I have set target platform on "any cpu" in Visual Studio.
What should I do to have it run on both 32 bit and 64 bit Windows?

C# Database providers are usually 32bit or 64bit (you didn't state the database provider you used).
If you set your program to be any CPU , at run time it will be compiled to either 32bit or 64bit which is determined by locally installed .Net framework.
Since your developing machine is 32bit , it runs as 32bit and has locally installed database provider of 32bit.
When you try to run it on your server , it runs as 64bit and doesn't find a provider for 64bit.
You seems to either need to install a 64bit provider on your server or compile your program to x86.

asp.net connecting to a 64 bit oracle client

I need to connect to a oracle database on another server so I don't have acces to the database itself.
I created an application in c# with winforms and I was able use this database when I changed some settings in the build options.
Now I am translating the application into a asp.net website and I got this error:
'Attempt to load Oracle client libraries threw BadImageFormatException. This problem will occur when running in 64 bit mode with the 32 bit Oracle client components installed.'
This is the same error as what I received when I used winforms but then It was possible to fix it in the build options.
Is it possible to fix this error without having acces to the server where the database is stored?

This has nothing to do with the database server version. It's the version of the client components/Oracle driver that you have installed on the web server and whether your web app is running in 32/64 bit mode. You need to make sure they are consistent (ie 32 bit app uses 32 bit driver, 64 bit app use 64 bit driver). Check the Enable 32-bit applications setting in your IIS app pool advanced settings.

Deployment on windows 7 64 bit os while trying to installing Windows application 2010 with crystal reports

I am getting deployment problem while installing Windows application developed using VS2010, access 2007 and Crystal Reports on windows 7 32 bit
First i got the following error.
The 'Microsoft.ACE.OLEDB.12.0' provider is not registered on the local machine while data export to MS ACCESS.I installed MS access database engine 2007 and Target Platform of my application to x86 ( which was initially set to AnyCPU)
MS access provider problem got resolved by installing Access database engine and changing the target platform to x86
Then i clicked a button to see reports.I got error "could not load assembly "crystaldecisions.crystalreports.engine".
I resolved it by installing Crystal Report Runtime 64 bit for .NET framework 4.0.
Now i am getting "The type initializer for crystaldecisions.crystalreports.engine.reportdocument' threw an exception "
I found some forums suggest that if u set Platform -> ANY CPU, it would get resolved.
But when i set platform - any cpu, i am getting msaccess problem again.
Please help me to find the solution for deploying Windows Application with Crystal Reports (developed vs2010 and msaccess 2007,windows 7 os 32 bit) on Windows 7 64 bit msaccess 2007.
Please provide a right solution to get rid of all deployment issue.It works finely on my system.
Development Setup:
Windows 7 32 bit
VS2010
Access 2007
Deployment Setup:
MS access 2007
window 7 64 bit
My windows application should run without any msaccess or report issue.
Thanks
Padma

While deploying application developed on 32 bit machine on 64 bit machine.Do the following
1.Build all projects under solution to X86 Platform.
2.Then in production machine,install all the necessary components for 32 bit.
Note Please do not install 64 bit components then it works finely for me.
I uninstalled all the components in my production server, next i installed my application.
Then i started installing components on receiving error messages while running my application.
Finally i got rid of all errors and it works finely for me.

oracle error in windows-7 64bit

I installed windows-7 64 bit. When I try to run my program (that works with Oracle 11g) I get this error:
Attempt to load Oracle client libraries threw BadImageFormatException
this problem will occur when running in 64 bit mode with the 32 bit Oracle client components installed
What can be the problem ? Where I can download 64 bit oracle client ?
(can I get any link for download)
thanks in advance

Have you tried download the 64bit Oracle Client from:
http://www.oracle.com/technetwork/database/enterprise-edition/downloads/112010-win64soft-094461.htmlBlockquote
This looks like it might be the correct download:
Oracle Database 11g Release 2 Client (11.2.0.1.0) for Microsoft Windows (x64)
win64_11gR2_client.zip (615,698,264 bytes) (cksum - 2947608743)
Contains the Oracle Client Libraries. Download if you want the client libraries only

Alternatively, if you cannot obtain a 64 bit version of the Oracle client and are stuck with the 32 bit version, then you can either:
rebuild your .NET application to
only run as a 32 bit (x86) process
instead of "Any CPU" or
use CorFlags.exe (CorFlags
Conversion Tool) to reconfigure
your existing .NET application exe
to run as 32 bit without having to
rebuild it.