Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Windows installer install both 32-bit and 64-bit in the same location #14895

Closed
sgjesse opened this issue Nov 7, 2013 · 4 comments
Closed

Windows installer install both 32-bit and 64-bit in the same location #14895

sgjesse opened this issue Nov 7, 2013 · 4 comments
Assignees
Labels
area-infrastructure Use area-infrastructure for SDK infrastructure issues, like continuous integration bot changes. closed-obsolete Closed as the reported issue is no longer relevant

Comments

@sgjesse
Copy link
Contributor

sgjesse commented Nov 7, 2013

The folder C:\Program Files (x86)\Dart Editor is used for installing both the 32-bit and the 64-bit version on 64-bit Windows 7.

The 32-bit version should go in that location and the 64-bit version should go in C:\Program Files\Dart Editor

@ricowind
Copy link
Contributor

ricowind commented Nov 7, 2013

Set owner to @ricowind.

@ricowind
Copy link
Contributor

ricowind commented Nov 7, 2013

Removed Priority-Unassigned label.
Added Priority-Medium label.

@anders-sandholm
Copy link
Contributor

Removed Area-Build label.
Added Area-Infrastructure label.

@ricowind
Copy link
Contributor

ricowind commented Jun 2, 2015

Added AssumedStale label.

@sgjesse sgjesse added Type-Defect area-infrastructure Use area-infrastructure for SDK infrastructure issues, like continuous integration bot changes. closed-obsolete Closed as the reported issue is no longer relevant labels Jun 2, 2015
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-infrastructure Use area-infrastructure for SDK infrastructure issues, like continuous integration bot changes. closed-obsolete Closed as the reported issue is no longer relevant
Projects
None yet
Development

No branches or pull requests

3 participants