microsoftedge / edge-launcher Goto Github PK

There's a fantastic application that creates Chrome-based SSBs for macOS called Epichrome. Frankly neither I nor anyone on our team could now live without Epichrome Chrome instances as it greatly reduces the complexity of managing our projects and keeping browsing instances and history managed very cleanly... as well as keeping cookies sanitized and stopping cross platform contamination. It's really great.

I think this is a prime opportunity for you to fork and support an open source project that would really get macOS users (and ultimately Linux) excited and really feel good about the inbound MS Edge release for macOS. I know it would excite us.

One reason that this would be exciting to a lot of folks is that the one thing that really differentiates Microsoft from Google right now is SUPPORT. I hate Google's relationship with users. It simply doesn't exist. There's no reasonable way to talk to Google Chrome devs about problems, features or whatever. The same is really seemingly true with Chromium in that I've had trouble getting any attention whatsoever from the Chromium group, etc.

I think this one fact, that Microsoft has started to facilitate open communications with those who want or need to chat things have a way to do so, really differentiates the Edge potential vs Chrome proper.

There is no license in this project at the moment.
Depending on this: https://help.github.com/articles/open-source-licensing/ it means that this code shall never be used, distributed and so on.
I guess, that it should be Apache 2 License like the rest of MS Edge: https://github.com/MicrosoftEdge/Status/blob/production/LICENSE.md

I've noticed a 1.2 release on this GitHub repo, but npm seems to only have versions 1.0.0 and 1.0.1. If you're interested in automating these releases, check out karma-ie-launcher's Gruntfile, it has some tasks for automating version bumps, GitHub releases, and npm publishes together.

Also, can you please add the published package.json to this repo's source (to make it easier to fork and to allow npm installs of unpublished commits through GitHub)?

My angular js Web application is working fine in dev environ ment as expected once its deployed to higher environment . While running/browsing the application in IE Edge the application by default selecting the 8 and my application is not working since ie 8 wont support angular js.

So tried changing the meta tag to override the compatable view setting in my code as follows

Trial `1)
**

Here in place of conent i tried with all possible options like
IE=edge","IE=11","IE=EmulateIE11","IE=10","IE=EmulateIE10","IE=9","IE=EmulateIE9

Trial 2)

<system.webServer>
     <httpProtocol>
        <customHeaders>
           <add name="X-UA-Compatible" value="IE=edge" />
        </customHeaders>
     </httpProtocol>
  </system.webServer>

I tried in all possible ways but while browsing the application by default it is selecting the ie mode 8 and application not working.

Note:
Before upgrading to i.e from 10 to IeEdge the application was up and running correctly with out any override compatability code
My hosted environment has compatiable view settings by default so am trying to override default setting by above trials but no luck.
In Fiddler Http response header i can see the X-UA-Compatible edge and in view source i can see the

Any suggestions or any issue with Edge or my code ?

FYI
Issue But my application opening in ie8 by default in higher environment ?

According to Command-Line Activation of Universal Windows Apps, the Fall Creators Update is getting improved support for command line invocation of UWP apps. Could there be performance and stability improvements for switching to this system, or is it better to keep edge-launcher's current functionality using the C# APIs?

I find the -k option very useful in automated testing, though it can be inconvenient that it leaves the browser open after the calling process is killed. Would it be possible to change -k's behavior (or add another flag) to close Edge after edge-launcher is closed?

Not sure if I'm missing something... The readme.md mentions a -k parameter that the binary doesn't support.

There's only a single release visible, 1.0.0. The code is currently 1.2.0 (which presumably explains the lack of support for -k).

Also, the 1.0.0 binary doesn't seem to do anything with a 64-bit v79 client (except when it returns the default 'help' when I provide the -k parameter)

So far, the extension, with @jckleinbourg's changes (#5) is near perfect; it would be nicer though to also have the command-line not flash during the transition between the launcher and the browser though.

I haven't looked at the source at all to see how you're launching the process, but I know in .NET you can do so like this, (maybe the same can be done in the Launcher?)

Dim p As New Process()

    With p.StartInfo
        .RedirectStandardOutput = True
        .RedirectStandardError = True
        .FileName = "CMD.EXE"
        .Arguments = "/C bcdedit " & strWhich
        .UseShellExecute = False
        .CreateNoWindow = True
    End With

    p.Start()

It's more of a question rather than an issue. What are the use cases for this tool that cannot be covered by microsoft-edge protocol? For example, you could use the following command instead:
start microsoft-edge://bing.com

I opened .sln file in visual studio express 2015 RC, when I build it there are some errors shown below:

It should set some options in visual studio express, do you give me some suggestions? Thanks

Since the last Microsoft Edge update (25.10586.0.0), using the launcher when Edge is already open launches a new blank Edge window instead of adding new tab with the url to the existing one

We currently have start shell:AppsFolder\Microsoft.MicrosoftEdge_8wekyb3d8bbwe!MicrosoftEdge that will start a new instance of edge and use an start shell:AppsFolder\Microsoft.MicrosoftEdge_8wekyb3d8bbwe!MicrosoftEdge <some url> that will use existing instance of edge if present to open url.

We also have start microsoft-edge: and `start microsoft-edge:<some url>" that always takes one to existing instance of edge if present either and existing instance with new tab pointing at specified url.

With either of the above we can set %lt;some url%gt; = about:InPrivate to get an InPrivate tab but not the <existing edge instance> | ctrl+shift+p experience of a new InPrivate instance of edge with InPrivate tab open. There are hits suggesting the first of the above options can be fed a -private switch to accomplish this but all it does on my current win10 setup is take me to a search page with -private search results.

Any thoughts on whether or not your work here could be updated to focus on providing a command line version for reproducing the <existing edge instance> | ctrl+shift+p experience ?

A problem that I currently have is that I use Edge as an actual browser, and using this utility causes a new tab to pop in existing windows with no way to manage that individual tab. It'd be nice if there was a way to use this tool to create a dedicated window that an automated system (e.g. Karma) could manage without interfering with other Edge windows. Additionally, it'd be cool if we could launch an instance of Edge without the user's profile loaded, so that we could test without any extensions/userscripts interfering with the content under test.

When I start any link or file (e.g. pdf) for the first time, it works perfectly.
But when I run the launcher again while one instance of Edge is open, it opens an empty Edge browser but the link doesn't open in any of the new running instances.

Works great, can you add these 2 small things to it, to perfect it? :)

1). Add the Edge icon as it's icon. That way, programs that extract a program's icon from it's .exe, will use the actual Edge icon as well.

2). If launched without any URL as a param, just launch Edge itself. Currently it just flashes the cmd window, then closes.

It seems as if using the -k flag without a URL causes the launch to open -k as the URL, ignoring the keepalive option.

Reproduction

Run MicrosoftEdgeLauncher.exe -k.

Expected behavior

• A new instance of Edge launches with the usual start page.
• The command waits to complete.

Actual behavior

• Edge opens with a blank window (it seems like a minor UI glitch, it's not the start page).
• The command does not wait to complete.

When providing a URL and the -k flag, in some cases Edge will stay at example.com instead of switching the tab to the given URL. It seems like this could be a network related issue, since one of the users experiencing this was unable to access example.com, though I can access the website and I don't have this issue myself. Please see the comments of nickmccurdy/karma-edge-launcher#27 for more information.

CC @gmisiolek @pchorus @leandro86

The prebuilt Release, ProjectSpartanLauncher.exe, does not work. It seems outdated; for example, it does not contain the Usage statement that is displayed when no arguments are specified. Nor does it perform the basic function. It does not thing at all. The latest code does work, though. Just the prebuilt exe needs updating.

This project is very useful but very difficult to use on Continues Integration (CI) servers, since its npm package is outdated (#20) and it is not available on NuGet.

My use-case is to test SVG.js on AppVeyor using Karma.