If you created your own extensions, you will need to make a few changes for them to work in the new version.
First, open your project, ensure the references are pointing to the latest JustCode DLLs, and then make sure it compiles. If this fails, you will need to update your code to the new API. The list of changes is quite large, but the general concepts remain. If you have a specific problem, please report it.
Now that it compiles, you need to add an assembly attribute. Assembly level attributes typically go in AssemblyInfo.cs located in the Properties folder of the project.
[assembly: SupportsCodeModelApiVersion (2)]
That’s all there is to it.
Extension management is on the roadmap for improvements. If you’re reading this article long after the release of JustCode Q1 2013, the information here may no longer be valid. So here’s a tip for quickly identifying the necessary pieces for JustCode extensions: simply create a new JustCode Visual Studio Extensions project. We keep this template updated for each release, so you can be sure it will work.
If you have any suggestions or comments, please write them below or in the JustCode Feedback Portal.
Happy LESS Coding!
Chris really does wish you happiness, not happiless, and is now considering creating an esoteric, dynamic stylesheet language call HapLESS to ensure you never get what you expect.
Chris Eargle is a Microsoft C# MVP with over a decade of experience designing and developing enterprise applications, and he runs the local .NET User Group: the Columbia Enterprise Developers Guild. He is a frequent guest of conferences and community events promoting best practices and new technologies. Chris is a native Carolinian; his family settled the Dutch Form region of South Carolina in 1752. He currently resides in Columbia with his wife, Binyue, his dog, Laika, and his three cats: Meeko, Tigger, and Sookie. Amazingly, they all get along... except for Meeko, who is by no means meek.
Copyright © 2017, Progress Software Corporation and/or its subsidiaries or affiliates. All Rights Reserved.
Progress, Telerik, and certain product names used herein are trademarks or registered trademarks of Progress Software Corporation and/or one of its subsidiaries or affiliates in the U.S. and/or other countries. See Trademarks or appropriate markings.