View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0003450 | Core Components | Implementation Bug | public | 2016-06-13 08:53 | 2016-12-19 19:50 |
| Reporter | Robert Bradford | Assigned To | |||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | new | Resolution | open | ||
| Platform | Any | OS | Windows | OS Version | 10 |
| Summary | 0003450: Why do the OPC Classic Core Components 3.0.106 Require the .NET Framework? | ||||
| Description | In the OPC Classic Core Components 3.0.106 setup programs, none of the exe and dll files in the install kit appear to require Common Language Runtime (CLR). So why does the installer require .NET Framework version 4.5.1 to be installed? | ||||
| Steps To Reproduce | Run the OPC Classic Core Components setup on Windows 7 (or earlier version of Windows). The setup program will prompt you to install .NET Framework version v4.5.1. | ||||
| Additional Information | The OPC Classic Core Components were downloaded from: https://opcfoundation.org/developer-tools/developer-kits-classic/core-components | ||||
| Tags | No tags attached. | ||||
|
|
We have the same question. It is impossible to install .NET 4.5 on Windows XP or Windows 2003 Server. The result is that we cannot install the OPC Core Components on those operating systems, even though OPCEnum does not require .NET framework at all. How can we get a .MSI that does not require .NET framework? Or at least, can you change the requirement to .NET 4.0 so that it can be installed on Windows XP/2003? |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2016-06-13 08:53 | Robert Bradford | New Issue | |
| 2016-11-18 06:40 | Robert Bradford | Tag Attached: .NET API | |
| 2016-11-18 06:40 | Robert Bradford | Tag Detached: .NET API | |
| 2016-12-19 19:50 | asthomas | Note Added: 0007649 |
