I guess to start:
Platform - Win7 x64
Framework - CUDA 5.0 RC using VS 2010
Debugger - Nsight VS Edition 2.2
After each debugging session, I am unable to immediately debug again (if desired) as I'm presented with a Visual Studio error pop-up that states "Value Cannot be null. Parameter name: pSrcNativeVariant". If I rebuild, I am able to invoke the debugging session fine.
The rebuild doesn't completely rid me of this problem though. While in the debug session, if I try to open a CUDA Warp Watch window, I'm presented with the same thing. I've never seen this error before and have not had much success at finding a solution. I'm assuming it has something to do with the way I have something configured, as there's nothing indicative of CUDA in the error (and I have not explicitly used pSrcNativeVariant). If anyone could shed some light or point me in the right direction, I'd greatly appreciate it.
p.s. sorry I couldn't attach the image (not enough rep)
Regards
Nsight 2.2 only supports CUDA 4.2 and 4.1. For CUDA 5.0 support, please wait for Nsight 3.0 which will come late October. Thanks
That sounds pretty strange. I would try an uninstall and reinstall. Uninstall all the CUDA stuff then VS. Then reinstall VS and Nsight (in that order). I'd download the version of Nsight that has the CUDA toolkit bundled.
Related
Afternoon all,
I had been using the Visual Studio 2022 Preview. Recently I decided to switch to the Release version. I uninstalled VS2022 Preview and installed the 2022 Community Release.
The install runs fine and completes with no issues. However when trying to run VS2022 It comes up with the error attached below.
From my talks with MS found at https://developercommunity.visualstudio.com/t/Unable-to-launch-VS-Comunity-2022-after/1596301?entry=myfeedback&viewtype=all It appears VS2022 Community should be running version 17.0 of the .Threading DLL. However no matter what I have tried it refuses to load.
I have run the uninstaller with -F. Re-installed several times.
Attempted to install 17.0 to the GAC but this does not change the outcome
As per the post on the developer community pretty much everything short of re-installing windows (Which I am 100% trying to avoid)
I ran the FusionLog viewer (Attached) and it looks like there is something re-binding this to the 17.1 .threading version however I know very little about how this works and where I might find a solution, Hence, I am here :). Although my post on the DeveloperCommunity is still active I'm hoping a resolution here maybe faster!
Thank you!
I have this error too, and its becouse you dont have defined startup project.
Right click on your startup project and choose "set as startup project".
Actually the above is incorrect, you can't even get to the startup screen.
The correct answer is you need to remove the V15 version of the dll from the GAC. Instructions from MS can be found here.
I have a problem with Visual Studio 2015.
When I start the IDE, it hangs after a short while, and I need to kill the process in Task Manager. Sometimes, I can open a project before it freezes, but then it usually freezes some time after that.
My OS: Windows 7
VS version: 14.0.24720.00 Update 1
Screen shot from ProcessExplorer:
(red marks numbers that keep climbing, the rest are not increasing)
I have created a dump file, but can't debug it...
Can someone please help me?
EDIT: Feb 2017 :
New PC (Windows 10) and newer version (14.0.25431.01 Update 3) do NOT give the same problem.
I had the same issue a while ago.
First, I'd recommend you to disable all extensions you're not interested in using of.
Second, many of VS issues is because of Node.js Tools. Though latest version of which fixes many of them, I highly recommend you to uninstall it if you're not planning to develop node-based apps.
Finally, there's still a lot of performance issues with VS, so we can only hope that Microsoft will fix them in the future.
New PC (Windows 10) and newer version (14.0.25431.01 Update 3) do NOT give the same problem.
I've tried both the ISO and the web installer. Neither works, they both give the same error. I get the splash screen for a few seconds, and then a popup comes up and says that it has simply "stopped working." I've got the latest .NET installed (4.5.2), both Intel HD Graphics drivers and my NVIDIA drivers up to date as well. I've tried all of the solutions I can see that people had for this issue to no avail. Any help would be much appreciated.
Look at ActivityLog.xml and EventViewer (probably for errors in devenv.exe) to get more details. And specify what version of VS13 and any Update packs you're trying to install. Also if you had any previous versions installed and if you're on a 32 or 64 bit system.
the full path of that folder would be c:\users(your user login)\App Data\Microsoft . but make sure you have it set to see hidden files and folders.
And again - which VS13 are you trying?
Try to uninstall:
"Intel HD graphics driver" (generic driver)
Or try an updated graphics driver.
It works for me in Visual Studio 2013 and Visual Studio 2015.
Recently, my coworker and I upgraded our development environment to Win7 x64 with VS2010 Pro. Our application is specifically targeted at x64 platform.
The problem we are encountering is during debugging, when attempting to step through the code (F10), at least 50% of the time VS will simply lock up the application being debugged. The IDE has the appearance of having pressed F5, but the application is not responsive and we have to force stop the application.
Our application is a Client (GUI) and a Server that communicate through .NET remoting.
This is starting to directly affect our productivity, so if anyone has any ideas what may be causing this, please let me know.
There is an outside chance that it might be the debug symbols loading. Check the status bar I think it tells you when the symbols are loading.
This may be a moot point, but have you installed the VS 2010 service pack 1?
There are various bugfixes related to debuggers included.
http://support.microsoft.com/kb/983509
I had a similar problem. it turned out that a higher level program had a different run-time library (multi-threaded debug dll), while my app was simply a multi-threaded debug. Once I converted mine to a multi-threaded debug dll, the freeze stopped happening.
I'm talking about VS 2010 Professional/Ultimate RTM (not express versions).
Google doesn't show much other than stuff about the beta 2 and RC versions.
Will it run OK on a Core 2 Duo E6550 2.33GHz with 3GB RAM and NVIDIA GeForce 8400 GS?
Edit:
How does it go with R# 5.0?
I've been using the Premium RTM daily since release and experienced no problems whatsoever developing with C#/ASP.NET MVC2.
My machine is also similar specs to yours and has been running just fine.
Regarding your edit, I've also been doing all of this with Resharper 5.0 - again, no problems whatsoever.
I haved runed it for since release now, and i must say i have had no problem at all, but hey diden't have any with VS 2008 ether. But evythings works great fast and all this while looking nice :D Eclipse go home .D
I installed VS 2010 Ultimate RTM, in my laptop and its specs is exactly like yours except the Nvidia, and it is working perfectly with no problems.
I've been very impressed with 2010.
Even the Beta and RC releases were stable. I find VS2008 SP1 hanging on average twice a day for me.
So far the only thing to crash 2010 was a third party plugin.
Stability: Good
SVN Support (using ankh): Good
2008 to 2010 project upgrade: Good.
No reason not to upgrade.
The only thing is that it requires 3 restarts on XP and 1 on 7...
I was running the RC for a few months before the RTM version was released, and even the RC version was rock solid as far as I was using it.
I didn't use a stopwatch but I got the impression that it is a bit slower at startup than its predecessor.