I have a windows form project that runs/debugs fine when the project is located on my local machine but when copied to a network location the run/debug just doesn't work. No error messages are given. Clicking the tool strip button that resembles a green play button briefly turns grey, nothing happens and then it turns back green ready to be pressed again.
When the project is copied from the network onto yet another machine so that it is local again debugging/running can be performed again as expected.
Has anyone any ideas as to why I can't debug/run the project in the visual studio environment when the project sits on a network?
Related
I had the free trial for the Visual Studio 2019 Enterprise version. Now that it has run out, I am trying to run my build from Unity using that .sln file in visual studio using the community version. I need to use the remote machine option because I am trying to deploy it to the HoloLens. I already tried rebuilding the unity project but I still had the same problem. Is it because when I created this Unity project I was using the enterprise version and now it can't translate the same way over to the community version? Does the community version not have the remote machine capability? I've attached a picture below of what I mean by "the start menu." Back in the enterprise version I would press that little down arrow to expand the Start menu and I would press "Remote Machine," but that option is no longer there when I try to run a .sln build from my Unity project.
Are you sure you have selected the correct project for the startup project? If you have a mistake in setting the startup project, there will only be a Start option under the menu. You can change the startup project from the Solution Explorer, right-click the desired project and choose Set as StartUp Project from the context-sensitive menu that is displayed.
If you still get this issue, can you see the Remote machine field under Project settings’ Debug tab: Configure the project for remote debugging
If yes, you just need to enter the network name or IP address in the Remote machine field, or select Find to search for the device in the Remote Connections dialog box.
If not, I believe you need to repair the VS installation.
I had the same problem. I put my machine in "developer mode" via the Settings and then opened my project in VS 2022. I'm now able to see the "Remote Machine" option.
Earlier I asked a question, which has now been deleted. It was asked me of to come up with some different wording to my question. I'm sorry, but in this case I don't know how better to ask it then I have. Here's what I said:
At work I've got a desktop with Windows 10 on it. Been working there
for 3 years. We using TFS 2015 with TFVC. Recently I was given a
laptop, but without enough disk space, so what I have done is on the
laptop I mapped a drive to the second drive on my desktop, where I
keep all of the Visual Studio projects I work on, that are in TFS. I
had hoped I could just open the project on the mapped drive from the
laptop to the D: drive on the desktop. But VS complained to me. So, is
it not possible to open the same project, on only 1 machine, but being
accessed both on the machine and by a mapped drive from another
machine?
Perhaps it would be best if I illustrated. On my desktop I have a project in my D: drive, so it's located in D:\Src\LRAT. Its in TFS 2015 and we're using TFVC on-premise.
On my laptop I've mapped the drive from the desktop, using D: on the laptop, as D was available. So, I get into VS 2017 on the laptop and try to open the project in D:\Src\LRAT on my laptop. However, trying to do that results in a warning message issued from Visual Studio (the complaint I mentioned earlier) which says:
Team Foundation Server Version Control
The solution you are opening is bound to source control on the
following Team Foundation Server:
http://ourserver:8080/tfs/defaultcollection. Would you like to contact
this server to try and enable source control integration?
This confuses me a lot! I know that its in source control. Why is it asking me if I want it in source control? I want to be able to open it and use TFS/TFVC from my laptop against the same files and folders that are on my desktop. The dialog box that warning pops up in has 3 buttons, Yes No and Help. Clicking Help sends me to a very unhelpful link about Git and VSTS. I don't know what will happen if I click the Yes button, because that project on my desktop is already in source control, so I just click No because I don't know what else to do.
So, this leads to ask is it the case that in some way I don't yet understand opening a project created in VS 2017 and saved to TFS under TFVC on my desktop is different than opening that same project from my laptop connected to the D: drive on my desktop?
The solution you are opening is bound to source control on the
following Team Foundation Server:
http://ourserver:8080/tfs/defaultcollection. Would you like to contact
this server to try and enable source control integration?`
This kind of pop-up info, usually indicate there are some mapping issue related. Please double check your workspace mapping first.
Besides you could also try to connect your project in Team Explorer -Visual Studio follow below steps:
1 View->'Team Explorer'
2 'Manage Connections' (green plug)
3 'Manage Connections' (drop down) -> 'Connect to Team Project'
4 List of projects shows up from your account.
5 Select Project and Connect
More details take a look at this similar issue-- Opening an existing VS2015 solution bound to TFS hangs VS2017RC
I'm a having play with the Magic Mirror 2 using vs2017 to integrate onto my PI 3. As this is my first time with VS I can't seem to get debug to work when trying to run Magic Mirror UWP App.
These are the instructions and app I'm using GIT Hub Magic Mirror
Instructions followed:
In Visual Studio, go to Solution explorer, click on package.appxmanifest > Application and set http://webreflections.azurewebsites.net/create as the start page
On the ribbon, change the target architecture to match that of your PC (e.g. x64)
Set the debugging target to "Local machine" (changing the architecture in step 2 probably did this for you)
Click play to start the app running on your local machine
Follow the prompts on the create experience to save a profile for yourself
If anyone can explain why the program won't run (debug) I'll be extremely happy.
Thank you
I own a Surface RT and I was programming in Visual Studio 2013.
I found the tutorial online on how to set it up but I couldn't do it. Right by the part Visual Studio tries to find remote connections it doesn't find the surface. If I reboot the surface, right about when I open the remote debugger there is a small (10 seconds) period where it becomes available on my Visual Studio to select but it disappears right after never giving me the change to remote debug the app.
Does anyone had this problem before?
You can try adding the Surface's address manually.
Right-click your Windows 8 project, select Properties, go to Debug tab. Here select Target device: Remote Machine and then in Remote machin field enter the address and port your Surface shows you when you run the Remote Debugging Monitor (in the very first message you will see something like Msvsmon started a new server named 'SOMEADDRESS:PORT'. Waiting for new connections.). This usually helps when Visual Studio fails to find the device on it's own.
I have installed the VS 2008 SP1 Remote debugger on the machine running the program I want to debug. I am running the Remote Debugger with no auth / allow anyone to connect on said machine. I am running VS 2008 on my development machine with the project for that application open. I have copied a .dll that i have made changed to the source and rebuilt, locally, to the executing directory of the target program, remotely, including it's .pdb file. I have attached to the process of the remote application though VS and the Remote Debugger.
The break point I put in my project says that it will never be reached because the module is not loaded.
An exception on the remote machine, even when i select retry, dose not cause any effect on my local VS instance.
I want to hit a break point i place locally when the remote application reaches it. How do I do this?
Am i miss understanding how Visual Studio Remote Debugging works?
Is the breakpoint the normal red circle or does it have a caution side in it?
If it's a red circle then the likely problem is "Just my Code" is enabled and VS thinks it's not your code. Go to debugger -> Tools -> Options and disable "Just My code". That should clear up the issue.
If it has the caution sign then hover over the break point and see what the error message says and please post it back as a comment / edit to your answer.
EDIT OP said hollow circle with the "No symbols" tooltip
Open up the modules window (debugger -> windows -> Modules). Then scroll down to the DLL that contains your code. Right click on the window and select Load Symbols. This will likely open the open file dialog. Navigate to your symbols and hit OK.
Have you installed Service Pack 1?
http://support.microsoft.com/kb/957912