EcoStruxure Geo SCADA Expert Forum
Schneider Electric support forum about installation, configuration, integration and troubleshooting of EcoStruxure Geo SCADA Expert (ClearSCADA, ViewX, WebX).
Link copied. Please paste this link to share this article on your social media post.
Posted: 2020-01-30 08:15 PM . Last Modified: 2023-05-03 12:18 AM
Hi, I refer to https://github.com/ClearSCADA/notify.
Cannot build Notify project to create Notify.dll file.
Not sure which processor type should be used with micorSystems.ClearSCADA.DDK
All references appear to be there.
(VS2019 Community does have a known issue with design view. Normally overcome with setting as shown in bottom image).
Thanks,
David.
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2020-01-30 08:23 PM
AnyCPU is only really valid when targetting the CLR itself (i.e. for class libraries that will be hosted by another executable etc).
For something that will be interfacing into Native applications (which most of ClearSCADA is) you will need to pick an architecture (x86/x64). What I normally do is have MSBUILD configurations which do an x86 pass, and then an x64 pass, and pass these into my WiX installation project to bundle into an MSI. But I think this is well in advance of what you should be doing.
I would recommend you to configure your target as either x86 or x64 based upon what you will be testing it with. I would imagine it would be a x64 processor, likely running a version of x64 Windows Server. So you'd want to target x64.
You need to make sure that you obtained your ControlMicrosystems and ClearSCADA DLLs from the appropriate location (C:\Program Files\... for x64, or C:\Program Files(x86)... for x86).
Design view itself is quite meaningless. I'm surprised that it even comes up. You should probably just right click on the .cs file and select View Code anyway. It's the raw C# that you would care about. There's no GUI overlay that I'm aware of for these applications from Steve.
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2020-01-30 08:23 PM
AnyCPU is only really valid when targetting the CLR itself (i.e. for class libraries that will be hosted by another executable etc).
For something that will be interfacing into Native applications (which most of ClearSCADA is) you will need to pick an architecture (x86/x64). What I normally do is have MSBUILD configurations which do an x86 pass, and then an x64 pass, and pass these into my WiX installation project to bundle into an MSI. But I think this is well in advance of what you should be doing.
I would recommend you to configure your target as either x86 or x64 based upon what you will be testing it with. I would imagine it would be a x64 processor, likely running a version of x64 Windows Server. So you'd want to target x64.
You need to make sure that you obtained your ControlMicrosystems and ClearSCADA DLLs from the appropriate location (C:\Program Files\... for x64, or C:\Program Files(x86)... for x86).
Design view itself is quite meaningless. I'm surprised that it even comes up. You should probably just right click on the .cs file and select View Code anyway. It's the raw C# that you would care about. There's no GUI overlay that I'm aware of for these applications from Steve.
Link copied. Please paste this link to share this article on your social media post.
Create your free account or log in to subscribe to the board - and gain access to more than 10,000+ support articles along with insights from experts and peers.