-
Notifications
You must be signed in to change notification settings - Fork 51
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
Package Not loading VS2012 #228
Comments
I uninstalled the product and switched to use match (xdt:Locator=”Match(name)”) conditions with Config Source (configSource=”myOther.config”). It appears Visual Studio 2015 (if not earlier) has functionality to accomplish what the Slow Cheetah add in used to provide for us. Sorry this answer doesn't support the product :(
|
I also have same issue on Visual Studio 2013 Premium. |
@ninerats I know its not very kosher to provide an alternative in the github comments, but I managed to get other config files running through the .Net transformations by just editting the .proj file. It says you can get Visual studio to perform a transformation like so
Now when our build server runs it though the deploy process, the deploy output log contains these two entrys |
I've got this error in VS2017, I cannot see the Add-In in my list of Extensions. How do you uninstall it? |
Just tried adding this plugin to our solution which is currently built in vs2012. When i load Visual studio it says SlowCheetahPackage package did not load correctly.
VisualStudio
VisualStudio
Vs Activity log says this:
1261
2017/02/27 15:17:56.335
Information
Begin package load [SlowCheetahPackage]
{9EB9F150-FCC9-4DB8-9E97-6AEF2011017C}
1262
2017/02/27 15:17:56.335
Error
SetSite failed for package [SlowCheetahPackage]
{9EB9F150-FCC9-4DB8-9E97-6AEF2011017C}
80131513
Method not found: '!!0[] System.Array.Empty()'.
1263
2017/02/27 15:17:56.335
Error
End package load [SlowCheetahPackage]
{9EB9F150-FCC9-4DB8-9E97-6AEF2011017C}
80131513
Method not found: '!!0[] System.Array.Empty()'.
Any advice on how to tackle this issue?
The text was updated successfully, but these errors were encountered: