I am currently attempting to deploy an app to a Windows 10 tablet running the Creator's Update, over my local network. When I select remote machine and enter my debug settings, I can discover the tablet on my network, and get its address and Authentication mode automatically.
However, when I try to deploy, I get this error:
DEP6957 : Failed to connect to device using Universal Authentication. Please verify the correct remote authentication mode is specified in the project debug settings. 0x8007274C: The network event being waited on triggered an error.
As far as I can tell from the documentation that I've read, this process should be more or less plug and play since the Creator's Update, can anyone explain what I might be doing wrong, or what might be going wrong?
Listed here are my debug settings currently in use.
Update: Since its not the solution I was looking for, I'm not adding it as an answer, but if anyone comes across this looking for a fix and no one has suggested one, the way I ended up working through this is just downloading the remote debugger to the tablet and running the old method for C# apps. I never did find out why the UWP method didn't work.
Related
I am creating a Xamarin android application. Most time consuming is build deployment which everyone known.
I tried to send signed APK via Bluetooth from my development machine to device. It gets successfully deployed, but instantly closes after start.
Have anyone tried this way and is there problem testing in device by copying APK?
You can definitely send the signed APK file (as produced by the build process) via Bluetooth, email or even USB, but it's not likely to offer an improvement on speed.
I do this sometimes when I work from home, as I can't easily connect a device to my work PC (which I'm accessing over a VPN).
If your application is crashing on load when you do that, you've almost certainly got a bug in the application that is causing it.
I have client-server .net application, WCF communication with IIS.
During development I encountered a strange phenomenon:
Once in a while, when I run my application without debug and press a button - it seems like the server doesn't respond to the action.
Then I turn to check the same action on debug mode, and when I try to attach the service to process in oder to debug it - I can't find the w3wp.exe process, which is surely active !
But when I open the inetmgr (IIS Manager) and press Browse to the service site - suddenly the service is found in the Attach to process list on VS, and everything continues to work - with or without debug mode - as if nothing had happened.......
Does anyone experienced something similar, or have any assumption why is this happening?
I am concerned that similar incidents can affect the stability of my system.
Note: Perhaps the phenomenon above occurs after I update the client service reference, but I'm not pretty sure.
Thanks!
I'm not exactly if I will answer your question since it's not clear but let me put answer anyway:
I sometimes get an error in running WCF on my machine and this because I have my host running Local IIS then when I change it to IISExpress it runs without issues.
To change this, right click the project -> properties-> open web tab, locate servers and select IIS Express in dropdown. See image
To understand the difference between the two you can check: http://weblogs.asp.net/scottgu/introducing-iis-express
I constantly run into problems where a program runs fine on my system (installed and in development environments) but fails on a users system.
The best solution I can conceive is to debug the program on the users computer, but that's not practical since it would require me to install VS on their system and move the source code over (and doing so would compromise the integrity of the test environment anyway since it may cause the bug to vanish).
I want to remote debug but what I'm reading from the MSDN says to me "Nope, you can't do that unless both systems are on the same network (all. my. rage.)" :
Network configuration
The remote computer and the Visual Studio computer must be connected over a network, workgroup, or homegroup, or else connected directly through an Ethernet cable. Debugging over the Internet is not supported.
Is there another option I can use to connect to the process that is running on another system outside my network?
A partial solution (for the case that throws an exception).
Instead of trying to reach client app over the Internet, generate crash dump and debug it locally, in a comfort of your home :). Please see MSDN for details.
You can use a tunneling application (like hamachi). This will allow you to connect the other party like you're on the same network. Then you can use the remote debugging option. But even in local network remote debugging works slow and sometimes fail with code-optimized builds. Before using the "remote debugger" (by assuming there is any exceptions) I suggest to log all exceptions to a log file then watch the system. It will be helpful to put .pdb files to the remote system to see the relations between code.
Back on Windows 8.x we had a thing called LoopbackExempt that allowed Windows Store Apps to communicate with the local system for development purposes.
This appears to be still present on Windows 10 for UWP apps.
However, adding an exempt does not work (my apps are still not able to communicate with the localhost).
Doing a CheckNetIsolation does not yield and results:
PS C:\WINDOWS\system32> CheckNetIsolation Debug -n=5bd19b2a-6c63-4dd4-9505-d13f72e46189_ggxdvrfmnj0tt
Network Isolation Debug Session started.
Reproduce your scenario, then press Ctrl-C when done.
Collecting Logs.....
Summary Report
Network Capabilities Status
InternetClient Not Used and Insecure
Detailed Traffic Report
InternetClient Not Used and Insecure
Did they change anything regarding the isolation for UWP? The article to enable the loopback exempt still refers to Windows 8.1?
Thanks in advance!
Just a heads up: the issue no longer exists and was probably a bug in the preview version.
Visual Studio now automatically enables loopback when running a project in the debugger.
Whenever I debug my application (ASP.NET Web Application converted to Web Role), I am able to get to the login page. I go ahead and sign in, debug through that and it seems to work fine, but as soon as it takes me to the landing page after login, DevFC.exe stops working with the error:
An unhandled exception ('System.Net.Sockets.SocketException') occurred in DevFC.exe [8072].
Now, I've searched for the issue and have seen something about DevFC.exe crashing due to VMWare Workstation that listens on the same port (12000) and HTC Sync that also listens on that port. I have neither of those applications on my machine, so I am lost here. Using TCPView (from Sysinternals), I find no other application using that port.
The one thing I do notice is that [System Process] goes crazy creating connections to localhost:12000 once DevFC.exe gets started.
Anyone have some insight on this?
This might sound ridiculous but restarting your machine might solve the issue. If that doesn't work, try your project on a different machine. If the project works then there is an issue with your primary machine try uninstalling then reinstalling the Azure SDK. If the devFabric still crashes on the secondary machine then it's something related to your project.
You might want to take a look at the logs created in the DevFC folder here: %localappdata%\dftemp\DevFCLogs (C:\Users\[user]\AppData\Local\dftmp\DevFCLogs). This will hopefully shed light on the actual error (which in my case, was a conflict on port 12001. Ran netstat -ab afterwards and found it was vmware-hostd.exe. This is a service included with VMWare Workstation 8. I know you said you don't have that, but you may have some other conflicting software).
See this thread as well for more detail.
http://social.msdn.microsoft.com/Forums/en-US/windowsazuredevelopment/thread/7e205afd-4b9a-4387-8e10-99e4b8f27788