-
Notifications
You must be signed in to change notification settings - Fork 87
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
Unable to open visual studio by double click #81
Comments
Hello Yanek! Did you follow these instructions as well?
Please make sure the External Script Editor Args type are set properly. Other then that you might want to try to define the UnityExePath as well in your Projeny.yaml. |
Yep, I followed every instructions. I also tried to start I also had some issues getting Projeny to work; I was not able to link packages from the asset store, and had to add Here's the full Projeny.yaml file I am currently using: PathVars:
UnityExePath: 'E:/Bin/Unity/Editor/Unity.exe'
UnityProjectsDir: '[ConfigDir]/UnityProjects'
SharedUnityPackagesDir: '[ConfigDir]/UnityPackages'
LogPath: '[ConfigDir]/PrjLog.txt'
VisualStudioIdePath: 'E:/Bin/Microsoft Visual Studio/2017/Community/Common7/IDE/devenv.exe' Could it be because Unity, VS2017 and Projeny are installed on a drive (E) while my projects and packages are on another one (D)? |
Hello,
I'm just installing Projeny (0.3.11 binary release) for the first time, and everything works as intended except for the fact that I cannot open any C# script by double clicking the file (in Unity) or an error pointing to it.
I followed the documentation to configure everything, and my
VisualStudioIdePath
is correctly set to'E:/Bin/Microsoft Visual Studio/2017/Community/Common7/IDE/devenv.exe'
.Here's the message I get in the console:
I checked PrjLog.txt multiple times, but it stays empty or contains messages regarding other operations.
Note that I can open VS2017 by going
Projeny -> Packages Manager... -> Open Solution
, and it works just fine.Any help would be welcome.
The text was updated successfully, but these errors were encountered: