Electron JS app icon not showing on Windows Store - electron

I am trying to publish my electron app to Windows store but it is showing default electron icon whereas the exe created has correct icon. Even on launching the Appx file, correct icon is showing up. How can I change the default icon of electron and put the correct icon on store?
Package JSON:
"build": {
"appId": "xxxx.xxxx.xxxx",
"directories": {
"buildResources": "build"
},
"win": {
"icon": "assets/icons/win/icon.ico",
"target": [
"Appx",
"nsis"
]
},
"nsis": {
"artifactName": "${productName}_Setup_${version}.${ext}",
"installerIcon": "assets/icons/win/icon.ico"
}

Add a folder as a sub folder under build. build->appx(must be appx)
Then add some icons named as Square44x44Logo.png, Square150x150Logo.png, StoreLogo.png, Wide310x150Logo.png
I believe you can get the image resolution from the name. for StoreLogo.png 256*256 will be fine.

As tpikachu pointed out, you haven't correctly defined the graphical assets form your package. Doing this manually is quite tedious and error-prone.
Tools like Advanced Installer Express (free forever) handle such configurations automatically. Here is an article about how to package an MSIX for an Electron app with Advanced Installer, and another one about how to publish your app in the MS store:
p.s. I work on the team building Advanced Installer

Related

How to include a gigantic 14GB+ folder in the NSIS installer of an Electron app?

I have an app made using Electron. I am creating the NSIS installer for the app using Electron Builder. The Electron app has a dependency to something similar to a videogame (lets call it a videogame but it's not a videogame) that is 14GB+ folder and contains large binaries (.dlls, .exes, etc.).
I need to create the NSIS installer for my app so the user installing the app gets both the app and the videogame dependency completely offline, without internet.
I am aware the NSIS installer cannot be larger than 2GB.
A solution I am thinking of:
Create a install.zip that contains NSIS installer and videogame.zip.
In the .nsh script, extract the videogame.zip via relative path to wherever I need the contents
I wasn't able to solve this problem. I just used an alternative: I used a .zip file instead of NSIS.
I included both the dependency and the Electron app together.

Importing test cases into TFS

I would like to move my test cases from an older system into the TFS system. I discovered the "Test Case Migrator Plus" tool, however after downloading & extracting zip file, I cannot find the TestCaseMigratorPlus.exe file. Project info can be found at: https://archive.codeplex.com/?p=tcmimport
Does anyone have suggestions on getting the the .exe file so I can begin the migration process? Are there other tools available to do this task? My test case data is in both cvs & xls format.
Looks like the archive zip file contains all the releases. But they're named a bit weird. Looking at the releases manifest you should be able to just rename this file releases\0\427b6077-824e-48ef-8eed-8111cc2f7fbc to TestCaseMigratorPlus(Excel-MHT) V1.1 RTM Binaries.zip:
{
"Id": "427b6077-824e-48ef-8eed-8111cc2f7fbc",
"FileName": "TestCaseMigratorPlus(Excel-MHT) V1.1 RTM Binaries.zip",
"Url": "./0/427b6077-824e-48ef-8eed-8111cc2f7fbc",
"Type": "Application",
"UploadDate": "2012-01-02T00:15:57.42-08:00"
},

Using Visual Studio Code with non-Core Asp.Net MVC

How I do to work with non-Core Asp.Net MVC projects on Visual Studio Code?
I'm tired of slowness of Visual Studio Community, so I was thinking about if I can setup an VS Code environment for that.
Here is how I was able to do it for my projects:
Install Visual Studio Code (obviously)
Install C# plug-in (I hope you are using C#) - main benefit here is intellisense, syntax highlighting, some refactoring options
Make sure you have msbuild in your environment path for building solutions
Now the basic flow looks like this:
Open Visual Studio Code
Choose File -> Open Folder... menu option and open the folder that contains your asp.net mvc solution
CTRL+SHIFT+P to run VS code command and find "OmniSharp: Select Project"
Choose your solution
Wait for OmniSharp to load (you can inspect its output by bringing up output view CTRL+j, select Output, 'OmniSharp Logs')
At this point you should be able to Go to any type with CTRL+T and typing the type name. Use CTRL+P to find files and edit them. And to build press CTRL+SHIFT+B. If you don't have vscode task configured for building, I believe VS Code will build a scaffold file for you which you need to fill out and then msbuild can be invoked to build your solution. Check mine out (put this in .vscode directory, in a file called tasks.json):
{
// See https://go.microsoft.com/fwlink/?LinkId=733558
// for the documentation about the tasks.json format
"version": "0.1.0",
"command": "msbuild",
"args": [
// Ask msbuild to generate full paths for file names.
"/property:GenerateFullPaths=true",
// "/p:Configuration=Release",
"YOUR SOLUTION FILENAME.sln"
],
"taskSelector": "/t:",
"showOutput": "silent",
"tasks": [
{
"taskName": "build",
// Show the output window only if unrecognized errors occur.
"showOutput": "silent",
// Use the standard MS compiler pattern to detect errors, warnings and infos
"problemMatcher": "$msCompile"
}
]
}
It will take some time to get used to but once you are there, it's awesome. No more VS.NET memory hogging and overall slowness.
I love it how fast the editor starts and closes. Just get used to the flow of open folder, CTRL+T or CTRL+P for navigating between classes/code files. And be patient with OmniSharp (C# plugin) as at times it becomes nonresponsive and syntax highlighting becomes unavailable. At that point, I just restart OmniSharp (via a CTRL+SHFT+P, find OmniSharp, restart option).
Biggest things I miss: debugging. VS Code with C# plugin only supports .NET Core debugging as far as I know. The way I get around this is usually having unit tests and then isolating the code I want to debug via a unit test and just iterate on the test until the problem is solved. In rare cases where I absolutely need a debugger, I just power up the good ol' Visual Studio beast, do debugging and get out.
Hope this helps!
I've successfully setup my Visual Studio 2015+ ASP.NET project on VSCode.
I've created an gulpfile that handle the build for me:
It starts an IISExpress instance.
Refresh my browser on razor code change.
And automatically rebuild my application when I change C# code.
You can find the gulpfile on my project's Github

Multi-Device Hybrid Apps for Visual Studio: ripple emulator doesn't start

I have the same problem like Fabio in this post. Unfortunately I can't add answer. I know that problem can be connected with white space in my user name. Can I change path from "c:\users\forename surname...", to "c:\users\forenamesurname..." ?
To change your username, I suggest creating a new user with the desired name. As far as dependencies are concerned, in case you used the Multi-Device Hybrid Apps installer for all your dependencies, here are the changes to be made:
Create a new user and login
Go to Control Panel -> Programs and Features
Uninstall Android SDK
Download the Android SDK again from here.
Install it choosing "Install for all users on this machine"
Install the following packages in the Android SDK manager:
Open your system Environment Settings:
Change the ADT_HOME to: "C:\Program Files (x86)\Android\android-sdk" (or if you chose a custom install directory)
Everything should run as expected now.
Yes, renaming your profile folder should work. Be sure to update any environment variables and paths accordingly.

With FDT, How Do I Prevent Packaging For Mobile Applications (iOS & Android)

When working with the FDT FREE version, how do I run a configuration which only compiles the SWF and doesn't package an .IPA or .APK.
Is there any way of do this?
For example, I would like to have 2 launch methods, one that only compiles the swf and after it processes some ant script to update resources, and another that final compiles and packages the app.
Set the launcher platform to 'Adobe AIR Desktop' and choose 'Do not launch'. You may need to set the project type to 'AIR All' in order to achieve this. This will work for most scenarios.

Resources