Topic: Buid Rapid SCADA 6 on Visual Studio Code | Rapid SCADA Forum

Tagged: vscode

This topic has 42 replies, 3 voices, and was last updated 6 months, 3 weeks ago by Mikhail.

Viewing 13 posts - 31 through 43 (of 43 total)

← 1 2 3

Author

Posts
October 24, 2022 at 10:58 am #11371
zzz
Participant
Problem solved. My bad, missing MqttNet.dll.

Since I use the .pdb and .deps.json file as identifiers to identify the target dll files and copy them out, the support dlls are not moved to my final build output folder.

What is the recommended way to collect all the necessary files into a clean separate folder after build each solution ? Like your distributed package does ?

I think the VSCode setup here works just fine on Debian 10.
Except that the default wine 5.0.3 doesn’t work with SA. Always stack overflow after activating any button or menu that actually start to load the xml file.
```
002d:fixme:msvcrt:MSVCRT__stdio_common_vsnwprintf_s options 24 not handled
002d:trace:loaddll:load_native_dll Loaded L"Z:\\home\\zzz\\repos\\rapidscada6\\scada-v6-master\\ScadaAdmin\\ScadaAdmin\\ScadaAdmin\\bin\\Release\\net6.0-windows\\win-x64\\ScadaWebCommon.Subset.dll" at 0x24cb0000: native
002d:fixme:msvcrt:MSVCRT__stdio_common_vsnwprintf_s options 24 not handled
002d:trace:loaddll:load_native_dll Loaded L"Z:\\home\\zzz\\repos\\rapidscada6\\scada-v6-master\\ScadaAdmin\\ScadaAdmin\\ScadaAdmin\\bin\\Release\\net6.0-windows\\win-x64\\System.Xml.XmlSerializer.dll" at 0x24ce0000: native
002d:fixme:msvcrt:MSVCRT__stdio_common_vsnwprintf_s options 24 not handled
002d:fixme:msvcrt:MSVCRT__stdio_common_vsnwprintf_s options 24 not handled
002d:fixme:msvcrt:MSVCRT__stdio_common_vsnwprintf_s options 24 not handled
002d:err:seh:setup_exception stack overflow 1584 bytes in thread 002d eip 000000007bcd61d3 esp 0000000000130fe0 stack 0x130000-0x131000-0x2b0000
0035:fixme:console:CONSOLE_DefaultHandler Terminating process 2c on event 0
```
I have other design software using wine 5.0.3. So maybe I just leave it that way and use VM instead.
October 25, 2022 at 7:49 am #11407

Mikhail
Moderator

What is the recommended way to collect all the necessary files into a clean separate folder after build each solution ? Like your distributed package does ?

I created a custom application to collect the files into the package. Not ready to share it. The task also can be solved by writing scripts.

October 26, 2022 at 6:22 am #11420

kumajaya
Participant

Yeah, I created a dumb script to pack Administrator app based on beta rilis file list but somehow my own build searching for dependency library in the current directory, different than official release from the root of Administrator app.

I even build SCADA 5 on VS Code but still need Visual Studio msbuild tools installed, so still Windows only.

October 26, 2022 at 11:01 am #11424

Mikhail
Moderator

somehow my own build searching for dependency library in the current directory, different than official release from the root of Administrator app

What particular files, for example?

October 27, 2022 at 3:14 am #11438
zzz
Participant
Yeah, I wrote a script for that. But I noticed that some files are missing from the build output. e.g.
```
web.confg
...
```
some output are not shown in released file
```
ScadaCommonApp
ScadaCommon
ScadaServerApp
ScadaServer
...
AgentClient.dll
```
etc.
```
ScadaCommon.dll
ScadaCommon.Log.dll
*Storage.dll
```
are copied multiple times, I tried put them in one ScadaCommon folder, and add --additionalprobingpath $SCADA_COMMON after dotnet in ExecStart line, this switch works for dotnet dlls, but not all dlls e.g. MQTTNet.dll

If the dependencies are in a central place, with some additionalprobingpath logic in code, maybe packaging could be a lot easier.
October 27, 2022 at 12:03 pm #11442

Mikhail
Moderator

For the ScadaWeb project try publishing to a folder.

November 4, 2022 at 8:02 am #11495

zzz
Participant

I am not a dotnet guy, this core thing is especially new to me. Is there any way to debug current app in VSCode. I mean like set a breakpoint, inspecting some variables etc ?

The API tooltip and Go To Definition command sometimes works, sometimes not, which is really annoying. I have to switch solution back and forth (the pull up menu on button bar) and wait for OminiSharp to finish, only after that the intellisensce seems to again become aware of the classes, methods etc.
Do you guys have this kind of glitches ? Could i5-5300+8G (disk:ssd) to be slow for this type of development?

November 4, 2022 at 8:41 am #11496

Mikhail
Moderator

Is there any way to debug current app in VSCode.

As I read, yes. But I haven’t tried debugging in VS Code by myself, because I use Visual Studio. VS Community Edition is free.

Could i5-5300+8G (disk:ssd) to be slow for this type of development?

The computer is good enough.

November 7, 2022 at 6:03 am #11499

zzz
Participant

Nah, until I replace the 500G with 1T or 2T, VS Studio is not my option.
PS I already have it in Win10 VM, a VM that I have always wanted to get rid of.
Win10 VM is a hack of painful experience, sometimes it doesn’t start, sometimes it doesn’t shutdown, always Please wait updating… Don’t shutdown. When its up, it occasionally become the bandwidth hog even when I am on a metered slow link. The built-in virus scanner sometime kicks in when I am compiling sth. and nothing can stop it. Thus I got to occasionally pause the VM.

November 7, 2022 at 7:37 am #11500

Mikhail
Moderator

When you get experience debugging in VS Code, please share with us.

November 16, 2022 at 1:45 pm #11555

kumajaya
Participant

https://github.com/RapidScada/scada-v6/pull/16/commits/6d6d28c5561bf9b56eac7dec7f658af845ab2581 contain launch.json for debugging ScadaAgent.

November 16, 2022 at 3:23 pm #11559

zzz
Participant

I found this VSCode Remote Debugging Guide interesting. The Linux boxes I manage are headless, remote debugging will make troubleshooting a lot easier, I think it will give it a try.

November 17, 2022 at 2:09 pm #11567

Mikhail
Moderator

Thanks to kumajaya and zzz
Author

Posts