Forum Replies Created
-
AuthorPosts
-
kumajaya
Participant@Mikhail Web plugin to show server information for admin only will be a good add-on but Rapid SCADA is a very complicated software. It’s good if you can create a simple example web plugin in the community repository for us.
kumajaya
Participant@Mikhail A good or a bad idea? https://drive.google.com/file/d/1utNnWR4-kXuTepxcD03yoQtjjSb-SbFF/preview
– Partial PWA support
– OS info on about page
– User agent info on user profilekumajaya
ParticipantHi @Mikhail To make device log more readable, you can install consolas font via winetricks using “winetricks consolas” command.
kumajaya
ParticipantFor en-GB culture: ScadaWeb/lang/ScadaData.en-GB.xml
kumajaya
ParticipantJust a little worried because no confirmation after back connected.
I found a glitch on mobile browser in portrait mode and found it the printer icon move down because no horizontal space left.
kumajaya
ParticipantI have a Windows application that only works on Wine staging, that’s why staging version installed on my computer.
kumajaya
Participantwine –version output:
wine-7.18 (Staging)
No special modification here, our current source should be run on Wine.
kumajaya
ParticipantUsing Ubuntu 20.04 and Wine staging here.
kumajaya
ParticipantA great way out. I love it 😀
kumajaya
ParticipantThe simplest method still:
https://github.com/RapidScada/scada-v6/pull/16/commits/71114c0ca8d0b671f22691053ddb9035249f5791
based on instructions from:
https://www.nuget.org/packages/Microsoft.NETFramework.ReferenceAssemblies/
kumajaya
ParticipantMonoDevelop create a bit more simple changes with a same packages.config contents:
@@ -53,6 +53,9 @@ <Name>ScadaCommon</Name> </ProjectReference> </ItemGroup> + <ItemGroup> + <None Include="packages.config" /> + </ItemGroup> <Import Project="$(MSBuildToolsPath)\Microsoft.CSharp.targets" /> <!-- To modify your build process, add your task inside one of the targets below and uncomment it. Other similar extension points exist, see Microsoft.Common.targets. @@ -61,4 +64,5 @@ <Target Name="AfterBuild"> </Target> --> + <Import Project="..\packages\Microsoft.NETFramework.ReferenceAssemblies.net48.1.0.3\build\Microsoft.NETFramework.ReferenceAssemblies.net48.targets" Condition="Exists('..\packages \Microsoft.NETFramework.ReferenceAssemblies.net48.1.0.3\build\Microsoft.NETFramework.ReferenceAssemblies.net48.targets')" /> </Project> \ No newline at end of file
Both need a manual nuget CLI command to restore package:
mono /usr/local/bin/nuget.exe restore ScadaCommon.Svc/ScadaCommon.Svc.csproj -PackagesDirectory packages
-
This reply was modified 2 years, 10 months ago by
kumajaya.
kumajaya
ParticipantYes, we can use VS 2022 to add nuget package Microsoft.NETFramework.ReferenceAssemblies.net48 with a complex change to ScadaCommon.Svc.csproj and packages.config added with content:
<?xml version="1.0" encoding="utf-8"?> <packages> <package id="Microsoft.NETFramework.ReferenceAssemblies.net48" version="1.0.3" targetFramework="net48" developmentDependency="true" /> </packages>
As a patch to ScadaCommon.Svc.csproj:
@@ -12,6 +12,8 @@ <TargetFrameworkVersion>v4.8</TargetFrameworkVersion> <FileAlignment>512</FileAlignment> <TargetFrameworkProfile /> + <NuGetPackageImportStamp> + </NuGetPackageImportStamp> </PropertyGroup> <PropertyGroup Condition=" '$(Configuration)|$(Platform)' == 'Debug|AnyCPU' "> <DebugSymbols>true</DebugSymbols> @@ -53,7 +55,17 @@ <Name>ScadaCommon</Name> </ProjectReference> </ItemGroup> + <ItemGroup> + <None Include="packages.config" /> + </ItemGroup> <Import Project="$(MSBuildToolsPath)\Microsoft.CSharp.targets" /> + <Import Project="..\packages\Microsoft.NETFramework.ReferenceAssemblies.net48.1.0.3\build\Microsoft.NETFramework.ReferenceAssemblies.net48.targets" Condition="Exists('..\packages\Microsoft.NETFramework.ReferenceAssemblies.net48.1.0.3\build\Microsoft.NETFramework.ReferenceAssemblies.net48.targets')" /> + <Target Name="EnsureNuGetPackageBuildImports" BeforeTargets="PrepareForBuild"> + <PropertyGroup> + <ErrorText>This project references NuGet package(s) that are missing on this computer. Use NuGet Package Restore to download them. For more information, see http://go.microsoft.com/fwlink/?LinkID=322105. The missing file is {0}.</ErrorText> + </PropertyGroup> + <Error Condition="!Exists('..\packages\Microsoft.NETFramework.ReferenceAssemblies.net48.1.0.3\build\Microsoft.NETFramework.ReferenceAssemblies.net48.targets')" Text="$([System.String]::Format('$(ErrorText)', '..\packages\Microsoft.NETFramework.ReferenceAssemblies.net48.1.0.3\build\Microsoft.NETFramework.ReferenceAssemblies.net48.targets'))" /> + </Target> <!-- To modify your build process, add your task inside one of the targets below and uncomment it. Other similar extension points exist, see Microsoft.Common.targets. <Target Name="BeforeBuild">
-
This reply was modified 2 years, 10 months ago by
kumajaya.
kumajaya
ParticipantI’m not familiar with VS. The compiler try to find .NetFramework v4.8:
error MSB3644: The reference assemblies for .NETFramework,Version=v4.8 were not found. To resolve this, install the Developer Pack (SDK/Targeting Pack) for this framework version or retarget your application. You can download .NET Framework Developer Packs at https://aka.ms/msbuild/developerpacks
and add per https://github.com/Microsoft/dotnet/tree/main/releases/reference-assemblies instructions:
<ItemGroup> <PackageReference Include="Microsoft.NETFramework.ReferenceAssemblies" Version="1.0.3" PrivateAssets="All" /> </ItemGroup>
fix it.
kumajaya
ParticipantIt’s normal because no object reference anywhere yet. In VS Code terminal type:
dotnet build ScadaCommon.sln -c Release
You will got your first error because of cross compiling Windows app on Linux, modify ScadaCommon.Forms.csproj like:
<Copyright>Copyright © 2022</Copyright> <EnableWindowsTargeting>true</EnableWindowsTargeting>
Run again dotnet build, you will got your second error. Edit ScadaCommon.Svc.csproj like:
</Target> --> <ItemGroup> <PackageReference Include="Microsoft.NETFramework.ReferenceAssemblies" Version="1.0.3"> <PrivateAssets>all</PrivateAssets> <IncludeAssets>runtime; build; native; contentfiles; analyzers</IncludeAssets> </PackageReference> </ItemGroup> </Project>
Run dotnet build again, profit!
kumajaya
ParticipantYes, I confirm without https endpoints, UAExpert not list https access anymore but Opc.Ua.Bindings.Https.dll still requested.
To confirm communicator exception, you can watch ScadaComm.log while restart Scada server.
-
This reply was modified 2 years, 10 months ago by
-
AuthorPosts