I open up VisualStudio 2017 (latest - just updated). I navigate to a type script file (this might just be coincedence that it's this type of file) and I get the following prompt:
---------------------------
Microsoft Visual Studio
---------------------------
An exception has been encountered. This may be caused by an extension.
You can get more information by examining the file
'C:\...\AppData\Roaming\Microsoft\VisualStudio\15.0_c4122470\ActivityLog.xml'
In my activity log, I get quite a few warnings about packages:
Unexpected system error mode before loading package <enter package name here>
The real kicker is at the end of the file I get an error:
System.NullReferenceException: Object reference not set to an instance of an object.
at
Microsoft.WindowsAzure.StreamAnalytics.UI.ViewModel.JavaScriptFunctionViewModel.GetJSFunctionInputsCount()
at
Microsoft.WindowsAzure.StreamAnalytics.UI.ViewModel.JavaScriptFunctionViewModel.Initialize(JSFunctionInfo configInfo)
at
Microsoft.WindowsAzure.StreamAnalytics.UI.ViewModel.JavaScriptFunctionViewModel.InitializeForEditor()
at
Microsoft.WindowsAzure.StreamAnalytics.UI.ViewModel.JavaScriptFunctionViewModel..ctor(String jsFilePath, Action saveJsFile, Action setJsFileDirty)
at
Microsoft.Cosmos.ScopeStudio.VsExtension.EditorMarginExtension.JavascriptEditorMargin..ctor(IWpfTextViewHost textViewHost)
at
Microsoft.Cosmos.ScopeStudio.VsExtension.EditorMarginExtension.JavascriptEditorMarginFactory.CreateMargin(IWpfTextViewHost wpfTextViewHost, IWpfTextViewMargin marginContainer)
at
Microsoft.VisualStudio.Text.Utilities.ContainerMargin.<AddMargins>b__25_1(IWpfTextViewMarginProvider mp)
at
Microsoft.VisualStudio.Text.Utilities.GuardedOperations.InstantiateExtension[TExtension,TMetadata,TExtensionInstance](Object errorSource, Lazy`2 provider, Func`2 getter)
--- End of stack trace from previous location where exception was thrown ---
at
Microsoft.VisualStudio.Telemetry.WindowsErrorReporting.WatsonReport.GetClrWatsonExceptionInfo(Exception exceptionObject)
I have tried:
Clearing the temp folder
Clearing the Model Cache inside the VS folder
Updating packages
Updating extensions
Nothing seems to help. Does anyone have a thought as to what would be causing this?
Error in Visual Studio… Extension loading issue
According to the error info "An exception has been encountered. This may be caused by an extension.", you can try to run the VS with safe mode using the command: devenv /safemode, if it works fine, that means the installed extensions caused this issue. Since I could not know which specified extension causes this issue based on the error log, you can try to remove/uninstall the installed extensions one by one to find the culprit.
Besides, you can also try to run visual studio as administrator and update the Visual Studio 2017 to latest version.
Hope this helps.
It appears the bug or issue is cause by the back ticks in your JS or TS code, which were present in the files I was working in.
` <- back tick
Here is a thread in the VS developer community describing the issue and a potential solution.
NullReferenceException after opening javascript file
Solution For Me:
I had to upgrade to VS version 15.8.1 (For me ,the bug was still in version 15.8.0, which is what I was using when I posted the question). This version just got released.
So far things are working properly.
Related
I run into Visual Studio and I get an error and ask a question.
I installed POWERVRSDK_2017 and ran OGLESHelloAPI.sln which is a sample file after installation. After the execution, the program was terminated with no response because it was executed after the build without touching the code.
The error occurred in DynamicEgl.h when debugging was executed, and the error content was 'Unhandled exception at 0x760BB3E5 in OGLESHelloAPI.exe: 0xC0000005: Access violation executing location 0x00000000.'
"DynamicEgl.h"
inline EGLDisplay DYNAMICEGL_FUNCTION(GetDisplay)(EGLNativeDisplayType display_id){
typedef EGLDisplay(EGLAPIENTRY * PROC_EGL_GetDisplay)(EGLNativeDisplayType display_id);
static PROC_EGL_GetDisplay _GetDisplay = (PROC_EGL_GetDisplay)::egl::internal::getEglFunction(::egl::internal::EglFuncName::GetDisplay);
return _GetDisplay(display_id);
}
I attached the code. _GetDisplay seems to check for errors, but I do not understand.
How can we solve this problem? Thank for your advise
When I installed powerVR, I clicked Accept Path setting during the installation process and finally it worked normally. I used visual studio 2017.
For some reason, most likely because I do not know how to configure Visual Studio Code. We are talking about the free light version.
It is always showing an error of some type. I am new to this product, NOT VS but this version of it.
How do we set this IDE up correct to work with it?
Here is my current error.
Downloading and configuring the .NET Core Debugger...
Telemetry is: Enabled
log : Restoring packages for C:\Users\Erik Little\.vscode\extensions\ms-vscode.csharp-0.3.7\coreclr-debug\project.json...
info : Committing restore...
log : Lock file has not changed. Skipping lock file write. Path: C:\Users\Erik Little\.vscode\extensions\ms-vscode.csharp-0.3.7\coreclr-debug\project.lock.json
log : C:\Users\Erik Little\.vscode\extensions\ms-vscode.csharp-0.3.7\coreclr-debug\project.json
log : Restore completed in 585ms.
NuGet Config files used:
C:\Users\Erik Little\.vscode\extensions\ms-vscode.csharp-0.3.7\coreclr-debug\NuGet.config
Feeds used:
https://www.myget.org/F/dotnet-core/api/v3/index.json
https://api.nuget.org/v3/index.json
https://www.myget.org/F/coreclr-debug/api/v3/index.json
Telemetry is: Enabled
Error: Can not find runtime target for framework 'DNXCore,Version=v5.0' compatible with one of the target runtimes: 'win10-x64, win81-x64, win8-x64, win7-x64'. Possible causes:
1. The project has not been restored or restore failed - run `dotnet restore`
2. The project does not list one of 'win10-x64, win81-x64, win8-x64, win7-x64' in the 'runtimes' section.
Error:
System.InvalidOperationException: Can not find runtime target for framework 'DNXCore,Version=v5.0' compatible with one of the target runtimes: 'win10-x64, win81-x64, win8-x64, win7-x64'. Possible causes:
1. The project has not been restored or restore failed - run `dotnet restore`
2. The project does not list one of 'win10-x64, win81-x64, win8-x64, win7-x64' in the 'runtimes' section.
at Microsoft.DotNet.ProjectModel.BuildWorkspace.GetRuntimeContext(ProjectContext context, IEnumerable`1 runtimeIdentifiers)
at Microsoft.DotNet.Tools.Publish.PublishCommand.<>c__DisplayClass71_0.<SelectContexts>b__1(ProjectContext c)
at System.Linq.Enumerable.WhereSelectListIterator`2.MoveNext()
at System.Collections.Generic.List`1..ctor(IEnumerable`1 collection)
at System.Linq.Enumerable.ToList[TSource](IEnumerable`1 source)
at Microsoft.DotNet.Tools.Publish.PublishCommand.TryPrepareForPublish()
at Microsoft.DotNet.Tools.Publish.PublishCommand.<>c__DisplayClass0_0.<Run>b__0()
at Microsoft.DotNet.Cli.CommandLine.CommandLineApplication.Execute(String[] args)
at Microsoft.DotNet.Tools.Publish.PublishCommand.Run(String[] args)
dotnet exited with error code 1
Error while installing .NET Core Debugger.
They make it seem so easy to set up but there is always something that i am missing. I have a very good thought that I am not setting up the configuration file correctly because it looks strange to me. Looks like all JS.
Also if I point to a folder that I work in with no issues at all with visual studio enterprise edition I always get this error
eslintrc-error
It keeps looking for eslintrc but i have looked everywhere to resolve this.
I've posted a snapshot of this issue as well.
I know is must be a config issue.
I do not even know what eslintrc is.
Please advise.
It's a linter for ecma... the rc file configures its options.
So you're aware code is an editor, not really an IDE. If you're looking for free I'd suggest Visual Studio Community.
I'm trying to use ros in cpp with Visual Studio 2012. I wrote the publisher and subscriber tutorial (http://wiki.ros.org/ROS/Tutorials/WritingPublisherSubscriber%28c%2B%2B%29) and first, I configure the project as says in the guide (http://wiki.ros.org/win_ros/hydro/Msvc%20SDK%20Projects).
Then i compiled an linked the publisher, but when I tried to run it, ros::init(argc,argv,"talker") throws an exception... The console says that I ROS_MASTER_URI is not defined but I've got it defined
There are 2 images here:
https://www.dropbox.com/s/o12m0l38gaxiugi/error1.png -
https://www.dropbox.com/s/ocdmf0wj6rj0962/error.png
Can anyone helps me?
Thanks in advance
So, I had the same issue, although I didn't set the ROS_MASTER_URI globally.
I managed to get around this specific issue by adding
ROS_MASTER_URI=http://localhost:11311
to the debugging environment variables (Project->Properties->Configuration Properties->Debugging->Environment).
However, after implementing the above I got an uncaught exception (Unhandled exception at 0x768bc41f in ros_demo.exe: Microsoft C++ exception: std::bad_alloc at memory location 0x0028f0e4..).
That went away when I built, compiled and ran the project in release mode (which matched my ROS SDK build).
I got the idea for the release/debug build from here:
xstring isn't an OSG specific object, so the error is elsewhere in the
3rd party dependency chain. As I know nothing about your OS and
software setup I can't speculate what this might be.
In general though this type of error could well be a linking issue -
for instance Visual Studio is hopeless at handling different libs
being built debug and release and will crash randomly.
That was fun to discover..
I am unable to run a windows application in Visual Studio 2008. Program has been working fine until I started getting an error in the Output Window - "
The program '[2260] MUS3.vshost.exe: Managed' has exited with code -2147023895 (0x800703e9). " This happens even before execution of the code begins.
Any help ? Thanks in Advance
I am placing the entire error here
'MUS3.vshost.exe' (Managed): Loaded
'D:\Documents and
Settings\Administrator\Desktop\MUS
TEMP\trunk\Dev\Source\Source\Binaries\MUS3.exe',
Symbols loaded. Ignoring managed
exception from unknown thread.The
program '[2260] MUS3.vshost.exe:
Managed' has exited with code
-2147023895 (0x800703e9).
Hell, this is not quite an answer, but at least it might help someone. I met with something like the above problem, but in Visual Studio 2005 Pro SP1. Everything had been working and then suddenly nothing worked.
I tried all sorts of different things and ideas... even tried simply creating a new windows application and trying to start it in debug mode (same thing happened, same message appeared - my heart broke seeing the following output again and again from the VS debug output window:
'WindowsApplication1.exe' (Managed): Loaded 'C:\WINDOWS\assembly\GAC_32\mscorlib\2.0.0.0__b77a5c561934e089\mscorlib.dll', Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
Process is terminated due to StackOverflowException.
Ignoring managed exception from unknown thread.The program '[1856] WindowsApplication1.exe: Managed' has exited with code -2147023895 (0x800703e9).
Even thought that i maybe messed the .NET versions on my computer. Well, but at least in my case things finally were much simpler, and maybe this applies for my case only (silly me) - but somehow in Application Properties -> Debug tab, the radio button named "Enable unmanaged code debugging" was unchecked. After checking it, more "libraries" seem to be loaded, albeit with no symbols....
and...
magically the program is started normally and the debugger actually steps in on a breakpoint. i don't quite know or suspect why this think worked out like this - any suggestions are welcome!
This Error occurred mostly at that when you move your code from one version of visual studio to another latest version.
In older version if you are using latest framework like 4.5
At initial stage Warning is !(Your Application Not Target the Exact Framework)
Then First you should target the Framework(Click on Project rather than Solution go to properties ->Application set your framework)
Then clean and rebuild. If not working then You should use a Window Form which not manipulate any data from DataBase or create a new folder, in that folder create a new Form then this from Run through the main function. I hope this will work
78692110
if you're using .net 2013, then go to project, then at the property windows go to references and add the references for the Microsoft ADO Data Control ,it will work now
I have a problem with VM-Debugger in Visual Studio 2008 (VMWare Workstation 6.5.3). Always when i try to Start the VM-debugging the debugger tells me the following:
Error: Unable to detect the current startup project.
I only have one startup-project but there are several other projects are in my solution.
The debugger-log says only this:
27.10.2009 14:35:29:
27.10.2009 14:35:29: Debugging started...
27.10.2009 14:35:29: ERROR: pEnumerator->Reset()
27.10.2009 14:35:29: An error occurred in .\Connect.cpp at line 2369.
27.10.2009 14:35:29: ERROR: FindProject(pEV, startupName, pProject)
27.10.2009 14:35:29: An error occurred in .\Connect.cpp at line 2412.
27.10.2009 14:35:30: Error: Unable to detect the current startup project.
27.10.2009 14:35:30: ERROR: DoStart()
27.10.2009 14:35:30: An error occurred in .\Connect.cpp at line 549.
The logs of VMWARE-Workstation-Program say nothing that seems like an error.
I already have tried to build a new solution and add my existing projects, but the same effect appears. I already have re-installed the vmware-visual-studio-plugin. There was noch change.
Do you perhaps know what's the problem and how it could be fixed.
Greetings, Martin
It appears that this is a known issue. However, as far I know, VMWare has not released a fix for this even when there have been reports about this since 2 years.
May be your startup project is under a solution folder. On this case, a workaround is to place your startup project at the main level of your solution.
Depending on the structure of your solution, this workaround may be useful or may not work.
For me, even with this workaround, VM-Debugger reuses to work. On my solution, VM-Debugger only worked with the project that is created on a fresh solution (the very, very first project on any solution). Since we removed that project from our solution, it doesn't matter what we do, VM-Debugger simply does not work.
"One more minor note: If you install VMWare 6.5, it will re-map F6 to "Start debugging in a virtual machine," causing an "Unable to detect the current startup project" error dialog to appear. To correct this, re-map F6 back to Build.BuildSolution. "
(taken from http://mark.michaelis.net/Blog/VisualStudioKeyboardShortcutsForCompilingMSDNFlashDec292008.aspx)
Maybe this will be helpful.