profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/GregorBiswanger/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.
Gregor Biswanger GregorBiswanger cross-platform-blog.com Germany http://about.me/gregor.biswanger Microsoft MVP, Intel Black Belt & Intel Software Innovator - is freelancer as consultant, author, speaker & trainer.

ElectronNET/Electron.NET 5829

:electron: Build cross platform desktop apps with ASP.NET Core (Razor Pages, MVC, Blazor).

GregorBiswanger/json2ts 89

Convert a JSON to TypeScript interfaces.

GregorBiswanger/Brackets-ZoomView 4

ZoomView for Brackets

GregorBiswanger/AspRestApiWorkshop 2

Projektvorlage für meinen ASP.NET Core 3.1 REST-Api Workshop

GregorBiswanger/MyBroker-pwa-workshop 2

The MyBroker Template should be implemented as an Progressive Web App.

GregorBiswanger/AspCoreMyBroker 1

Exercise application for my ASP.NET Core 3.1 training.

GregorBiswanger/AspNetAngularElectronSample 1

ASP.NET Core 5 + Angular 11 + Electron.NET 11.5.1

GregorBiswanger/AspNetCoreGraphQLWorkshop 1

Sample Project for my ASP.NET Core with GraphQL Workshop 🎯

GregorBiswanger/AspSwaggerWorkshop 1

Projektvorlage für meinen ASP.NET Core 5 Swagger/OpenAPI Workshop

GregorBiswanger/BEM-SASS-Workshop 1

Übungen für meinen BEM & SASS Workshop

startedDevExpress/angular-testcafe

started time in 4 days

issue openedDevExpress/angular-testcafe

No Angular Server is started with ng e2e

ng e2e gives me the following warning message at Angular in version 12.1.2: "TestcafeBuilderOptions" schema is using the keyword "id" which its support is deprecated. Use "$id" for schema ID.

No Angular Server is started. You have to start ng serve separately. No advantage currently visible with this library.

An Angular Schematic for this library would be really very helpful.

created time in 4 days

issue commentElectronNET/Electron.NET

How to use Auto updater ?

@sachinmakhre Please refer to the instructions on the Internet for electron builder - Auto Update. This can be used 1:1 with Electron.NET.

giorgosavramopoulos

comment created time in 9 days

issue closeddapr/dapr

Kubernetes (AKS) - Azure Key Vault Secret Store: failed to get oauth token from certificate auth: failed to read the certificate file

Hey Community, I have problems using my certificate in Kubernetes (AKS) for my Azure Key Vault Secret Store.

It works wonderfully with local hosting. I made the configuration according to the instructions and also added the certificate file to the Kubernetes Store. But unfortunately I get the following error message with Kubernetes when starting the dapr sidecar:

time="2021-07-14T14:31:57.756966579Z" level=warning msg="failed to init state store secretstores.azure.keyvault/v1 named azurekeyvault: failed to get oauth token from certificate auth: failed to read the certificate file (0\x82\nP\x0...a\xd0: invalid argument" app_id=mywebapp instance=mywebapp-5557c78c9b-v86ss scope=dapr.runtime type=log ver=1.2.2 time="2021-07-14T14:31:57.757159681Z" level=fatal msg="process component azurekeyvault error: failed to get oauth token from certificate auth: failed to read the certificate file (0\x82\nP\x02\x\xde: invalid argument" app_id=mywebapp instance=mywebapp-5557c78c9b-v86ss scope=dapr.runtime type=log ver=1.2

i have done all the steps according to this documentation: https://docs.dapr.io/reference/components-reference/supported-secret-stores/azure-keyvault/

My Kubectl command: kubectl create secret generic k8s-secret-store --from-file=myapp-certificate=myapp-secrets-myapp-certificate-20210713.pfx

My azurekeyvault.yaml

apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
  name: azurekeyvault
  namespace: default
spec:
  type: secretstores.azure.keyvault
  version: v1
  metadata:
    - name: vaultName
      value: myapp-secrets
    - name: spnTenantId
      value: "460d88b8-d055-4149-9f03-XXX" #changed to XXX only on this post
    - name: spnClientId
      value: "dd964473-808e-4a82-a167-XXX" #changed to XXX only on this post
    - name: spnCertificateFile
      secretKeyRef:
        name: k8s-secret-store
        key: myapp-certificate
auth:
    secretStore: kubernetes

closed time in 10 days

GregorBiswanger

issue commentdapr/dapr

Kubernetes (AKS) - Azure Key Vault Secret Store: failed to get oauth token from certificate auth: failed to read the certificate file

It was my fault. I used spnCertificateFile and that is for local. I changed it to spnCertificate and now it works.

GregorBiswanger

comment created time in 10 days

issue openeddapr/dapr

Kubernetes (AKS) - Azure Key Vault Secret Store: failed to get oauth token from certificate auth: failed to read the certificate file

Hey Community, I have problems using my certificate in Kubernetes (AKS) for my Azure Key Vault Secret Store.

It works wonderfully with local hosting. I made the configuration according to the instructions and also added the certificate file to the Kubernetes Store. But unfortunately I get the following error message with Kubernetes when starting the dapr sidecar:

time="2021-07-14T14:31:57.756966579Z" level=warning msg="failed to init state store secretstores.azure.keyvault/v1 named azurekeyvault: failed to get oauth token from certificate auth: failed to read the certificate file (0\x82\nP\x0...a\xd0: invalid argument" app_id=mywebapp instance=mywebapp-5557c78c9b-v86ss scope=dapr.runtime type=log ver=1.2.2 time="2021-07-14T14:31:57.757159681Z" level=fatal msg="process component azurekeyvault error: failed to get oauth token from certificate auth: failed to read the certificate file (0\x82\nP\x02\x\xde: invalid argument" app_id=mywebapp instance=mywebapp-5557c78c9b-v86ss scope=dapr.runtime type=log ver=1.2

i have done all the steps according to this documentation: https://docs.dapr.io/reference/components-reference/supported-secret-stores/azure-keyvault/

My Kubectl command: kubectl create secret generic k8s-secret-store --from-file=myapp-certificate=myapp-secrets-myapp-certificate-20210713.pfx

My azurekeyvault.yaml

apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
  name: azurekeyvault
  namespace: default
spec:
  type: secretstores.azure.keyvault
  version: v1
  metadata:
    - name: vaultName
      value: myapp-secrets
    - name: spnTenantId
      value: "460d88b8-d055-4149-9f03-XXX" #changed to XXX only on this post
    - name: spnClientId
      value: "dd964473-808e-4a82-a167-XXX" #changed to XXX only on this post
    - name: spnCertificateFile
      secretKeyRef:
        name: k8s-secret-store
        key: myapp-certificate
auth:
    secretStore: kubernetes

created time in 11 days

starteddoghappy/socket.io-client-csharp

started time in 12 days

issue openeddapr/dapr

Azure Cosmos DB with MongoDB API as a state store - error initializing state store

Hello everyone,

I have a problem using Azure Cosmos DB with MongoDB API as a state store. I only get the following error message when starting Dapr:

time="2021-07-09T15:42:45.5258797+02:00" level=warning msg="error initializing state store statestore (state.azure.cosmosdb/v1): , " app_id=servicea instance=SurfaceBook2 scope=dapr.runtime type=log ver=1.2.2
time="2021-07-09T15:42:45.5270009+02:00" level=fatal msg="process component statestore error: , " app_id=servicea instance=SurfaceBook2 scope=dapr.runtime type=log ver=1.2.2
The daprd process exited with error code: exit status 1

I have tried Azure Cosmos DB with SQL and it only worked when I created a database and a container manually (normally this should also be created by itself with NoSQL).

I tried the same with the Azure Cosmos DB with MongoDB API. Despite the database and collection, I get the same error message as posted above.

My Azure Cosmos DB state store configuration: image

created time in 16 days

issue commentElectronNET/Electron.NET

Uncaught Exception: A Javascript error occurred in the main process in (version 11.5.1)

And please use the latest version of Electron.NET + Electron.NET CLI! (Version 13.5.1)

rambabu-paluru-tfs

comment created time in 17 days

issue commentElectronNET/Electron.NET

Uncaught Exception: A Javascript error occurred in the main process in (version 11.5.1)

Please manually remove the host folder from the Obj directory. Then the problem should be fixed.

rambabu-paluru-tfs

comment created time in 17 days

issue commentElectronNET/Electron.NET

Version flag not persisting with the referenced executable

yes you can run down the adrenaline now... 😂😂😂🥳

Thank you for your support!

tub5

comment created time in 23 days

push eventElectronNET/Electron.NET

tub5

commit sha 0af664b8a6fa1290e11c9ea26af8fa6c59ff4070

If we provide the Version parameter and haven't included the version or product version dotnet flag then add them. Fixes: #584

view details

Gregor Biswanger

commit sha 186209486130f63c0e267c912d2e7f08ba7ab0d9

Merge pull request #585 from tub5/bug/584 If we provide the Version parameter and haven't included the version …

view details

push time in 23 days

PR merged ElectronNET/Electron.NET

If we provide the Version parameter and haven't included the version …

If we provide the Version parameter and haven't included the version or product version dotnet flag then add them.

Fixes: #584

+8 -0

0 comment

1 changed file

tub5

pr closed time in 23 days

issue closedElectronNET/Electron.NET

Version flag not persisting with the referenced executable

<!-- Please search existing issues to avoid creating duplicates. --> When using the new Version flag, this is not being persisted to the dotnet command (I'm not sure why this wasn't in the PR). You can bypass this by using electronize build /target win /Version 2.0.13 /p:Version=2.0.13 /p:ProductVersion=2.0.13 however, this should not have to be the case.

<!-- Which version of Electron.NET CLI and API are you using? --> <!-- Please always try to use latest version before report. -->

  • Version: 13.5.1

<!-- Which version of .NET Core and Node.js are you using (if applicable)? -->

<!-- What target are you building for? -->

  • Target: Windows

<!-- Enter your issue details below this comment. --> <!-- If you want, you can donate to increase issue priority (https://donorbox.org/electron-net) -->

Steps to Reproduce:

  1. use the /Version flag when building the electronize build command

closed time in 23 days

tub5

push eventElectronNET/Electron.NET

Gregor Biswanger

commit sha 0ad89c7d220ab6c96be22ba1b5122aa76f72c247

RequestSingleInstanceLockAsync callback does work now - bug fix #519

view details

push time in 23 days

issue closedElectronNET/Electron.NET

RequestSingleInstanceLockAsync callback does not seem to work

<!-- Please search existing issues to avoid creating duplicates. -->

<!-- Which version of Electron.NET CLI and API are you using? --> <!-- Please always try to use latest version before report. -->

  • Version: 9.31.2

<!-- Which version of .NET Core and Node.js are you using (if applicable)? -->

<!-- What target are you building for? -->

  • Target: Windows 10

<!-- Enter your issue details below this comment. --> <!-- If you want, you can donate to increase issue priority (https://donorbox.org/electron-net) --> I cannot get the RequestSingleInstanceLockAsync callback to work at all. I have tried several things and it just does not seem to get called.

I have set up a test to see if its firing. Basically, if a second instance is launched, I just want it to kill the first instance. It does not kill the app. In my actual app, I want it to restore the window if necessary and focus the window; that wouldn't work either. It seems the callback just isn't being called at all.

The lock is working, it won't launch the second instance. (Although it does launch the splash screen which is not very nice).

// This method gets called by the runtime. Use this method to configure the HTTP request pipeline.
public void Configure(IApplicationBuilder app, IWebHostEnvironment env)
{
    if (env.IsDevelopment())
    {
        app.UseDeveloperExceptionPage();
    }
    else
    {
        app.UseExceptionHandler("/Error");
        // The default HSTS value is 30 days. You may want to change this for production scenarios, see https://aka.ms/aspnetcore-hsts.
        app.UseHsts();
    }

    app.UseRequestLocalization(localizationOptions);

    app.UseHttpsRedirection();
    app.UseStaticFiles();

    app.UseRouting();

    app.UseEndpoints(endpoints =>
    {
        endpoints.MapBlazorHub();
        endpoints.MapFallbackToPage("/_Host");
    });

    if (HybridSupport.IsElectronActive)
    {
        var task = Electron.App.RequestSingleInstanceLockAsync(MyCallback);
        var hasLock = task.GetAwaiter().GetResult();
        if (!hasLock)
        {
            Electron.App.Exit();
            return;
        }
        // Normal browser window setup, etc.
    }
}

public void MyCallback(string[] args, string directory)
{
    Electron.App.Exit(); // !!! This is never executed.
}
        

Any idea what is going on here? Or am I using this incorrectly?

closed time in 23 days

Delpire

issue commentElectronNET/Electron.NET

RequestSingleInstanceLockAsync callback does not seem to work

Hi @matanelrb the support of handle command line arguments in singleInstance is implemented for the next Electron.NET 13.5.1 release.

see https://github.com/ElectronNET/Electron.NET/issues/520

Delpire

comment created time in 23 days

issue commentElectronNET/Electron.NET

Version flag not persisting with the referenced executable

Would you like to quickly submit a pull request? :)

Then it should still be fixed for the 13.5.1 release.

tub5

comment created time in 23 days

issue commentElectronNET/Electron.NET

singleInstance Electron Manifest setting should handle command line arguments

Hi @Delpire, this feature is implemented for the next Electron.NET 13.5.1 release.

If the second instance is opened with arguments, the main application that has landed receives a focus. If you subscribe to this event, you can also request your new arguments.

As example:

Task.Run(async () =>
{
    var mainWindow = await Electron.WindowManager.CreateWindowAsync();
    mainWindow.OnFocus += async () =>
    {
        if(await Electron.App.CommandLine.HasSwitchAsync("message"))
        {
            var message = await Electron.App.CommandLine.GetSwitchValueAsync("message");
            await Electron.Dialog.ShowMessageBoxAsync(message);
        }
    };
});
Delpire

comment created time in 23 days

issue closedElectronNET/Electron.NET

singleInstance Electron Manifest setting should handle command line arguments

Currently there are two ways of enforcing an app to be single instance.

  1. Set "singleInstance": true in the electron manifest json
  2. Write code in .NET to request the single instance lock and handle the second instance accordingly.

The first option seems to be the most reliable and robust. It works the fastest since it is being done in the javascript before the ASP .NET Core application launches (at least that is my understanding). However, one major problem is that you cannot handle the command line arguments to this second instance.

The alternative to this, is to set this to false and write the code to handle it ourselves, but this has several problems. Firstly, I can't get the callback to work, see #519 . Secondly, the second instance will always launch the splash screen, which is undesired if I have an instance running (and not a problem using the singleInstance in the manifest).

I really think both problems should be fixed, but I would be happy with one of the following two solutions. Solution 1: Allow the javascript to take arguments and pass them to .NET. Then we can just check for the lock and handle the arguments. Solution 2: Provide a new setting to the electron.manifest.json that will cause main.js to first check if it has the lock, and if it does not have the lock, don't display the Splashscreen, but continue to call the ASP .NET Core stuff so that we can handle the arguments.

I believe the only work around (assuming I can get the callback working or that gets fixed), is to handle showing the splash screen myself. That concerns me because I believe the app will seem more responsive at launch when the javascript launches the splash screen. My app seems to take a long time to load, and I am concerned that the splash screen will take a long time to show up if I write that code myself in .NET

closed time in 23 days

Delpire

push eventElectronNET/Electron.NET

Gregor Biswanger

commit sha afcd113675c36282db8855788cd6901009236258

singleInstance handle command line arguments

view details

push time in 23 days

issue commentElectronNET/Electron.NET

Socket Disconnection Error

The talk here is of SocketIoClientDotNet

AykutToprak

comment created time in 23 days

issue commentElectronNET/Electron.NET

Socket Disconnection Error

We are currently also using a .NET library to be able to communicate with Nodejs Socket.io, which has long been deprecated.

We need a new one that will continue to be maintained and will also work with the current Socket.io version. Can someone help us? We are also happy to do this together.

AykutToprak

comment created time in 23 days

issue commentElectronNET/Electron.NET

Socket Disconnection Error

I can hardly reproduce it. We need support.

Here is a video of how you can install the missing features yourself and submit them as a pull request: https://youtu.be/Po-saU_Z6Ws

Please also test it with you.

AykutToprak

comment created time in 23 days

issue commentElectronNET/Electron.NET

Prevent downloads

We need support - I can't add new features as quickly as possible on my own. Here is a video of how you can install the missing features yourself and submit them as a pull request: https://youtu.be/Po-saU_Z6Ws

Please also test it with you.

Elimil

comment created time in 23 days

push eventElectronNET/Electron.NET

Gregor Biswanger

commit sha 0e22ee3fd3742b5906f822ffa1fb602239d57c22

Changed CLI help text

view details

push time in 23 days

issue commentElectronNET/Electron.NET

electronize start /target custom not working

And for the start command you only had one typo.

This command does what you want: electronize start /target custom "win7-x86;win32"

Bmooij

comment created time in 23 days

issue commentElectronNET/Electron.NET

electronize start /target custom not working

You also need the electron-arch parameter for the processor architecture.

This command does what you want: electronize build /target custom "win7-x86;win" /electron-arch ia32

Bmooij

comment created time in 23 days

issue closedElectronNET/Electron.NET

electronize start /target custom not working

  • Version: 9.31.2
  • .NET Core: 3.1
  • Node.js: v12.13.0
  • Target: x68

With the command electronize start /target custom "win7-x68;win32", it always publish with x64: dotnet publish -r win-x64

closed time in 23 days

Bmooij

push eventElectronNET/Electron.NET

Gregor Biswanger

commit sha ce0cdf39c62b92264cd8ebf53c867c20b08a4823

Update to native Electron 13.1.5, Update Changelog

view details

push time in 23 days