I created a plain ASP.NET 5 (vNext) app from Visual Studio 2015 RC in Windows. I then checked my code into GitHub and pulled it down onto my Mac OS X environment. I have Visual Studio Code installed on it.
I can successfully run the ASP.NET 5 app by running dnx . kestrel from the terminal window in Mac OS X. However, if I change any of the HTML, JavaScript, or anything, I cannot see the change take effect. Instead, I have to kill the process that contains dnx. Then I have to run dnx . kestrel again.
What am I doing wrong? Or is this a bug that's a work in progress?
Thank you!
Related
I have a situation where I need to develop a multi-platform app to run on windows and Raspbian (Raspberry PI OS). Currently, I have an application written in Xamarin Forms WPF for windows and one written in Xamarin Forms GTK for use on the RPI. The issue I am having is, when I deploy the GTK version, I get one of two exception:
Development System:
Visual Studio 2019 on Windows 10 Pro
Framework 4.7.2 and .Net Standard 2.0
Target Systems
Windows 10 (Xamarin.Forms.WPF)
Debian 10 "Buster" (Xamarin.Forms.GTK)
System.DllNotFoundException: libglib-2.0-0.dll : When trying to run with Mono
The library 'libhostpolicy.so' required to execute the application was not found. : When trying to run under dotnet.
The RPI is running Debian 10 "Buster". The OS is up to date and dotnet, mono and GTK have been installed successfully. A simple "Hello World!" console app was build on windows using Visual Studio and executed against both frameworks without issue on the RPI. However, any real app with UI fails with the above exceptions.
Can anyone please provide me with information or point me in the right direction on how to resolve these issues in detail? Most of the information on the web is partial and/or makes assumptions about subject matter knowledge. Which is not really helpful.
I've researched and followed many examples online. However, they either did not work as expected or did not cover the subject of deployment to the RPI (Raspberry Pi). The system has the required frameworks and tools on it. It appears there application is missing configuration files.
I have the problem, that I wrote an executable (windows .exe) in Visual Studio 2019 with Qt 5.12 (x64). It is supposed to be a console (no-gui-, server-) application. And it works just fine. But when I start the application I get not console window. In other applications of the same type I do get the terminal console window. AND (and this is why I wanted that) I can see debug output. I already tried "subsystem:windows" -> "subsystem:console" but with no success. Does anyone know a setting I might change there to get the console showing up again?
I am having an issue with Visual Studio 2017 RC where when I run an MVC and/or WebAPI app using IIS Express the app never actually runs. Instead I get stuck with a page in the browser indicating it is trying to attach and from there it goes no further. If I open another tab/window in the browser and try to navigate directly to the launch URL, it just spins forever. Likewise when I run this using the dot net run command, the app launches and runs fine.
There do not seem to be any errors that I can see, just that the browser spins indefinitely without actually ever loading the page/endpoint.
Note: this occurs for most any circumstance. Newly created project in VS with no changes, known working project from previous versions, etc.
You could follow or upvote the issue: https://developercommunity.visualstudio.com/content/problem/11391/aspnet-core-iis-express-httplocalhost51733-failed.html
Looks like our workarounds meanwhile are
dotnet run
Publish to local IIS. Which is working for me.
(Untested: downgrade from core-1.1 to core-1.0)
If you aren't familiar with VS2017/asp.net:
You have, or can reveal via View Menu-->Other Toolbars :
Debug toolbar --> dropdowncombobutton saying "[green arrow>] IIS Express"
Click on the dropdown downarrow part of the button.
You should see a Run {yourprojectname} option.
This is the equivalent of dotnet run {yourprojectname} from the commandline.
You can configure the options that appear in the dropdown with
Right-click on project in solution explorer --> Properties --> Debug
I had this same issue and after digging around for a while I discovered that I had dotnet preview v1.0.0-preview2 installed under Programs Files (x86) and a non-preview version in x64. I think VS is launching the x86 (preview) version but expecting to see the full version. To fix this, I did the following.
from programs and feature uninstall every visible dotnet core. (note: for me this did not remove the x86 preview)
go to https://www.microsoft.com/net/download/core#/sdk and install BOTH x86 and x64 SDK packages
open command line and from the root directory check run: dotnet --version (at the time of writing it was 1.0.4)
fire up .net core project in VS 2017 and run.
When I did all of the above, I was able to start up the site in IIS Express from VS.
We have an ASP.NET web application already deployed to Azure. I'm trying to create a new development virtual machine (using VirtualBox). Everything seems to work fine. I can run the project locally, but when I click on Publish, I just get a comment in the Output window: "The build has been canceled".
The same project using the same version of Visual Studio 2015 Update 1 can be deployed without any problem from the other development PCs (they are NOT virtual machines, don't know if it matter or not).
I use the latest version of all extensions installed. I have 'repaired' my Visual Studio Installation, just in case.
Any suggestions?
Note : I just tried to publish a new, empty ASP.NET 5 Web Application. I got the same "The build has been canceled" message.
The problem seems to be VirtualBox (or Visual Studio 2015 in VirtualBox). I can't publish any website from any VirtualBox VM but I can publish all of them from the PC where the VM is running.
I use Visual Studio 2013 with IncrediBuild to compile Qt apps. Through the IDE everything works fine, but when running on the command line, BuildConsole never returns.
Process that are running:
BuildConsole.exe
cmd.exe
devenv.com
devenv.exe
MSBuild.exe
Turns out, the qt5appwrapper step was the piece that was never finishing.
I could see this by opening up IncrediBuild's Build Monitor window and seeing that that portion was just going and going and going...
Uninstalling the Qt Add-in 1.2.4 fixed the problem.
This is done by running Qt5VSAddin\uninst.exe. I found it in my start menu under Qt5 Visual Studio Add-in (not from inside Visual Studio).