I'm trying do deploy and debug my kernel driver.
Host: Win7 Prof, 64-bit
Guest (VirtualBox): Win7 Prof, 64-bit Checked / Win7 Prof, 32-bit
I followed many tutorials but without success.
Vistual Studio claims:
Unable to attach to the process
and
Windows Debugging Extension for Visual Studio
Failure to create process instance prevents debugging
In the other hand Windbg can connect to the VM (with the same configuration) but only during restart of VM.
I'm totally frustrated because no single solution helped.
For eg.:
http://www.codeproject.com/Tips/545835/Kernel-Mode-Debugging-in-a-VM-using-Visual-Studio
http://msdn.microsoft.com/en-us/library/windows/hardware/hh439359%28v=vs.85%29.aspx
I've tried to provision my machines but every time it fails at
Installing .NET Framework (possible reboot)
and
Installing driver test framework
What's more, when configuring new sample project in Visual Studio (NDIS sample driver) then I'm forced to add additional includes because it won't compile but as far as I know it should compile (plain sample project) without any additional configuration.
I had the same error when I ran Visual Studio 2012 non-elevated. Choosing "run as administrator" fixed it.
Related
I'm trying to create a WPF Net Core 5 app from Visual Studio Community 2019 on Windows and publish it with standalone deployment mode (runtime included) for use on linux X64 without having to install the runtime on the target. When publishing, Visual Studio shows an error. Reviewing the log, "The source of the problem could not be determined."
If I select "Framework Dependent" deployment mode it works correctly.
What can be the error?
Thanks.
If I select "Framework Dependent" deployment mode, it works correctly. But I try to avoid installing the runtime on the destination.
WPF is a Windows-only technology, it won't run on Linux. Some cross-platform alternatives that are similar enough are MAUI and Avalonia.
So, I have a project being built and test on Windows platform, since Visual Studio 2017 works and run program most comfortable for me in Windows. Now, that I have completed debug most part of the code, I'll have to change my platform built target to Linux.
I used an external project (lib) to help with the internet control, which it's built target is also Windows.
Both the project are written with under C++17 standards so cross-platform should work fine.
Following the instruction on Microsoft website, I had successfully built a test project on my remote Linux server.
However, all the tutorials seem to ask people to start up a new "Linux Project", in which I did for the test project. The question is, since I already have a project/solution created and the build target is Windows platform, is there a way to switch the build to Linux Remote Build?
I've tried opening project settings, but the "target build" option is always Windows 10 and is not changeable.
My system:
Server: Windows 10 Pro 1511 10586.36 Microsoft Visual Studio 2015 Community 14.0.24720.00 Update 1
Client: Windows 10 IoT Core (build 10586) Raspberry Pi 2.
My question:
I would like to profile C++ native application on Raspberry Pi 2.
But i was unable to find how exactly to do it.
Default profiling launch wizard works ok when using the application which is deployed locally but doesn't work for the case when application deployed remotely.
Here is the link Visual studio 2012 profiling remotely debugged process which is about VS 2012 actually, but it seems that even for 2015 problem is the same.
So is there a direct way to use VS remote profiling tool similar to the local one?
I am using Visual Studio 2012 Ultimate 11.0.60315.01 Update 2 under Windows 7 Pro. I have been doing some non visual development with it for a while with no issues. I have just now created a fresh web forms application. As soon as I go to open the Site.master in "Design View" in the HTML editor VS freezes.
The freee results in me being unable to click elsewhere in the IDE (Menu's, Solution Explorer) etc. so it does not look as if the IDE has hung, rather that it has just stopped responding. The same behaviour is evident if I run devenv.exe /SafeMode. CPU usage is minimal and I have plenty of RAM available.
Any suggestions on how I diagnose and resolve this issue?
Running VS as administrator seems to alleviate the problem.
I have installed Visual Studio Express for Windows 8 on my development system. When I add a project for TDD and build the solution, the IDE crashes -- apparently it is unable to find any tests (even though they are there in code). The "Test Output" window indicates that it is searching for tests, and then the entire devenv crashes.
This was working correctly using the trial version of Visual Studio 2012 Professional, but since uninstalling that and replacing it with VS Express for Win8 I have had no luck in getting MSTest to work without crashing the environment.
Any ideas as to what I might be missing?
It turned out to be a collision with another process on the computer (Garmin update program). With this process stopped, Test Output works as expected. The problem was fixed in VS2013.