Activities of "pliaspzero"

so order for build:

yarn npm run create-dynamic-bundles npm run publish

Thanks for that - now one step forward. But still I need to reload - any further idea?

DEBUG: scripts.c7f035c4f2b95935.js:1 Starting connection using WebSockets transport scripts.c7f035c4f2b95935.js:1 DEBUG: scripts.c7f035c4f2b95935.js:1 Starting connection using WebSockets transport scripts.c7f035c4f2b95935.js:1 [2024-11-19T12:37:44.397Z] Information: WebSocket connected to wss://myURL/signalr?id=3KFUWjao_Q7rNmiSHUB_iA. scripts.c7f035c4f2b95935.js:1 DEBUG: scripts.c7f035c4f2b95935.js:1 Connected to SignalR server! scripts.c7f035c4f2b95935.js:1 DEBUG: scripts.c7f035c4f2b95935.js:1 Registered to the SignalR server! scripts.c7f035c4f2b95935.js:1 [2024-11-19T12:37:44.550Z] Information: WebSocket connected to wss://myURL/signalr-chat?id=hAmuvL5relNB_lA0fuU5Cg.

"scripts": {

"ng": "ng",

"publish": "gulp build && ng build --configuration production",

"lint": "eslint -c .eslintrc.js --ext .ts src",

"post-publish": "shx mv ./wwwroot/dist/* ./wwwroot/",

"publish-k8s": "gulp build && ng build --configuration k8s --verbose",

"start": "ng serve --host 0.0.0.0 --port 4200",

"hmr": "gulp buildDev && ng serve --host 0.0.0.0 --port 4200 --hmr",

"test": "gulp buildDev && ng test",

"create-dynamic-bundles": "gulp buildDev",

"nswag": "cd nswag/ && refresh.bat"

},

Hi,

we use ASPNET Core - API - Backend CSS V13.4 without any changes - when abp-href is used - CSS is not working - when we just use href - CSS style is used and working.

See also image below. What is the abp-href for / what could be reason for that / how to solve.

any idea?

We did that - but still not working;

Hi, we did that - but still same problem:

Hi, no - we host in Azure - Web App Services.. and did this enhancement var redisConnectionString = _appConfiguration["Abp:RedisCache:ConnectionString"]; var redisDatabaseId = _appConfiguration.GetValue<int>("Abp:RedisCache:DatabaseId");

    if (!string.Equals(redisConnectionString, "localhost", StringComparison.OrdinalIgnoreCase))...

maybe this helps - I get this in Angualr app F12 in browser: DEBUG: scripts.c7f035c4f2b95935.js:1 Cannot start the connection using WebSockets transport. Unable to connect to the server with any of the available transports. ServerSentEvents failed: Error: 'ServerSentEvents' is disabled by the client. LongPolling failed: Error: 'LongPolling' is disabled by the client. scripts.c7f035c4f2b95935.js:1 DEBUG: scripts.c7f035c4f2b95935.js:1 Starting connection using ServerSentEvents transport polyfills.ce1ab5650c81c793.js:1 N: Unable to connect to the server with any of the available transports. ServerSentEvents failed: Error: 'ServerSentEvents' is disabled by the client. LongPolling failed: Error: 'LongPolling' is disabled by the client.

maybe it is a timezone issue?

We are currently using ASPZero with Redis configured as the SignalR backplane for our application. However, we are encountering an issue where Redis messages (published through SignalR) are not being immediately received by connected clients. Messages only appear after the page is reloaded, which suggests a potential issue with Redis and/or SignalR configuration.

Our application is deployed on Azure, and the site's timezone is set to W. Europe Standard Time. We suspect that this may be causing an issue with how SignalR and Redis interact, particularly in terms of time synchronization. We understand that Redis uses UTC for timestamps, and we believe there might be a mismatch with the timezone settings that could be affecting message delivery. Here's a summary of our setup and the issue:

Redis Connection String: Configured correctly with the Azure Redis Cache endpoint.
SignalR Configuration: We are using the Redis backplane with the AddStackExchangeRedis method.
Timezone: The site's timezone is set to W. Europe Standard Time.
Problem: Messages published to Redis (e.g., PUBLISH WFMOne.Web.Chat.SignalR.ChatHub:all "Hello from Redis!") are only visible to clients after they reload the page. We suspect this could be related to time handling, either in Redis or SignalR, or potentially the timezone mismatch.

Our steps taken:

We have confirmed that Redis is correctly receiving and publishing messages.
We checked that the connection and channel subscriptions work, but messages only appear after reloading the page.
We also ensured that the Redis time stamps are in UTC as expected, but we're unsure how this aligns with our local timezone (W. Europe Standard Time) and whether this is causing a delay or missed messages.

Could you please assist us in confirming if there is an issue with the timezone settings or Redis/SignalR configuration that could be causing this delay in message delivery? We would appreciate any guidance on how to properly handle timezones between SignalR and Redis in our setup.

Thank you in advance for your support.