Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NetPrintsEditor.Exe not Opening #86

Open
evanricard opened this issue Aug 19, 2019 · 3 comments
Open

NetPrintsEditor.Exe not Opening #86

evanricard opened this issue Aug 19, 2019 · 3 comments

Comments

@evanricard
Copy link

Hi RobinKa, fantastic addition to the .NET space. I'm going to try to interop this with F# somehow possibly. I was really enthusiastic to try out your project so I downloaded the standalone release but, unfortunately, the executable did not execute properly I think and thus did not open any window. I do have .NET core 3 (3.0.100-preview6-012264, to be specific) on my machine.

I tried looking at Event Viewer to see if there was any reason for the silent failure...this is not the first time I have had executables just not open on my computer so it very well could just be my machine.

In any event thanks!

@zh5243a
Copy link

zh5243a commented Nov 19, 2019

me too

@RobinKa
Copy link
Owner

RobinKa commented Dec 5, 2019

Not sure honestly, I tried downloading and running both the standalone and framework-independent one and they worked for me. Your best bet is probably cloning the repository and compiling it yourself (also the new version targets .NET Framework instead of Core because the VS extension wouldn't work otherwise, so if you want to run on Core you can just change that and it should just work hopefully).
You could also use the extension within Visual Studio https://marketplace.visualstudio.com/items?itemName=NawTora.NetPrints

Since I don't have a better place to post this right now: I still intend to keep working on this, I just haven't found the right combination of time and motivation yet :)

@evanricard
Copy link
Author

Ah okay, no problem, thanks for getting back to me @RobinKa . Provided dependencies are in order, one fix I found was to just open up a powershell in that directory then hit the executable that way...then it would open that way for whatever reason!..

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants