Please integrate the the Nuget SlackBotMessages package into WL7. Would be very useful for cross-platform communication.
https://www.nuget.org/packages/SlackBotMessages
Unfortunately the Assembly Reference Editor doesn't recognize the DLL itself.
#FeatureRequest
https://www.nuget.org/packages/SlackBotMessages
Unfortunately the Assembly Reference Editor doesn't recognize the DLL itself.
#FeatureRequest
Rename
The Assembly Reference dialog is for .net framework assemblies only. As documented, custom assemblies should just be copied into the WL7 installation folder. Be sure to copy any required reference dlls.
According to the NuGet Package, there are 4 reference assemblies, Newtonsoft.Json.dll, System.Runtime.Serialization.Json.dll, System.Threading.Tasks.dll and System.Runtime.dll (netstandard1.5).
But here an old problem appears, which completely confuses the code editor.
If I remove System.Runtime.dll from the WL7 directory, the problem disappears.
However, the code editor fails afterwards because it points to types that are stored in this assembly.
But here an old problem appears, which completely confuses the code editor.
If I remove System.Runtime.dll from the WL7 directory, the problem disappears.
However, the code editor fails afterwards because it points to types that are stored in this assembly.
QUOTE:I wouldn't put that DLL in the WL7 install directory since Windows already has that file in the Windows directory, but ...
If I remove System.Runtime.dll from the WL7 directory, the problem disappears.
... you still need to include a "using statement" pointing to that DLL. Maybe ...
CODE:or something similar would work. Check the Microsoft documentation for exact name of the namespace associated with the System.Runtime.dll assembly.
using System;
Same comments for the System.Threading.Tasks.dll and System.Runtime.Serialization.Json.dll files. I wouldn't include them in the WL7 install directory unless the copies in the Windows directory are too old (Are they?). And I would include a "using statement" pointing to the namespaces for these two DLLs.
@superticker
You're right. Instead of messing up the WL7 folder, it makes more sense to put the whole Slack client into an external Visual Studio utilities class right from the beginn.
The simplest Slack client can be created with the Newtonsoft Json.NET serializer NuGet package, which is already part of WL7. Once the utilities class is compiled, I can easily call the Slack client from the WL7 code editor and send out messages.
You're right. Instead of messing up the WL7 folder, it makes more sense to put the whole Slack client into an external Visual Studio utilities class right from the beginn.
The simplest Slack client can be created with the Newtonsoft Json.NET serializer NuGet package, which is already part of WL7. Once the utilities class is compiled, I can easily call the Slack client from the WL7 code editor and send out messages.
Your Response
Post
Edit Post
Login is required