Replace the contents of the Execute method with the following code:
Public void Execute(IServiceProvider serviceProvider) If you just type : IPlugin after the class name, Visual Studio will auto-suggest implementing a stub for the Execute Method. Implement the IPlugin interface by editing the class. When prompted, allow Visual Studio to re-name the class to match the file name.Īdd the following using statements to the top of the FollowupPlugin.cs file: using System.ServiceModel Rename the Class1.cs file to FollowupPlugin.cs. In Solution Explorer, right-click the Class1.cs file and choose Rename in the context menu. You cannot assume that the assemblies other than those included in the NuGet package will be present on the server and compatible with your code. You cannot include these assemblies when you register the assembly with your logic. These assemblies are already present in the sandbox runtime.ĭo not include any other NuGet packages or assemblies to the build folder of your project. You must select I Accept in the License Acceptance dialog.Īdding the NuGet package will include these assemblies in the build folder for your assembly, but you will not upload these assemblies with the assembly that includes your logic. Select Browse and search for and install the latest version. In Solution Explorer, right-click the project and select Manage NuGet Packages… from the context menu.
The name used for the project will be the name of the assembly. Open Visual Studio and open a new Class Library (.NET Framework) project using. Create a Visual Studio project for the plug-in Alternately, you can find the complete plug-in solution files here: Sample: Create a basic plug-in. Use these steps to write a basic plug-in. You need to use Visual Studio to write a plug-in. That topic includes instructions to use a PowerShell script to download the latest tools from NuGet.
0 kommentar(er)
