element-desktop | A glossy Matrix collaboration client for desktop | Chat library

by vector-im TypeScript Version: v1.11.34-rc1 License: Apache-2.0

X-Ray Key Features Code Snippets Community Discussions(1)Vulnerabilities Install Support

kandi X-RAY | element-desktop Summary

element-desktop is a TypeScript library typically used in Messaging, Chat applications. element-desktop has no bugs, it has no vulnerabilities, it has a Permissive License and it has medium support. You can download it from GitHub.

Element Desktop is a Matrix client for desktop platforms with Element Web at its core.

Support

Quality

Security

License

Reuse

Support

element-desktop has a medium active ecosystem.

It has 830 star(s) with 195 fork(s). There are 42 watchers for this library.

It had no major release in the last 12 months.

There are 281 open issues and 60 have been closed. On average issues are closed in 128 days. There are 26 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of element-desktop is v1.11.34-rc1

Quality

element-desktop has 0 bugs and 0 code smells.

Security

element-desktop has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

element-desktop code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

element-desktop is licensed under the Apache-2.0 License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

element-desktop releases are available to install and integrate.

Installation instructions, examples and code snippets are available.

Top functions reviewed by kandi - BETA

kandi has reviewed element-desktop and discovered the below as its top functions. This is intended to give you an instant insight into element-desktop implemented functionality, and help decide if they suit your requirements.

Gets the latest development build for the project .
Computes the signTool tool .
Generate a language file
Convert mapping to counter partials .
Watch a language file .
set package . json version
Download a file to a remote URL
Verify that a file exists
Get version of Webapp app .
Main entry point .

Get all kandi verified functions for this library.

element-desktop Key Features

No Key Features are available at this moment for element-desktop.

element-desktop Examples and Code Snippets

No Code Snippets are available at this moment for element-desktop.

Community Discussions

Trending Discussions on element-desktop

MSIX: How to achieve automatic install of .net 5 required for my application?

QUESTION

MSIX: How to achieve automatic install of .net 5 required for my application?

Asked 2021-May-26 at 10:06

I wrote a WPF program using .NET 5, packed it into the MSIX bundle (Release, x86 and x64) as a framework-dependent package. Everything seems fine, but there is one very annoying thing: on the first run the app says ".NET runtime is missing, would you like to install it?”. If you click yes, the download page opens, where the user has to select the needed runtime, download, and install it. Not the best user experience, I'm thinking about how to improve it.

Is there an option to add .net 5 runtimes (x86 or x64 depending on the user system, or maybe both) as a dependency so it installed automatically?

I know I can define dependencies, but how can I find the right name for the needed dependency?

Also, I know it's possible to define custom install action but I haven't tried it yet, because I want to find a simpler solution. Looks like for that option I'll have to create a small app or script that will check if the needed runtime exists and if not - check the platform and ask the user to install the specific version of the runtime. Not the best user experience too.

Of course, I still have an option to go with self-contained, but I don't want to distribute so many megabytes of .net every time, especially given the fact that I expect frequent updates.

...

ANSWER

Answered 2021-May-26 at 10:06

Luckily, I got an answer on techcommunity.microsoft.com

Thanks to Matteo Pagani:

if it's an application based on .NET Core / .NET 5 (as I seem to understand from the description), the suggested and best way to distribuite via MSIX is to use the self-deployment approach. Thanks to MSIX features like differential updates and single disk instance, you don't have to worry too much about the increased size, since the runtime will be downloaded only at the first install.

Dependencies are not a good fit because there are no packages for .net 5 yet.

Custom install actions are possible but more complicated, so I decided to go with self-contained.

Source https://stackoverflow.com/questions/67638459

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install element-desktop

TODO: List native pre-requisites. Optionally, [build the native modules](https://github.com/vector-im/element-desktop/blob/develop/docs/native-node-modules.md), which include support for searching in encrypted rooms and secure storage. Skipping this step is fine, you just won’t have those features. This will do a couple of things: * Run the setversion script to set the local package version to match whatever version of Element you installed above. * Run electron-builder to build a package. The package built will match the operating system you’re running the build process on.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: