-
-
Notifications
You must be signed in to change notification settings - Fork 735
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
Addin Framework parsing fails #1328
Comments
@aateeque how does the #addin directive/in you build.cake |
@devlead I have |
You mentioned using VS Code for debugging, you are the using Cake.CoreCLR and not Cake, am I correct? AFAIK, Cake.ReSharperReports and Cake.AliaSql are .NET 4.5 packages, and does not then work with .NET Core... |
@mholo65 I have tried compiling & running latest master in VS 2015 and observe the same behaviour |
@aateeque Do you have a |
@aateeque can you point us at at complete reproduction of this issue. I.e. Complete cake and bootstrapper you are using, and any other related files. |
To narrow down the problem, I have just got The exception occurs in the I am sure there is a good reason, but intuitively shouldn't that |
@aateeque No, it should be the relative path. The error is exactly what it says, it cannot parse the framework from the addin path. The AliasSQL NuGet package does not follow the naming conventions which should be something like |
@patriksvensson that makes sense then! Thanks. |
What You Are Seeing?
Error: System.InvalidOperationException: Something went wrong when parsing framework.
What is Expected?
Script should run withour error
What version of Cake are you using?
Version 0.16.2+Branch.main.Sha.fb23be463dacfa51c9b19a7cd111149dda7e8c6b
Are you running on a 32 or 64 bit system?
64-bit
What environment are you running on? Windows? Linux? Mac?
Windows 7
Are you running on a CI Server? If so, which one?
No
How Did You Get This To Happen? (Steps to Reproduce)
Attaching debugger to a script that installs any Cake Addin. I am using VS Code and have tried with Visual Studio too
Output Log
The text was updated successfully, but these errors were encountered: