I have a bigger project that I would like to transfer to Visual Studio 2017. Project was created in VS15 and everytime I try to load it in VS17, about 5 seconds after the project gets loaded, the program crashes - saying usual "Program has stopped working". Creating new project in VS17 does work normally though, without any crashes.
I tried to delete .vs folder, nothing has changed. I tried to change versions in solution file in my project, nothing has changed.
What happens that it crashes few seconds after the project load?
EDIT: I found it only happens to that one project. So I tried to get further.
Unexpected system error mode before loading package [Microsoft.VisualStudio.Shell.Connected.Packages.OnlineLicensing.OnlineLicensingManagerPackage]
Related
I am updating an older application, for which I had to dig out Visual Studio 2008. The application uses the JET Engine, 'Microsoft.Jet.OLEDB.4.0'
It has an interesting flaw - when I work with it, it out of nowhere gives the error that "The 'Microsoft.Jet.OLEDB.4.0' provider is not registered on the local machine."
Now I have had this so many times, that I know what to do - delete solution and check it out again.
This error is only when running/debugging from Visual Studio. The compiled EXE works all the time
I have checked the folders and tried to just reinstate the database etc etc, but I cannot see what is wrong. Checking updated files by date, there is nothing weird. Only 4 *.vb files. I cannot see any other change.
For some reason it just does not see the OLEDB.40 anymore, but the compiled exe works. Obviously the OLEDB.40 is there, but Visual Studio will not see it.
This error happens at random, from every 10 mins to every 2 days.
Every time I delete the solution and check it out again, and I can work again.
Any ideas?
LATEST: I tried checking the code out to a new place, copying 5 *.vb files and VS2008 can run/debug again.
Checking it out to the original location will not work, nor copying the new checkout into the old place.
But checking it out in a new place and I am back up again...
The issue is related to the path
Using the latest VS update 16.7.4 but happened also on .3 and .2. Working on a Xamarin.Forms project when I first started noticing it, but now it happens on any project when I try to go to the menu and click [Manage Nuget Packages for the Solution].
NPM shows up fine. If I stay on the installed or updates tab it works fine. But when I click the BROWSE tab it shows a list of the latest searches, and then after about 3 seconds the cursor pops up, then vs becomes un responsive and it crashes.
I don't know much about looking at the vs logs to find out what is going on. I happens on every project now, so I don't think removing the .vs or .obj folders have anything to do with it, although I tried it on the Xamarin Project to no avail.
Anyone else seen this?
Nuget PM crashes VS 2019
1) First, disable any other VS installed Extensions under Extensions-->Manage Extensions to check whether a vs extension caused that.
2) clean all nuget caches
3) reset all vs settings under Tools-->Import and Export Settings-->Reset All VS Settings
4) close VS Instance, delete the global nuget.config file under C:\Users\Administrator\AppData\Roaming\NuGet then reopen VS to regenerate that file.
5) check under Tools-->Options-->Nuget Package Manager-->Package Sources
try to use https://www.nuget.org/api/v2/ or http://packages.nuget.org/v1/FeedService.svc/ as nuget.org source.
Also, uncheck other package source and only remain the nuget.org package source.
6) delete bin and obj folder of the project to do a clean step. Also, you can try to install one package on the new project to test whether the issue happens again.
7) try to repair VS and it works as the final step.
When running a project in Test or Debug configuration in VB.NET using Visual Studio 2012, sometimes it gives the following error as the reason for "Build Failed"
Error 1 Could not copy the file "obj\Debug\MyProgram.exe" because it was not found. MyProgram
There are no issues with the code as it was just compiled seconds before this (sometimes I start the program again just to see how everything gets laid out visually and then go back to the code to make Location adjustments)
What I found is this. If I wait , when I go to test compile again -- it just magically starts working again -- Only to fail again later.
Sometimes, I can get 10-15 good compiles before it wigs out.
About my system configuration:
I do not have any other version of Visual Studio or standalone .NET language installed
The paths are set correctly (else it would never compile in the first place.. not just occassionaly fail)
The program can be a simple program with absolutely no code added (aka... New > WinForms Project > Compile)
The project, language (and all requirements), and project output path are on a local drive that is connected directly to the PC internally (using C:\code* for projects and the standard install location for Visual Studio 2012)
I checked the smart data and scanned my hard drive for any errors ... none ever encountered. The temperature of my system (CPU), and the drive is around 25-30 degrees C.
I am really baffled as to why this happens and at random. I have also tried completely clearing out the bin/ folder, and even Moving the project or repointing where the compiled output path is.
Deleting the .suo file helps sometimes, but not all the time.
I believe this is something that may be able to be tweaked in the UI somehow, however I do not know anything about manually linking and compiling programs.
Lastly -- it does not matter whether I run VS in "Administrator" mode (elevated privileges) or as a user.
Some methods that may help you
Have you tried to reinstall Visual Studio. If that does not work you may need to install some of Windows Updates, the compiler may be missing some essential libraries/references to compile your application.
Check your .Net Target Framework, setting your application to a new framework that you don't have installed can stop the application from compiling yet even stop it from being debugged, having a compiler that is to low, this may come with errors for the compiler but not for the IDE/Visual Studio to notice.
Try cleaning your project solution's output folder by right clicking your solution then try to rebuild your project/solution.
Check your compilation references in your project's properties, check if a reference added is not on your computer
Reinstall/Update .Net Framework, same here some requirements may be missing from your installation
Try installing a newer version of Visual Studio, try Vs2013 - this contains various improvements and fixes, Visual Studio 2015 is fast approaching, a recommendation install VS2015 when the full version gets released it will contain a lot of useful features for future .net programming.
Create an new Administrator account and Run VS with Administrator rights and try compiling then, this fixes some of problems in vs and other microsoft products, it might work here.
Install all of the .Net Frameworks from the lowest to current 4.5, this may help when some of the used references/libraries are not on your local hard drive.
if none of these methods work, i would not know of the problem one last thing you could try is installing Windows to another hard drive and try using that installation of windows and see what happens... Hope this helps.
Best regards!
I faced this kind of problem because of my virus guard
blocked my application(but it is not have any harmful code :) )
exclude your project folder from virus guard
or
simply disable it(not recommended)
Recently Edit and Continue with VB.net has been kinda flaky.
In one project in particular. It was working as expected the last time I touched this project.
Recently when I pause the project while the winform message pump is running, I get a message saying no code is running. When I go back to my class file (in the same project, not external) I cannot make any changes - typing does nothing in the editor.
I have another class which is part of this solution, it has no entry point but I thought I would remind VS which was the startup project. This made edit and continue seem to work. I could make changes in the code, but when I continued the old version of the code was what was actually running. It's as if I am in an external class.
I just noticed something else, when you first start the project, edit and continue seems to work fine. After you continue, if you break the code again, it stops working.
I never had edit and continue problems at all with VS2012.
VS was hanging and crashing a lot yesterday so I rebooted my computer. That did not help this problem. I also installed SP1 and that did not fix anything.
I tried compiling to X86 and Any CPU.
Is there a setting I am missing? How can I get this working?
Thanks,
Brad
I tried a few more things based on some suggestion in other forums.
I repaired VS, I reinstalled VS, I tried to restore my default settings. None worked. I tried a simple project to duplicate the issue that I could share to get feedback. I could not get it to not work.
So assuming then the problem was with my project and not VS I made a new project and brought over my forms, modules and classes from project with the problem. I added my references and... edit and continue now works! The only things I changed from the default project were: Target CPU: x86, and Target Framework: .Net Framework 4
I still do not know if there was some corruption or it was a bad setting. This project was originally ported from VB6 many years ago and has been through a few VS upgrades as well.
Recently my VB.Net project failed while building, raising a dialog that said (approximately):
External Tool: VbMyResourcesResXFileCodeGenerator failed due to a System.OutOfMemoryException
I'm posting this question and answer as a public service for future searchers with the same problem - in particular because it wasn't easy to figure out.
Searching for a clue to resolve the issue lead me to this question: Visual Studio 2010 - (OutOfMemoryException) & (Memory increase in Ideal State) - and a suggestion to try the Solution Load Manager to reduce memory use. With only the failing project loaded, immediately after starting VS2010, I could successfully execute 'run custom tool' on the resx file from the solution explorer context menu and then build the application.
However, shortly afterwards the build began to silently fail, much like this poster's situation: Visual studio 2010 IDE build fails mysteriously with no errors or warnings In the comments to his question I found my salvation:
You will have to go to Visual Studio Options dialog and navigate to Projects and Solutions | Build and Run. Change MSBuild project build output verbosity to Detailed or Diagnostic and then analyze the output. That should give you hint on what is the root cause.
Once I did so, I was able to see that, again, the resource.resx file couldn't be built.
The ultimate issue turned out to be a forgotten file resource. I had previously embedded a file as a resource, and subsequently increased that file's size significantly by adding several screenshots. Although I was no longer using the file in my code, I hadn't deleted it as a project resource. It was the size of this file that eventually caused the System.OutOfMemoryException and build failures I was seeing. Once I removed the file from the resources, the solution could be built as expected.