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

Make .NET Desktop fsi.exe 32-bit again and make Desktop fsiAnyCpu.exe (64-bit) the default to launch in VS #6223

Merged
merged 1 commit into from
Feb 16, 2019

Conversation

dsyme
Copy link
Contributor

@dsyme dsyme commented Feb 10, 2019

Fixes #6219

In addition, for dev16.0 I think it would make sense to make 64-bit the default when launching VS in Visual Studio for dev16.0. For example ML.NET only works with 64-bit, and F# Interactive in NET Core is 64-bit always. This PR makes this change too.

@dsyme dsyme changed the title Make .NET Desktop fsi.exe 32-bit again and make fsiAnyCpu.exe (64-bit) the default to launch in VS Make .NET Desktop fsi.exe 32-bit again and make Desktop fsiAnyCpu.exe (64-bit) the default to launch in VS Feb 10, 2019
@KevinRansom
Copy link
Member

@dsyme,

Okay I think this makes sense. Retain a 32bit desktop FSI for back-compatability, but migrate VS forward to the 64 bit build. The only thing that I am unsure about is that fsi.exe "the good name" gets to be the 32 bit version ... the non default version.

This would mean that VS scripts that run in 64 bit, would have a hard time on the command line, unless someone knew to use the FsiAnyCPU.exe.

Regardless the above is still better than silently upgrading fsi.exe to Any CPU and retaining fsi anycpu as exactly the same thing to confuse folks.

Anyway this puts us back to where we were in dev15.9 except for updating FSI to 64 bit where it can be.
So all is good.

Kevin

Copy link
Member

@KevinRansom KevinRansom left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good.

@cartermp cartermp added this to the 16.0 milestone Feb 12, 2019
@KevinRansom KevinRansom merged commit 740a39d into dotnet:dev16.0 Feb 16, 2019
dsyme added a commit to dsyme/fsharp that referenced this pull request Feb 28, 2019
dsyme added a commit that referenced this pull request Mar 1, 2019
* Make .NET Desktop fsi.exe 32-bit again and make Desktop fsiAnyCpu.exe (64-bit) the default to launch in VS #6223

* make fsc.exe 32-bit for compat

* make fsc.exe 32-bit for compat

* improve diagnostics

* fix tests

* fix determinism
dsyme added a commit that referenced this pull request Mar 2, 2019
* process large expressions systematically

* add test cases

* update tests

* Make .NET Desktop fsi.exe 32-bit again and make Desktop fsiAnyCpu.exe (64-bit) the default to launch in VS #6223

* make fsc.exe 32-bit for compat

* make fsc.exe 32-bit for compat

* fix build

* fix build

* ramp up max testing

* correct optimization of linear matches

* improve diagnostics

* fix tests

* tests only on .NET Framework for now

* fix determinism
dsyme pushed a commit that referenced this pull request Mar 2, 2019
* Make .NET Desktop fsi.exe 32-bit again and make Desktop fsiAnyCpu.exe (64-bit) the default to launch in VS #6223

* make fsc.exe 32-bit for compat

* make fsc.exe 32-bit for compat

* improve diagnostics

* fix tests

* fix determinism
@cartermp cartermp removed this from the 16.0 milestone Mar 10, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants