C# program will not run?

Question

1.00/5 (1 vote)

See more:

Hi All,
Bit of an odd one, I have written a quick little app in VS 2008 (.NET2), I brought it into work to make my life easier. The 'thing!' won't run with or without admin rights on Win 11. Possible issues I can think of:

1) Virus Control (Not aware of any)
2) Differences is machine (.NET should handle that, it has in the past)
3) Insufficient rights (but I'm a local Admin!)
4) VS2008 not advanced enough for Win11 (I have used other programs built with it)

Windows ignores a click on the Icon??

Umm is there a setting I am missing or ....

What I have tried:

Running Exe by double clicking also tried to run via Run as Admin.

Posted 26-Jul-23 2:29am

glennPattonWork3

Updated 26-Jul-23 4:42am

Add a Solution

Comments

Graeme_Grant 26-Jul-23 8:31am

You know that we can't see your code on your PC ... Same with the error messages.

There is not enough information to know what is going on.

glennPattonWork3 26-Jul-23 8:49am

Thats the thing, I click nothing happens! I'm wondering if it's some to with a .NET2 program running on Win11...

Graeme_Grant 26-Jul-23 8:54am

It's like you're saying over the phone that your car won't start. If I can't see it, nor hear it, how am I supposed to identify the issue?

glennPattonWork3 26-Jul-23 9:39am

All I can say is I click on the Icon doesn't open (slows right down) doesn't open I don't have any tools to do a more in-depth analysis. I was just wondering if there was a known issue.

CHill60 26-Jul-23 8:52am

Have you tried rebuilding it on that machine?
Included any libraries that may not be standard?
Not used anything that is now deprecated? (Saw someone the other day wondering why his code stopped working on WIN11 and he was trying to open Internet Explorer)
Where are you running it from?
Have you discussed this with your local IT team (thinking group policies may have changed?)

glennPattonWork3 26-Jul-23 9:36am

I would if I could but no Vis Studio, requested it, raised a ticket for it, reply was VS Code is good enough! The IT have the Network falling around their ears at the moment so probably not the best time to bother them

PIEBALDconsult 26-Jul-23 8:57am

I've had those symptoms, but I don't recall the cause or cure.

glennPattonWork3 26-Jul-23 9:39am

So it's not just me!

glennPattonWork3 26-Jul-23 10:45am

Might be if the program uses USB devices or something that change the widget changes state and that breaks something.

Chris Copeland 26-Jul-23 9:12am

Have you tried running it via a command line? If I recall .NET might spit out an error message to the console if there's something wrong with the .NET Framework version or something. You could also try checking the Windows event log to see if there's something there.

glennPattonWork3 26-Jul-23 9:40am

Command Line!

glennPattonWork3 26-Jul-23 9:45am

Just Opened it and run it and a big fat nothing... I wondering if there is a switch in building the Exe I have missed, can't think I did anything different though.

Richard MacCutchan 26-Jul-23 9:25am

Come on Glenn, you know we can't guess anything without seeing your code or how you built it.

glennPattonWork3 26-Jul-23 14:19pm

I made a stupid mistake. The program relies on a serial port being present. On this dang work lappy only when you give it a Serial port via USB. Sorry!

2 solutions

Solution 2

Solved it! Running on a machine with No Serial Ports...Runs fine with Serial Ports Stupid!!

Posted 26-Jul-23 4:42am

glennPattonWork3

Comments

OriginalGriff 26-Jul-23 15:01pm

Ha! Had to be something fairly obvious - and easy to miss.
Well done!

glennPattonWork3 26-Jul-23 15:43pm

A simple error message would have save so much time.

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)

OriginalGriff · Accepted Answer · 2023-07-26T03:43:00

We can't help you - we don't have any way to examine the app or the system it is running on.

My first check would be to look at how you "brought it into work" - did you just copy the EXE file, or did you copy the whole bin/Release folder? Did you make an installer? Are the config files present? Are dependent assemblies installed where needed or present in the EXE folder?
Where did you put the exe before you ran it?

Then I'd be looking at local policies: do IT have any group policies which prevent some apps / assemblies running?

Does it work on a different machine in the same office?

I think there is a good chance you're going to have to disturb the IT department on this one!