I've been developing an application In VB.net for the past few months using Visual Studio 2013 Pro and Azure Cloud Services. Thursday when I went to run / debug the application I got an exception vshost32.exe has stopped working. After hours of research, trial and error I was unable to fix it. I uninstalled VS and re-installed it. No Luck :(
I was then frustrated to the point that I wiped my computer, Formatted the hard drives and Installed a clean version of Windows 7 Ultimate and VS Pro 2013. My application still does the same thing.. any idea what the heck is going on here? I have changed the debugger to x86 followed hundreds of solutions online with no luck.
I have now started another application but when I connect to my Azure Files then try to connect to the DB in SQL Server Explorer within VS it literally just crashes Visual Studio goes into debug mode then restarts. I have tried disabling my Firewall and Virus Protection. Can anyone point me in the right direction, I'm bummed right out as it seems I have an application which was nearing completion that is now unusable...
Thanks in advance to Everyone for your help and replies!
Do you encounter the problem when you debug it? I had the same problem when I was debugging it by pressing F11 key when the debugger point is at the sql statement. If you have the same problem, then try debugging it with F10 key.
I also have the problem to connect remote database a month ago. Each time I connect to the remote database, the application (VisualStudio/SSMS) crashed. After reserching, I found the solution for my case.
The source of my problem are:
Visual Studio 2013 or .NET Framework 4.5.1 installed
Some network anaylyzing / detecting tools installed
I don't know whether you are the same case. You can check the link for details.
Related
I have been using Visual Studio 2010 Pro for my vb.net desktop application development. I publish the apps via clickonce to a web server with ftp. My settings look like this:
Publishing folder location: ftp://www.webaddress.com/folder/
Installation folder : http://webaddress.com/folder/
This works perfect in VS2010.
I am now trying to upgrade to Visual Studio 2015 community edition. When I try to publish my app, I get the error "The components for communicating with FTP servers are not installed". I am getting this error on both computers I have installed VS2015 on.
Strangely enough, there isn't much info on this error. The only solution I've seen is to repair the installation. I did this but still a no go.. Another cause I read about is having Xamarin installed, but I have never had that installed.
Has anybody run into this and know what the fix is??
EDIT:
It appears to not actually have anything to do with installed components. After I posted this question, I realized the publish via FTP had worked earlier on a little sample Hello World project i made (brain fart). It was only once I loaded my existing project that this error started showing up.
I closed the solution, created another simple project, and still got the error. I closed visual studio, reopened the sample project, and ftp worked! I then opened my existing project and ftp worked there too?! So I don't know what the trigger is, and I haven't had it fail again yet, but maybe this info will help figure out what is causing the failure.
EDIT (3/30/2017)
Just an update - I am still having this issue. This issue happens on visual studio 2013, 2015, and 2017. I have tried reinstalling the c++ redistributable, still nothing. It seems others are having this issue with a web project but mine is a desktop app publishing with clickonce via FTP. It must be something to do with solution I am working on that was originally created in 2010, as the issue is not present in any other project.
I had the same issue with Visual Studio 2017. What fixed it for me was to start the Visual Studio Installer and install the ".NET Core cross-platform development" workload.
I had the same issue in Visual Studio 2015 / Update 3. It was resolved after installing the 32-bit version of Visual C++ Redistributable Packages for Visual Studio 2013 (https://www.microsoft.com/en-us/download/details.aspx?id=40784)
See also https://github.com/aspnet/Tooling/issues/748
I had the same problem with Visual Studio 2015. And Publish used to work fine so I went going crazy looking for and trying different solutions. Then I read on another thread of doing a Setup-> Repair (submitted by Erikest). I did a Setup->Repair and the publish process now works! I think it's also possible that the Repair not only did the trick on the FTP components but also replaced the C++ redistributable (often mentioned as a solution to this problem),
This is a total work around, but I've noticed I get this error every time I open my app (that originated in VS2010) and try to publish without first opening a sample app. I created a new project and published it to my FTP server. When I receive this error, I close Visual studio, reopen and the open the sample project, publish that app, then open my real app. The publish then works.
This works every time, and seems to be a bug in Visual studio, and probably has something to do with the fact that my app was originally built in 2010.
Maybe this will help somebody else with the same issue. It's a big pain so hopefully MS gets a fix in for this.
I have been banging my head against this problem for many months, re-installed VS over and over and just did a clean install of Windows 10 in the hope it would work but to no avail. By chance I cleaned some old .accdb files from the App_Data folder that I no longer need since I converted to SQL Server database and FTP publishing now works.
So it seems VS does not like the .accdb files but was happy with .mdb files when publishing with FTP.
As soon as I put the file back in App_Data the problem returns. Hope this is some help.
I had the same issue here, I was using the Publish right click option on the project, which had been working fine. What fixed it for me was going back through the publish options and re-testing the connection. Publish seemed to work after that. Maybe it forgot a password or settings?
I also installed the x86 C++ Redistribution Package.
Hope this helps someone who is in the same boat.
After many successful website publishes with Visual Studio 2015 Community Edition, we experienced the "components for communicating with ftp servers are not installed" issue. :(
First attempt at resolution was uninstalling VS Community 2015, then installing VS Community 2017. Received the same error: "components for communicating with ftp servers are not installed" when attempting to publish our business website.
With some work, we found that by uninstalling Microsoft Web Deploy and re-installing, this seemed to fix the problem. We can now use Visual Studio > Publish function to our ftp without problems.
See this link for download of Microsoft Web Deploy components.
https://www.microsoft.com/en-us/download/details.aspx?id=43717
Dont know what broke this VS IDE functionality, but hope this fix helps some.
I encountered the same error with Visual Studio 2019
I fixed it by using the Visual Studio Installer to install the Web Deploy (inc .netcore 2.1) under individual components
I just did a simple "repair installation" in the installer. Worked for me.
I am using Microsoft Visual Studio Community 2019 and had this problem for a while.
The problem went away after I updated about 10 NuGet updates that were over due.
I had the same problem, I closed all the open windows I closed Visual Studio and then I opened again and published and then it worked!
Yesterday, I could work with Visual Studio 2010 without any problem. However, today after I turned on the computer and tried to open my project (Web application with Visual Basic.NET) on VS2010 again, I got a message box showing as below:
Later, I found out after I tried deleting suo file that this message box will show up whenever I open some file in Visual Studio so I tried to run the application. Then, I found another message box popped up as below:
And after I close the message box, I finally got this window
It says:
Compilation Error
Compiler Error Message: The compiler failed with error code -1073741511.
I have searched for the solution through the internet. I have found a few methods that might solve the solution such as scanning for virus, using clean boot. I have also tried repairing and uninstalling VS2010 and .NET framework but none still work. Right now, I have no idea what I should to do make it work again.
Anyway, I realized that there is Windows auto update when I turned off the computer. Not so sure if this related to the problem (I used Window 8.1).
After formatting Drive C to reinstalling everything again, I found out that the reason might be Windows update. I have started from reinstalling Windows 8, all necessary programs (except Visual Studio and SQL Management Studio) and all window updates required for upgrading to Windows 8.1.
When I successfully got to Windows 8.1, I created system restore point and try installing VS2010 and all windows update. The result had caused the same error I posted in this thread.
After that, I restored back to original state and installed VS2010 first. Then installed some of windows updates. This time, I decided to install all updates except the ones that have publish date after 10/11/2015. The result is satisfied. I don't get this error again.
Later, Hans Passant help me find the actual cause of this problem. Please see this link:
Why do I get an error for "__CrtGetFileInformationByHandleEx " when I try to compile
We are getting a application failed to initialize error 0xc000007b. I looked around it seems to maybe be the .NET framework, I also read a possible virus.
Our application is Visual Basic .NET 2010, running on Windows XP, Windows Update is turned on.
What fixes the problem, seems to be temporary, is take my backup copy of the .exe and replace the .exe on the machine, it runs for a few hours. Keep in mind I am 12 hours away or more from the machine, I remote to it using TeamViewer.
Will event viewer or something else give me a better idea of what happened? or more information about the error and it's cause?
I'm far from a Visual Basic guru, so I'm very puzzled as to why this application is throwing this error after running for approximately 2 years.
Can windows update cause this? Does .NET framework update itself automatically?
Thanks for any help.
Well if your program was not recompiled, I'd doubt it's the program itself, but if you have the source code you can try running it through the debugger to see what's going on, and where. Personally I'd try just reimaging your xp system and seeing if that fixes the issue.
Also, isn't xp out of support? I suppose windows updates could affect it. I've seen updates cause older applications to break, so it is a possibility. You can look at the recent updates and roll them back.
So I have a program I've been making in VB for my company through Visual Studio 2013 Express for Desktop and have not worked on it in a couple of months. When I try to open it, I get the following error:
"The VB project "WindowsApplication1" is targeting ".NETFramework,Version=4.5" which is not installed on this machine."
http://imageshack.com/a/img661/6001/DGAfuk.png
I have all of the .NET frameworks installed including all developer and service packs (even language packs). I uninstalled all .NET frameworks and re-installed each of them without any resolution.
I tried to re-install Visual Studio and even tried changing the Framework (one of the options I have) but I cannot view any code or open designer view if I do so. (http://imageshack.com/a/img633/2109/OJaXbr.png)
The strange thing is this computer is the same one I have been developing this application on for months, so I'm not sure what happened over the last 60 days since I launched it.
Does anyone have any clues as to how I can resolve this issue?
Thanks in advance,
Matt
The path to your project must be Les then 256 Character.
That can be the reason of it.
Make sure the path is short "Copy the project to your c drive "C:\ProjectFolder" and try again".
"Unable to start debugging 'C:\Windows\System32\WWAHost.exe'. The Microsoft Visual Studio Remote Debugging Monitor (MSVSMON.EXE) does not appear to be running on the remote computer. This may be because a firewall is preventing communication to the remote computer. Please see Help for assistance on configuring remote debugging."
Searched for similar posts, but didn't found one. If duplicate just inform.
I am not trying to connect to any remote machine. Just testing on my local machine.
Is there any way to solve this issue. (I'm using Windows 8 Enterprise 64-bit, just a javascript project)
Problem solved. Installed Remote tools update from here and working fine. Thanks for responding. Closing the topic.
I had the same problem. I fixed it by changing properties/compile/target platform to x86 instead of Any CPU. It solved the problem in my case. Hope it helps.
This happened to me just now when I had a website set up in IIS for mydomain.com, and set my project's start up url (Local IIS) to mydomain.com, and then launched the project before remembering to add a record in the host files for the domain:
127.0.0.1 mydomain.com
This got me for a good hour before I remembered I never set the record. Adding the record fixed it right away.
Windows 7 x64, VS 2012
In my case, the Remote Debugging Monitor component was installed and the app was clearly configured to debug locally in settings. This was a WinForms app upgraded from VS 2008, .NET 3.5.
Turns out it was the Windows Firewall. By directly running:
C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\Remote Debugger\x64\msvsmon.exe
A firewall dialog appeared where I could allow msvsmon.exe to run. After a VS 2012 re-start, debugging (locally) was fine!
Ensure you have Local Machine selected in this drop-down menu:
Windows 7 x64, VS 2012, VB.NET
I fixed it like this:-
Create a shortcut on your desktop to "C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\Remote Debugger\x64\msvsmon.exe".
Right-click shortcut and select "Properties" from the dropdown menu. Select the "Compatibity" tab, tick "Run this program as administrator" and click OK
Create a shortcut on your desktop to "C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\devenv.exe".
Right-click shortcut and select "Properties" from the dropdown menu. Select the "Compatibity" tab, tick "Run this program as administrator" and click OK.
To start VS2012:-
Double-click the msvsmon shortcut icon (that you created above, to launch msvsmon). Wait for the "Visual Studio Remote Debugging Monitor (Administrator)" window to display before continuing ...
Double-click the "Visual Studio 2012 Professional" shortcut icon (that you created above, to launch VS2012)
In VS2012, ensure standard toolbar is visible.
In VS2012, ensure "Solution Platforms" dropdown (on standard toolbar) is visible and set to "x86".
and debug now works (for me anyway) ...
However after 15 minutes or so, debug may stop working and you may get the msvsmon error again. If that happens, simply close VS2012 and msvsmon and then start again (from "To start VS2012:-" above) ...
Myself and several other developers have been trying to look for a solution for this problem for about 3/4 hours as Visual Studio crashed then this error would occur (twice in 2 days). I then suddenly (after a lot of debugging and trying other suggestions and headbanging) I somehow realised that the file which was highlighted had changed and when I was trying to debug was not the MVC app project, once I changed it to my project's one it then worked.
Hope this helps and saves people from hours of pain!
I also got this error, I usually run sites under a named user (which is also a database user) and forgot to set the Application Pool. (parliament's answer also helped me)
For me this worked in VS2013:
Save your work, close Visual Studio then reopen your project
I encountered this error as well.
The cause of mine was that I had accidentally emptied out the following property
Properties->Debugging->WorkingDirectory
Changing it to:
inherit from parent or project defaults
Solved the issue.
If you are using Microsoft's Azure, try attaching manually the debugger:
I have outlined the steps in the following answer:
https://stackoverflow.com/a/35738995/1057052