nats-by-example icon indicating copy to clipboard operation
nats-by-example copied to clipboard

NBE doesn't work well under Windows.

Open wa1gon opened this issue 1 year ago • 0 comments

Observed behavior

I am very excited about the package, but so far the learning curve is fairly sharp.

darryl@Spock:/mnt/c/github/NBE/nats-by-example/examples$ nbe.exe run messaging/pub-sub/dotnet copy default files: CreateFile .: The system cannot find the path specified. darryl@Spock:/mnt/c/github/NBE/nats-by-example/examples$ nbe.exe run messaging/pub-sub/dotnet dotnet/ dotnet2/ darryl@Spock:/mnt/c/github/NBE/nats-by-example/examples$ nbe.exe run messaging/pub-sub/dotnet2/ Main.cs messaging-pub-sub.csproj output.cast output.txt darryl@Spock:/mnt/c/github/NBE/nats-by-example/examples$ nbe.exe run messaging/pub-sub/dotnet2/ copy default files: CreateFile .: The system cannot find the path specified.

Expected behavior

I haven't found the right commands for NBE to work under Windows.

I found that the web NBE examples were out of date from the GitHub code.

It seems like for DotNet instead of spinning up a docker image, just having a solution would be better. After giving up on NBE CLI I went to making my own solution/project and got the first example to work.

Server and client version

nats --version 0.1.5 nats-server --version nats-server: v2.10.20

Host environment

Windows 11, 64Gig memory

Starting nats-server Version: 2.10.20 Git: [7140387] Name: NATS JetStream Server Node: qitFEUGp ID: NBDVCSKFG4FORG6LAQQZAAS2HGQN5EZP57EJXEGI7P3RCGJ3SLD4SEAZ Using configuration file: C:\nats-sandbox\nets-server.conf Starting http monitor on 0.0.0.0:8222 Starting JetStream

      https://docs.nats.io/jetstream

---------------- JETSTREAM ---------------- Max Memory: 4.00 GB Max Storage: 1.00 TB Store Directory: "c:\nats\jetstream\jetstream"

Listening for client connections on 0.0.0.0:4222 Server is ready

Steps to reproduce

The observed behavior is the steps I used.

wa1gon avatar Oct 01 '24 14:10 wa1gon