![]() Within the (which will look very familiar to anyone who has built a VSIX extension before), make sure to modify all the values that you want (these are the values that will show up on the VS Extension Gallery), but leave the “Tags” unchanged. There are two files that need to be updated, the in the VSIX project (the one ending in Extention), and the CustomCodeGeneratorFactory class in the Class Library Project. The first step is filling out the metadata of your Custom Scaffolder. Finally, the template has configured your project and solution settings to correctly launch the experimental instance of VS to test out your Scaffolder on F5. The template has also added dependencies to the .12.0 and .12.0 dlls necessary to interface with the scaffolding framework. The former is a class library project which will contain most of the code for your custom scaffolder, the latter is the VSIX project which will build the vsix that you will be able to share with others (or upload to the VS Extension Gallery). ![]() Now, that your custom scaffolder solution has been created, you will notice that it has two projects in the solution, one named BasicScaffolder1 and the other BasicScaffolder1Extension (with the Italics substituted with the name you gave your solution).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |