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

Stuck at opening it with Visual Studio #22

Open
OkiDJ opened this issue Dec 13, 2020 · 5 comments
Open

Stuck at opening it with Visual Studio #22

OkiDJ opened this issue Dec 13, 2020 · 5 comments

Comments

@OkiDJ
Copy link

OkiDJ commented Dec 13, 2020

Shit does not work, still says it can't open. Do not waste your fucking time.

@julianperrott
Copy link
Owner

Anyone else having trouble opening the solution ?

@NKatic
Copy link

NKatic commented Dec 22, 2020

Ofc not, everything works fine, solution is functional. That's prolly some edgy troll who can't install VS so he blames it on the project.

@datcraig
Copy link

datcraig commented Dec 27, 2020

I am not sure if it is the same issue that was originally open, but I am unable to get this working. I was able to get Visual Studio Community 2019 installed and confirmed the proper versions of .NET Framework are there. When trying to run the solution file it errors out with the following:

image

I also see the following output:

image

Looking in the Output referenced paths I don't see a Chrome.exe file there at all. Per the error I have played around with the build properties, but nothing seems to be working from any research done so far. When attempting to build per the error message received I get the following outputs:

image

Any help would be appreciated.

@datcraig
Copy link

Well I feel like a jackass, but I found my issue. I utilized Bitdefender and the on Access Scanning module was flagging the powershell.exe and chrome.exe applications since they were in a different location. Added exceptions to my AV for these paths recopied the project files successfully. I now see the files and was able to run this successfully. Hope that helps someone else.

@julianperrott
Copy link
Owner

You can call the output anything you like, I named it something generic so that it wouldn't be obvious to anything spying on your running processes.

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

4 participants