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?
Related
Visual Studio 2019 is not creating and executing a console app like previous versions of VS.
If I open a new project, put this code in Main():
Console.WriteLine("hello");
Console.ReadKey();
and hit F5, the app appears to run, then exit with code 0. The console doesn't wait for a key input to close, and breakpoints in the source do not hit.
The EXE should be in this folder
c:\projects\test-app\bin\debug\
but it is actually in:
c:\projects\test-app\bin\debug\netcoreapp3.0
and when I run it from that location outside the IDE it opens a console and immediately closes it, apparently not running the code in Main().
Going through the exact same steps with Visual Studio 2017 runs the app as expected.
I can live with the final exe being located to a different folder but VS2019 doesn't even seem to be running any of my code. Am I missing something?
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.
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).
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!
On Vista Ultimate (No SP), I installed Qt Creator 1.3 from Nokia, using the Windows Binary installer. When I tried running it, I got a side-by-side error saying:
"The Application has failed to start because its side-by-side configuration is incorrect. Please see the application event log for more detail."
The Event Viewer Logs showed:
"Activation context generation failed for "C:\Qt\qtcreator-1.3.0\bin\qtcreator.exe". Dependent Assembly Microsoft.VC90.CRT,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="9.0.21022.8" could not be found. Please use sxstrace.exe for detailed diagnosis."
Running and sxstrace gave me a log file. I've uploaded the contents at http://cl1p.net/sxstrace/
I've figured it has something to do with different versions of DLLs and the Sxstrace system, and VC90.crt, but I don't know what to do. If it helps, the only other development tool I have installed on my PC is Dev-C++ (and MingW). I have had Visual Studio installed in the past, but its been uninstalled since. Other apps with VC90.crt manifests, like Limewire and Digsby are running fine. Help please?
Try installing the Visual C++ 2008 Redistribuable Package or Visual C++ 2008 SP1 Redistribuable Package.