Visual studio community exe not running at all

Question

5.00/5 (1 vote)

See more:

VS2017

I only started coding on visual studio community today and made a really simple in Visual Basic Universal Windows app. Just a button that exits the program again to test things out.
BUT I cant for the life of me figure out how to get it to run without visual studio.
I've tried both building in debug and release and neither of the exe files produced in the bin folder even try to run.
I'm very frustrated at this point and need some help

What I have tried:

I've tried both building in debug and release and neither of the exe files produced in the bin folder even try to run.

Posted 11-Apr-18 0:25am

Member 13773783

Updated 12-Apr-18 22:25pm

Add a Solution

Comments

Jochen Arndt 11-Apr-18 7:44am

Run them first within VS using F5 (with debugging) or Ctrl+F5 (without debugging). Do it first with the debug build and F5 so that you got notified about any problems.

When it then executes as expected, the created executables should do it too.

Member 13773783 11-Apr-18 14:18pm

it passes the debugs but the executables in the bin/x84/debug folders don't launch. I've tried clicking on the ones in the obj folder and doing builds in x64 too. None of it works.

Jochen Arndt 11-Apr-18 14:36pm

"it passes the debugs"
What does that mean?
Does it run when exeting it from VS (F5)?

When pressing F5 from within VS it will execute the same executable but under debug control.

Member 13773783 12-Apr-18 4:49am

"passes the debugs" as in the executable runs as expected via VS with no found errors/bugs. The problem is that it wont launch externally without the aid of VS

Jochen Arndt 12-Apr-18 6:14am

I will repeat and refine my question:
Does it execute when using F5 or a Start option from the Debug menu?

The options from the Build menu (F7) will build the application but not execute. When a build succeeds without errors it does not mean that the application is working. That is the reason for having a debugger which executes the application under it's control allowing to stop execution and inspect variables.

Member 13773783 13-Apr-18 3:56am

Yes. It does.

Jochen Arndt 13-Apr-18 4:18am

I finally know the reason and will provide an answer. The keyword is "Universal Windows app".

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Jochen Arndt · Answer 1 · 2018-04-12T22:26:00

Solution 1

It can't be executed because you are not building a desktop application but a Universal Windows Application.

These must be packaged first and then installed to be executed stand alone. See Packaging UWP apps - UWP app developer | Microsoft Docs[^].

Posted 12-Apr-18 22:26pm

Jochen Arndt