Search results

[[Category:NuGet]] [[Category:NuGet packages]] ...tive for .NET Framework development). This article attempts to explain why NuGet is the only delivery vehicle for QuickOPC .libraries that target .NET Core.

...ide. In order for this mechanism to function properly, a full set of NuGet packages used by the application must be known. When building an application, common * Situations in which the full set of referenced NuGet packages/assemblies is not known upfront (such as dynamic loading).

[[Category:Communication packages]] [[Category:MQTT]] [[Category:OPC UA PubSub]] [[Category:Python]] ...ch provides interface to the rest of OPC Labs software. Some communication packages are built-in, i.e. they are always available, do not require additional art

[[Category:Communication packages]] [[Category:OPC UA PubSub]] [[Category:Python]] ...ill end up having to use a NuGet client (e.g. Visual Studio) and install a NuGet package, just for the purpose of reviewing the license terms.

...argely invisible to most .NET developers, because they reference the NuGet packages, and not the individual assemblies. It is also does not affect the code its ...d in Python packages. The main package name is '''opclabs_quickopc'''. The packages hide away from the developer the fact that behind the scenes, Python.NET is

= Library Packages = # [[:Category:Communication packages|Communication packages]]

Name: "nugetpackages"; Description: "NuGet packages (Local Feed)"; Flags: checkablealone; Types: typicalnet full custom product Name: "redist"; Description: "3rd-party Redistributable Packages"; Types: typicalnet typicalcom full custom buildnet buildcom;

...ment), be prepared for the fact that there is a higher number of dependent packages, and you need to review and accept their licenses. ...lier QuickOPC versions, remove the individual assembly references, and add NuGet package references instead (see User's Guide). As an exception, individual

...mework 4.6.1]] [[Category:Event pull]] [[Category:NuGet]] [[Category:NuGet packages]] [[Category:OPC UA Alarms & Conditions]] [[Category:Python]] [[Category:Vi * ''NuGet package distribution format''

...s properly reference the corresponding Microsoft Platform Extensions NuGet packages (they do not contain the individual referenced assemblies). This increases

; NuGet ...and are therefore guaranteed to give identical outcome. In addition, NuGet packages with sample code in C# and VB.NET are also available.

...ct. Explanation to this decision can be found here: [[Why is delivery over NuGet feed used for .NET Core?]] * The installation packages (for Windows) have been renamed to contain "Windows" in their name, e.g. Qu

...include LINQPad examples with them. If you add a reference to one of these packages in LINQPad, the examples will automatically show under the "Samples" tab in

* Added NuGet packages with console-based examples in C# and VB.NET (from DocExamples and UADocExa

* Modified the NuGet manifest so that under .NET Framework, the packages for .NET Standard are not unnecessarily considered as dependencies.