C# solution中的reference 里的nationalinsturment.common总显示有问题

easevelvetpaw 2008-12-14 10:45:57

如题,请问是不是忘记安装NI的什么软件了?

...全文

51 1 打赏收藏转发到动态举报

写回复

1 条回复

切换为时间正序

请发表友善的回复…

发表回复

easevelvetpaw 2008-12-14

打赏
举报

回复

没人用C#写过仪器控制程序的吗?谢谢!

Overview This OPC UA reference implementation is targeting the .NET Standard Library. .Net Standard allows developing apps that run on all common platforms available today, including Linux, iOS, Android (via Xamarin) and Windows 7/8/8.1/10 (including embedded/IoT editions) without requiring platform-specific modifications. Furthermore, cloud applications and services (such as ASP.Net, DNX, Azure Websites, Azure Webjobs, Azure Nano Server and Azure Service Fabric) are also supported. Features included 1. Fully ported Core UA stack and SDK (Client, Server, Configuration & Sample assemblies) 2. Sample Servers and Clients, including all required controls, for .Net 4.6, .NetCore and UWP. 3. X.509 certificate support for client and server authentication 4. Anonymous, username, X.509 certificate (experimental) and JWT (experimental) user authentication 5. UA-TCP & HTTPS transports (client and server) 6. Folder certificate-store support 7. Sessions (including UI support in the samples) 8. Subscriptions (including UI support in the samples) Getting Started All the tools you need for .Net Standard come with the .Net Core tools. See here for what you need. How to create self signed certificates for the sample applications On Windows 1. Open a command prompt in the root folder of your repository 2. Run the script CreateAllCerts.cmd in the root folder of your repository to create the certificates for all sample applications. 3. Alternatively, you can run the script CreateCert.cmd in each sample project folder to create new self signed certificates for the application. 4. The self signed certificates are stored in OPC Foundation/CertificateStores/MachineDefault in each application project folder On Linux 1. Open a command prompt 2. Navigate to the project folder of the sample app, e.g. SampleApplications/Samples/NetCoreConsoleClient 3. Run the script ./createcert.sh to create the certificates for the sample applications. 4. The self signed certificates are stored in OPC Foundation/CertificateStores/MachineDefault in each application project folder How to build and run the samples in Visual Studio on Windows 1. Create certificates for all sample applications. 2. Open the solution UA-NetStandard.sln with VisualStudio. 3. Choose a project in the Solution Explorer and set it with a right click as Startup Project. 4. Hit F5 to build and execute the sample. How to build and run the console samples on Windows, Linux and iOS This section describes how to run the NetCoreConsoleClient, NetCoreConsolePublisher and NetCoreConsoleServer sample applications. Please follow instructions in this article to setup the dotnet command line environment for your platform. Prerequisites 1. Once the dotnet command is available, navigate to the root folder in your local copy of the repository and execute dotnet restore. This command calls into NuGet to restore the tree of dependencies. Start the server 1. Open a command prompt 2. Now navigate to the folder SampleApplications/Samples/NetCoreConsoleServer. 3. Run the script ./createcert.sh on Linux or CreateCert.cmd on Windows to create the self signed certificate for the command line application. 4. To run the server sample type dotnet run. The server is now running and waiting for connections. In this sample configuration the server always accepts new client certificates. Start the client 1. Open a command prompt 2. Now navigate to the folder SampleApplications/Samples/NetCoreConsoleClient. 3. Run the script ./createcert.sh on Linux or CreateCert.cmd on Windows to create the self signed certificate for the command line application. 4. To execute the sample type dotnet run to connect to the OPC UA console sample server running on the same host. To connect to another OPC UA server specify the server as first argument and type e.g. dotnet run opc.tcp://myserver:51210/UA/SampleServer. How to build and run the OPC UA Web Telemetry sample • Go to the Azure portal and create a new Storage account. • Open the solution OpcUaWebTelemetry.sln with VisualStudio 2015. • Open the MessageProcessing\Configuration.cs file to configure the app to use your Azure resources (Storage account and IoTHub). // {StorageAccountName} is the name of the storage account and could be found // under Settings->Access keys->Storage account name of your storage account on the Azure portal. // {AccessKey} is the access key of the storage account and could be found // under Settings->Access keys->key1 of your storage account on the Azure portal. public static string StorageConnectionString = "DefaultEndpointsProtocol=https;AccountName={StorageAccountName};AccountKey={AccessKey}"; // {ConsumerGroupName} is the name of a aonsumer group of your IoTHub. The IoTHub you use is the // one you have created for use with the OPC UA Publisher sample. // You need to create this consumer group via the messaging settings of your IoTHub in the Azure portal. // We recommend that you do not share this Consumer group with other consumers, nor that you use the $Default consumer group. public static string EventHubConsumerGroup = "{ConsumerGroupName}"; // {EventHubEndpoint} is the Event Hub compatible endpoint of your IoTHub and could be found // under Settings->Messaging->Event Hub-compatible endpoint of your IoTHub in the Azure portal. // {PrimaryKey} is the IoT Hub primary key for access with iothubowner policy and could be found // under Settings->Shared access policies->iothubowner->Primary key of your IoTHub in the Azure portal. public static string EventHubConnectionString = "Endpoint={EventHubEndpoint};SharedAccessKeyName=iothubowner;{PrimaryKey}"; // {HubName} is the Event Hub compatible name of your IoTHub and could be found // under Settings->Messaging->Event Hub-compatible name of your IoTHub in the Azure portal. public static string EventHubName = "{HubName}"; • Save the file, rebuild the solution and start it. This will start a local instance of the application. • The solution can also be deployed into a Azure App service. Please use VisualStudio 2015's Azure publishing functionality for this purpose. • Now run the OPC UA Publisher sample, connect to a OPC UA server and publish a node. • You should see the node value on the web page after a few seconds. License This repository includes the UA .NetStandard Stack, sample libraries, and sample applications. The UA .NetStandard Stack follows a dual-license: • OPC Foundation Corporate Members: RCL • Everybody else: GPL 2.0 • RCL enables OPC Foundation members to deploy their applications using the UA .NetStandard stack without being required to disclose the application code. Non-members must disclose their application code when using the UA .NetStandard Stack. • Note: Dual license applies to this repository only; GPL 2.0 applies to all derived repositories (for example 'forks'). For details check the License section below. • All samples are provided under the MIT license. Contributing We strongly encourage community participation and contribution to this project. First, please fork the repository and commit your changes there. Once happy with your changes you can generate a 'pull request'. You must agree to the contributor license agreement before we can accept your changes. The CLA and "I AGREE" button is automatically displayed when you perform the pull request. You can preview CLA here.

This article is designed to be the first in several to explain the use of the EMGU image processing wrapper. For more information on the EMGU wrapper please visit the EMGU website . If you are new to this wrapper see the Creating Your First EMGU Image Processing Project article. You may start with 3 warnings for the references not being found. Expand the References folder within the solution explorer delete the 3 with yellow warning icons and Add fresh references to them located within the Lib folder. If you have used this wrapper before please feel free to browse other examples on the EMGU Code Reference page Face Recognition has always been a popular subject for image processing and this article builds upon the work by Sergio Andrés Gutiérrez Rojas and his original article here[^]. The reason that face recognition is so popular is not only it’s real world application but also the common use of principal component analysis (PCA). PCA is an ideal method for recognizing statistical patterns in data. The popularity of face recognition is the fact a user can apply a method easily and see if it is working without needing to know to much about how the process is working. This article will look into PCA analysis and its application in more detail while discussing the use of parallel processing and the future of it in image analysis. The source code makes some key improvements over the original source both in usability and the way it trains and the use of parallel architecture for multiple face recognition.

开发环境/Development Environment ● Visual Studio 2019 ● .NET Framework 4.7.2 ● Halcon 12 解决方案介绍/Solution Introduction ● AutomationSystem 软件运行主窗体项目。 The software runs the main form project. ● BuildDLL 所有生成的引用DLL集中放置在此处，可通过BuildDLL.sln统一管理需要编译生成的项目。 All generated reference DLLs are centrally placed here, and you can use BuildDLL.sln to unify the management of projects that need to be compiled and generated. ● Calibration 编译生成的标定DLL放置位置。 The location of the calibrated DLL placement generated by the compilation. ● CameraDLL 编译生成的相机DLL放置位置。 Placement of the camera DLL generated by the compiler. ● CommonLibrary 个人常用的工具类项目，含文件读取写入、常用变量类型扩展、控件操作等功能。 Personal tools commonly used projects , including file reading and writing , common variable type expansion , control operations and othe

ComponentOne Studio for WinForms 2013 v1 2/5 共五个压缩文件，请全部下载后解压 Part of: Ultimate | Enterprise 65+ .NET Windows Forms controls, including the ones you can't get anywhere else. Generate a grid with a million rows to a chart with unlimited points. Over 65 .NET Windows Forms controls, including the ones you can't get anywhere else. ComponentOne Studio® for WinForms controls come packed with smart, code-free designers, endless built-in features, superior flexibility, and the outstanding assurance that these controls will stand the test of time. 2013 v1 Now Available! Download the 2013 v1 update to access the new TileControl to achieve a Windows 8 look and feel in your desktop apps as well as feature enhancements for Reports, Editor, and Scheduler. See the what's new details. What's Inside? Chart FlexGrid PDF Reports Scheduler True DBGrid BarCode DataExtender DataObjects DockingTab DynamicHelp Editor Excel Flash GanttView Gauges Input InputPanel List Menus and Toolbars NavBar OutBar Ribbon Sizer SpellChecker SplitContainer SuperTooltip TopicBar Win7 Pack Zip Show Less Why use Studio for WinForms? Best Selling Grids in the Market Best Selling Grids in the Market Since 1991 ComponentOne has been offering two award-winning grids for creating Windows Client applications: FlexGrid and True DBGrid. Each is designed to give you the best performance and features for different types of applications. Both grids offer many out-of-the-box features like filtering, hierarchical data-binding, grouping, printing, and exporting to Microsoft Excel without any additional coding required. See a comparison. All-in-one Reporting Solution All-in-one Reporting Solution With a rich object model for generating reports, several UI controls for previewing, and a report designer for creating and designing reports, Reports for WinForms is your all-in-one reporting solution. Generating cutting-edge reports for your .NET applications has never been easier. You can even integrate your existing reporting solutions (SQL Server, Access, Crystal) into your applications. Mimic Popular Microsoft UIs and Layouts Mimic Popular Microsoft UIs and Layouts Replicate popular interfaces as seen in Microsoft Office and other programs using Studio for WinForms controls. For example, provide a docking UI similar to Visual Studio using DockingTab, create an appointments calendar similar to Outlook with Scheduler, and deliver a complete Office 2010 menu system using Ribbon. These customizable controls can be easily modified to perfectly fit your application. Advanced Charting Made Easy Advanced Charting Made Easy Chart for WinForms comes packed with all the charting functionality you need. You get over 80 chart types, designers for code-free development, flexible and customizable charting elements, visual effects, end-user interaction, advanced mouse-tracking capabilities, built-in analysis features and more. ComponentOne is also the only vendor to provide real 3D surface and contour charts. Smarter Design-time Technology Smarter Design-time Technology Studio for WinForms includes ComponentOne SmartDesigner® Technology that allows you to set the components most common properties and features without leaving the design surface. Set up your entire interface using the design-time wizards, property dialogs, smart tags, and context-sensitive toolbars provided by our smart design-time technology. 300+ Unique Samples 300+ Unique Samples Studio for WinForms stands out from the pack with over 300 unique samples. These samples (C# and VB.NET), which install alongside the controls, show how to do all of the common tasks associated with each control to ease the learning curve. Features and Highlights Show All 65+ .NET Components and Controls Innovative InputPanel Control Best-selling Grids in the Market Microsoft Excel Support All-in-one Reporting Solution Out-of-the-box Scheduling Solutions Mimic Popular Microsoft UIs and Layouts Microsoft Office Visual Styles Advanced Charting Made Easy Handle More Data, Faster Add Spell-Checking Embed Context-sensitive Help Smarter Design-time Technology Support for .NET 4.0 Right-to-Left Support 300+ Unique Samples Unparalleled Platinum Support What's New in 2013 v1? In the 2013 v1 release, Studio for WinForms includes enhancements to popular controls as well as a new TileControl. The new tile control enables developers to achieve a Windows 8 look and feel in desktop applications. TileControl The new TileControl for WinForms allows you to develop desktop applications with a Windows 8 application look and feel. Using the TileControl, you can automatically create tile layouts with great data binding features. Reports Reports for WinForms enhancements include: With C1ReportViewer, you can view your C1PrintDocuments in an easy-to-use, standalone application. Ability to stretch rendered barcodes so that they fit any report design format. Barcodes rendered in the reports can have their width adjusted to the look and feel of the overall report design. Improved the rendering of dashed lines in PDF. Quicker report generation with the ability to now choose which medium to use to provide reference graphics objects, scan specific printer or your screen. Performance improvements and lesser memory consumption. Added the Print method to C1Reports which allows you to print directly from the C1Report object. Editor New comments feature in Editor for WinForms. Comments, similar to Microsoft Word comments, can be added to text. GanttView Added new properties (FirstMonthOfFY and UseStartingYearForFY) to C1GanttView and the Schedule objects, which enable you to specify the first month of the fiscal year and the calendar year when the fiscal year starts. Can now show Progress lines for individual tasks, which allows end-users to better monitor tasks that are ahead or behind schedule. Scheduler With the Scheduler control, you can now view the next seven days schedule right from the context menu. This is only visible when not in the timeline view. For the complete technical details of enhancements, improvements and breaking changes, check out the latest release notes for 2013 v1. What's New in Prior Releases? Take a look at Studio for WinForms's release history to find out what's new in previous releases.

111,131

社区成员

642,542

社区内容

发帖

与我相关

我的任务

社区管理员

加入社区

近7日
近30日
至今

加载中

查看更多榜单

社区公告

让您成为最强悍的C#开发者

试试用AI创作助手写篇文章吧

+ 用AI写文章