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

System.IO.FileNotFoundException #93

Closed
thenameless314159 opened this issue Apr 17, 2017 · 3 comments
Closed

System.IO.FileNotFoundException #93

thenameless314159 opened this issue Apr 17, 2017 · 3 comments
Labels

Comments

@thenameless314159
Copy link

Hi, i have an issue when i add ScriptyGenerator as a custom tool i have the following error :

Erreur		Erreur de l'outil personnalisé : System.IO.FileNotFoundException: Impossible de charger le fichier ou l'assembly 'Microsoft.VisualStudio.Shell.15.0, Version=15.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' ou une de ses dépendances. The system cannot find the file specified.
Nom de fichier : 'Microsoft.VisualStudio.Shell.15.0, Version=15.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'
   à Scripty.BaseCodeGeneratorWithSite.GetService(Type serviceType)
   à Scripty.BaseCodeGeneratorWithSite.GetProjectItem() dans E:\Code\Scripty\src\Scripty.CustomTool\BaseCodeGeneratorWithSite.cs:ligne 158
   à Scripty.ScriptyGenerator.GenerateCode(String inputFileContent) dans E:\Code\Scripty\src\Scripty.CustomTool\ScriptyGenerator.cs:ligne 0

I'm on VS2015 with .NET framework project, I use the VS extensions and this happens on every .csx i made with ScriptyGenerator as a custom tool.

The test script doesn't generate itself when i use the custom tool it throw an error just like this :

issue

I've been able to generate some class but it happens magically on some try .__.

@daveaglick daveaglick added the Bug label Apr 25, 2017
@daveaglick
Copy link
Owner

Looks like the VSIX is relying on some references from the VS 2017 SDK. I'm going to try tweaking it a bit to get this resolved in the next release.

@daveaglick
Copy link
Owner

Okay, made the changes and tested them out. I'm going to call this resolved with the next release. If you continue to have problems after 0.7.4 is out please open a new issue.

@thenameless314159
Copy link
Author

I've updated vs to 2017 version therefore it should be fine now, ty ! Great work anyway n_n

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

No branches or pull requests

2 participants