The goal
I would like to use a Windows Server 2016 (x64) for remote debugging of UWP applications. The reason? My working PC still runs a Windows 7 instance and it is not possible to deploy an UWP app on a Windows 7 machine.
The problem
I have already installed the Remote Tools For Visual Studio 2015 on the Windows Server 2016 machine and started it on port 4020. Authentication mode was set to "None". I have enabled Developer mode on the server as well. Also I have set up my project in Visual Studio to use the remote machine for debugging.
The problem is, whenever I try to deploy (just deploy, not even debug) my solution to the server, the following happens:
Visual Studio shows the following output:
Deploy started: Project: MyProject.UI.Uwp, Configuration: Debug x86
Starting remote deployment...
Reading package recipe file "C:\SourceCode\MyProject\MyProject.UI.Uwp\bin\x86\Debug\MyProject.UI.Uwp.build.appxrecipe"...
and then hangs forever.
In the meantime, remote tools on the server show the following output:
UserAbc connected.
This indicates there must be at least some communication between my Windows 7 PC and the target Windows Server 2016 machine.
No error message is displayed whatsoever (neither in Visual Studio, nor in the Remote Debugger).
The question
Any idea why the deployment hangs forever without an error message? Or am I trying to achieve an impossible task? Is the Windows Server 2016 capable of running UWP apps at all?
Update
I installed VS 2015 Update 3 directly on the Windows Server 2016. I was able to create and debug a simple UWP app directly on the server so the server is clearly able to run an UWP app. However I am still unable to make the remote debugging working. Maybe the problem is completely on my local Windows 7 PC and has nothing to do with the Windows Server. It is strange that the process hangs while "Reading package recipe file". Could it be that an antivirus is intercepting?
Thanks for your feedback. There is a similar issue when I try to deploy the UWP project to a remote machine on Windows 7. We have communicated about this using our internal channel. Unfortunately, Visual Studio 2015 or Visual Studio 2017 doing UWP development on Windows 7 is not a recommend scenario.
For Visual Studio 2017, using Tools for UWP App Development is not applicable on Windows 7. See Visual Studio 2017 Support for Windows Development.
For Visual Studio 2015, the official support for Windows Universal is "Build only". We can use Visual Studio 2015 to build UWP apps on Windows 7, but some other Visual Studio features for Windows Universal development may be degraded. See Visual Studio 2015 Support for Windows Universal, Windows Store, and Windows Phone App Development.
To develop Windows Universal Apps, Windows 10 is strongly recommended. With Windows 10, you can get the best experience of UWP development.
Related
We have TeamCity with 2 build agents:
VM with Windows 8.1
VM with Windows 10
Some of our projects use MS Build 12, others use MS Build 14. Some use MS Test 12, others use MS Test 14.
I installed the build tools for Visual Studio 2013 and Visual Studio 2015 on both machines. All builds were succesful, but our tests weren't.
Some of the projects configured with MSTest 2013 had failing tests on the Windows 10 VM and some of the projects configured with MSTest 2015 had failing tests on the Windows 8.1 VM.
The exception I get is the same for all the tests. This is the one I get on the Windows 8.1 VM:
System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260882 for more information.
This is the exception I get on the Windows 10 VM:
System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260882 for more information.
Everything worked fine on all of our development machines (some devs use VS 13, other devs use VS 15).
The problem was fixed on the Windows 10 VM by installing Entity Framework 6 Tools for Visual Studio 2013.
As of now the Windows 8.1 VM has the tools for VS 2013 and the Windows 10 VM has the tools for VS 2013 and VS 2015.
As of Visual Studio 2015, the tools are included in the installation of Visual Studio itself. I'm not going to install VS on a build agent (the Windows 10 build agent is also a development machine, that is why it already has the tools installed)...
How can I get this to work on my Windows 8.1 VM, with or without installing the EF tools? Shouldn't installing the build tools be enough for a build agent?
Should
I install github in visual studio 2010 express for windows phone.
How can I do?
I don't recommend integrating git into visual studio.
However, you can use standalone Github application. I've been using it for a long time for my Windows Phone projects, it works OK.
P.S. And one more thing. You shouldn't use VS 2010: the SDK is too old, and is long unsupported. You can, and you should, migrate to visual studio 2012 or 2013 - it supports building apps for windows phone 7.5+
I have developed an application with Visual Studio 2012. I have also created a setup.exe with Install Shield 2010 Premium for my application. My development environment is Windows 8 64-bit, the application is compiled under Release Win32. The developing language is C++.
After building setup.exe, I ran it on another computer that is running on Windows 7 64-bit. An error message box pops up saying MSVCP110.dll is missing or not configured to run on Windows. Any ideas as to why this may be?
I tried installing Visual C++ Redistributable for Visual Studio 2012 (http://www.microsoft.com/en-au/download/details.aspx?id=30679), but it still gives the same error.
Any help would be appreciated.
MSVCP110.dll is really part of VC++ Redistributable package.
Try to install both versions of them: x86 and x64 if your machine is 64 bit.
For 32bit machine you need only x86 package.
When I installed Microsoft Visual C++ and C# 2008 Express, I got "Microsoft Windows SDK for Windows Server 2008" added in.
I want to know if I can remove it and still have all the functionality of Visual C++/C#.
Strange, I remember it was shipped with Vista RTM headers (The Microsoft Windows Software Development Kit Update for Windows Vista version). Looks like Microsoft updated the SDK bundled with Express.
Anyway, the SDK is responsible for a lot of features in Visual Studio. For example, Visual Studio invokes sgen.exe to generate XML serializer assemblies, and call rc.exe to compile a resource script. Chances are you can't get away without it if you are not writing hello-world apps.
What is best way to do remote live gdb debugging and use Visual studio as the front end.
In my case: I have a C++ application (compiled for debugging) running on a Linux server
Can I use Visual studio on my windows machine as a front end to do
live debugging on the C++ application. Is this even possible for a
large scale application (OR)
If above is not possible, can I use eclipse on my windows or on a different linux box to do the same remote live debugging
Any other better IDE options ?
Thanks.
You can easily do it with VisualGDB:
Build your app on the Linux machine and ensure that you can run it.
Install VisualGDB on your Windows machine with Visual Studio.
Run the VisualGDB build server on the Linux machine.
In Visual Studio, create new project, select C++->VisualGDB
In the wizard select Linux Application -> Import Existing -> Import from Remote machine
Select the directory where you have built the Linux app. If it's not based on GNU Make, also specify the build command line.
Specify whether you want to synchronize IntelliSense directories with Visual Studio.
On the last wizard page specify the executable name of your project so that VisualGDB knows what to debug.
When you press "finish", the Wizard will create a Visual Studio wrapper project around your Linux project so that you can edit the files, built the project and debug it from Visual Studio.
There's a more detailed tutorial here: http://visualgdb.com/tutorials/linux/import/
You can try WinGDB.
It is an extension for Visual Studio allowing to develop and debug programs with GDB. Here is how to setup Remote Linux development using WinGDB.
I don't think it's possible using Visual Studio.
It should be possible using gdbserver/gdb combo, but on Windows machine you will need special build of gdb that targets linux. I never tried this, but it should be possible to build.
If you can get this working, then you can use Eclipse or any IDE that supports GNU tools.
Just some recommendation:
You can install a free X server on your Windows machine, such as Xming or Xorg in Cygwin. Then you can do Linux native debugging with eclipse. Just display the eclipse GUI to your X server on Windows. You can interactive with the GUI on your Windows machine.
Now possible with VS2015 + GDB extension, reas MS blog post here: http://blogs.msdn.com/b/vcblog/archive/2015/11/18/announcing-the-vs-gdb-debugger-extension.aspx