I met a highly disturbing issue. I wrote a C# application in Visual Studio Community which uses a local .mdf database file.
My computer's operating system is Windows 10 Home, 64 bit. My problem is that I cannot run the compiled EXE file on certain computers. Previously I used it on a computer running 32-bit Windows 7 Professional, with no problems.
After upgrading it to Windows 10 Pro, 32 bit, the application starts, but it crashes when it comes to an SQL command:
"The application was unable to start correctly. 0xC0000142".
I reinstalled the Microsoft SQL Server 2014 Express Local database, performed a system cleaning but the problem persists. My setting in Visual Studio is 'Any CPU'. I tried to run the EXE in the debug folder and also the one in the release folder. On 64-bit Windows Home everything is just fine with either of the .exe files. On 32 bit Professional, on the other hand, 0xC0000142 error again.
I tried another computer with 64-bit Windows 10 Home and Microsoft SQL Server 2014 Express Local DB: the application runs without problem. I guess some DLL files cause the problem, but neither can I track the source of the problem nor fix it. Does anybody have any suggestions?
Related
I have developed a desktop application in c# & SQL server 2012 using Visual Studio 2013. I have included the reference for Microsoft.VisualStudio.DebuggerVisualizers and set copy local : true.
The application runs perfectly on client systems with windows 8, 10.
But its showing this error while installing on a windows 7 system.
- OS Windows 7 Ultimate
- already installed .NET Framework 4.5
- installed Report Viewer.exe 2012
- installed report viewer.msi 2010
- installed sqlclr types
- the system doesnt have any microsoft c++ redistributable , i am not sure whether it has any impact.
I checked in the assembly folder, but couldnt find the Microsoft.VisualStudio.DebuggerVisualizers.dll
Am I missing any prerequisites here? How to solve this issue so that i can install the application
Error Message
It needs the Microsoft.VisualStudio.DebuggerVisualizers.dll in the global assembly cache. The GAC is the area where libs are placed which can be accessed from all of the system.
It's kinda a ugly fix but you could place this lib in the same or subdirectory of the same directory where the application is.
Is it possibly that you haven't installed VS on that Win7 machine but on the others?
Unintentionally the Microsoft.VisualStudio.DebuggerVisualizers.dll had been included in the project reference. And in the client system the specified dll could not be found even after trying to install it. Hence I removed it from reference and then it worked perfectly fine without any issues. I guess instead of report visualizer i have included debuggervisualizer. It was a manual error.
Thank you for your support
I am using Visual Studio Express 2015 to build an application that reads a SQL Server CE database (I was reading a SQLite database but want to change, the sqlite program work fine). When I build on on machine it runs fine.
When I copy the binary and .sdf file to another machine (I have tried Vista and Windows 7, both 64 bit), the program hangs when starting. It never comes back. I can't even kill the process. I have to reboot.
I thought it must be something I am doing so I downloaded the source for CompactView and it does the same thing however if I install CompactView from the installer it runs fine.
Any ideas that would cause my program to hang and never return?
Also I am building for x86 and .net framework 4 client profile
The reason is that Avast was blocking the program from running. Once I disabled Avast it ran fine.
It could be permisions.windows vista & windows 7 have stricted permision policies.try in other folder
I am having problem getting the MS Visual Studio Remote Debugger to connect to my local IE instance as it is running as a 64-bit rather than a 32-bit process.
Every time I try to run it currently in Visual Studio I get the
The 32-bit version of the Visual Studio Remote Debugging Monitor (MSVSMON.EXE) cannot be used to debug 64-bit processes or 64-bit dumps".
error.
Investigating a bit, I think I have narrowed it down to the web asp service being run as a x64 process rather than a x86 (which both Visual Studio, and the silver light application are running as). I confirmed it as running as a 64-bit process by trying to "attach" visual studio to the process when the application was running in the ASP.Net Development Server.
In short: Is there a setting I am missing somewhere to force Visual Studio to run the ASP.Net service as a 32-bit process? I have read about using a variable in the web.config application pool to use 32-bit (via the enable32BitAppOnWin64 config option), but it seems to only work in IIS, not ASP.net Dev server.
Any thoughts?
Edit For Clarity:
I am running Windows 7 64-bit, Visual Studio 2010 (which is running as a 32-bit process). Currently it is launching ASP.NET Development Server (not IIS) to host the back end web service. I am hoping I can simply "fix" this via a setting, but if not my backup would be to run IIS Express.
If I'm understanding you correctly you should do this:
IIS Manager/Application Pools-> choose the correct pool for your application/Advanced Settings/Enable 32-Bit Applications->set it to true !
I had problem like this in the past which cost me 1-2 days, hope this helps !
Check also Project/Properties/Build/Platform target->this should be Any CPU
(Background: Just started using VC# and .NET)
Hi, I have a simple project which I started developing on Win7 (Pro), using VC# Express edition. It works well when I send it to the client who wanted to use it on Win7 Pro. I used to use "Build -> Publish" to generate the setup.exe and the relevant files. (Both development and client machines are very similar, Win7 Pro, 64-bit etc)
However, now the requirement changed and the client wants to use it on a different machine which is on WinXP Pro (32-bit) and it doesn't have an internet connection (it cannot be ever put on internet).
I used "Any CPU" option, made sure that the .Net version matches (Both have ver 4.0 Client profile". Since this PC will not have internet connection, I unchecked "Create setup program to install prerequisite components".
The program installs on the XP machine, but when it tries to launch it displays an error dialog "encounted a problem, need to close, send an error report to MS".I am not before the XP machine,so I don't know the "details" part of it.
I installed VC# 2010 express on the client machine and tried to open the solution file, but I get an error saying that the solution file cannot be opened because it was created with a newer version of VC#.
Ideally I would need to generate an installation file, which will uninstall the previous version and use a newer version (we need to go back and forth on any changes). But that is not a requirement as of now.
Any idea how should I go about getting this program installed on a WinXP machine? I don't have access to an XP license to test it in a virtual machine.
Thanks.
i finally finished a proyect i was requested in my university with Lightswitch. Im ready to deploy (publish) next week, and i was JUST told that the people that will recieve the software, are using XP machines. I've read a lot of questions and lots of fixes, to get Lightswitch working on Windows XP, like:
Changing the DumpBin with "editbin vslshost.exe /SUBSYSTEM:WINDOWS,5.01 /OSVERSION:5.1"
deploy it as a desktop application with the services deployed to IIS (i dont think this will work because those are really old pc's)
install all the prerequisites manually and launch the ClickOnce application directly from deployment manifest file (.application)
create a sample ClickOnce application using Visual Studio 2010 OR Visual Studio 2008 with the same name as mentioned in Visual Studio 2012 and publish it. From the published location take the setup.exe bootstrapper and replace the existing setup.exe bootstrapper created using Visual Studio 2012
With all of this workarounds available, i NEED to ask, will this ultimately work? Can someone REALLY tell me that using one-or-all of this workarounds i WILL be able to deploy the application!?
Someone?
The 2-Tier Deployment issue on XP was also addressed in VS 2012 Update 2 IF you upgrade to a "V3" LightSwitch project by right-clicking on the root project in Solution Explorer and selecting "Upgrade Project". This updates the project to the "V3" project system, runtime and will use a much newer publish wizard. The version of VSLSHOST.exe that ships with VS 2012 Update 2 is compatible with XP.
Dave Kidder - LightSwitch team
http://social.msdn.microsoft.com/profile/dave%20kidder/
I have a successfully deployed application using the 3-tiers running as an out-of-browser (desktop app) on XP. Initially I was going to do the 2-tier deployment, but I was unable to get a workaround to work.
So I have one server, which runs IIS as well as my SQL server (OS is Windows Server 2003, but doesn't have to be.)
The client machines range from Windows XP to Windows 7, and I haven't had any special problems with windows XP.
So I can definitely say XP will work as a client. I was unable to get it to run the middle tier (hence IIS on the server) but I didn't try every last idea I found, so I won't say it's impossible.
The two links I found most helpful in the process were
http://blogs.msdn.com/b/bethmassi/archive/2011/03/23/deployment-guide-how-to-configure-a-web-server-to-host-lightswitch-applications.aspx
and
http://blogs.msdn.com/b/bethmassi/archive/2012/03/29/lightswitch-iis-deployment-enhancements-in-visual-studio-11.aspx
Hope that helps.