Daniel Cazzulino

You mean the loaded file would not be able to use #load and #r? If so, I think that's fine. The loaded file in that case would be a plain...

The package bundles either the Windows or the Mac version of the assembly (see https://github.com/kzu/mono-nugetized/blob/master/package/Mono.proj#L32-L33) so I don't know why you'd reference it for a Xamarin for Android project. I...

Why do you need to install the nuget package? As I said, the Mono.Security is already part of the reference assemblies that Xamarin for Android installs, there's no need to...

I don’t think the reference will be resolved automatically to the reference assemblies though, so you'd still need to add the other reference, or code will continue to not compile...

Unless we add a targets that conditionally references it.... hm... That might be the simplest solution...

yep, that's fine

@akoeplinger that referenced issue, however, is about Mono on Windows, not XA/XI. I can't see how the windows dll could be wrong since I'm [referencing it conditionally](https://github.com/kzu/mono-nugetized/blob/master/package/Mono.Security.targets#L5) and it's [unpacked...

@marek-safar but the user is referring to using this assembly on windows with Mono, see https://github.com/kzu/mono-nugetized/issues/3...

Would be totally awesome to be able to name nodes. This would make also for a more realistic representation when discussing and brainstorming on the topology things might result in...

Same issue here, against production SignalR service, tried both approaches (class and trigger), as explained in https://docs.microsoft.com/en-us/azure/azure-functions/functions-bindings-signalr-service-trigger?tabs=csharp#with-class-based-model