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.

Sign up for GitHub

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

Jump to bottom

c# Interactive System.BadImageFormatException: Could not load file or assembly #7663

Closed
andrew-vdb opened this issue Dec 22, 2015 · 10 comments
Closed

c# Interactive System.BadImageFormatException: Could not load file or assembly #7663

andrew-vdb opened this issue Dec 22, 2015 · 10 comments
Labels
Area-Interactive Feature Request
Milestone
Backlog

Comments

@andrew-vdb
Copy link

c# interactive window on Visual Studio 2015 Update 1 seems have problem when referencing x64 dll as we get System.BadImageFormatException exception
@tmat
Copy link
Member

tmat commented Dec 25, 2015

The hosting process is 32bit. We don't support 64bit currently, it's on our backlog though.

@tmat tmat assigned tmat and unassigned tmat Dec 25, 2015
@tmat tmat added this to the 1.3 milestone Dec 25, 2015
@ManishJayaswal ManishJayaswal modified the milestones: Unknown, 1.3 May 5, 2016
@mjewkes
Copy link

mjewkes commented Jul 27, 2016

What needs to be done to support this? I'd love to use C# interactive to explore some >4GB datasets.

@Sebazzz
Copy link

Sebazzz commented Aug 17, 2016

Note that when running CSI directly, there is no issue.

@poke
Copy link

poke commented Mar 29, 2017

Any news on this? I’d really like to use the SharePoint DLLs from within the Interactive C# window but they require a 64bit process… :/

@Aldebaran91
Copy link

Aldebaran91 commented Jun 29, 2017 •
edited
Loading

C# interactive with 64bit would be very useful

PS: And also please enable multiple C# interactive views and graphic support ala Apple Swift Playground, Python, etc. etc.

@ewinnington
Copy link

When working in C# interactive and database drivers in 64 bit, I get this error.

It would be great to configure the c# interactive in VS to 64 bit

@BrunoJuchli
Copy link

BrunoJuchli commented Jun 8, 2018 •
edited
Loading

What's the state of this now? I've got a x86 dll (using com components) and with VS 2017.7.3 I can't load the assembly because C# interative is running in x64 (also see https://stackoverflow.com/questions/49067671/vs-2017-c-sharp-interactive-is-not-a-valid-win32-application).

So i guess if you want to have C# Interactive on x86 dll you've ought to use VS2015, and if you want C# interactive on x64 you ought to use VS2017.

Or am I missing something?

It would be nice if VS2017 C# interactive would support both x64 and x86.

Note: error:

Could not load file or assembly '*********' or one of its dependencies. is not a valid Win32 application. (Exception from HRESULT: 0x800700C1)

  • AsyncTaskMethodBuilder.Start(ref TStateMachine)

@tmat
Copy link
Member

tmat commented Jun 8, 2018

It seems that some change inadvertently flipped the bitness to 64bit. Will investigate.

@poke
Copy link

poke commented Jun 8, 2018

Whatever that change was, can we get a toggle in the settings? 😅

@tmat tmat mentioned this issue Jun 20, 2018
Merged
@tmat
Copy link
Member

tmat commented Jun 29, 2018 •
edited
Loading

Fixed by #28006.

The default stays as 64. #reset 32 switches to 32-bit, #reset 64 switches to 64-bit.

@tmat tmat closed this as completed Jun 29, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Area-Interactive Feature Request
Projects
None yet
Milestone
Backlog
Development

No branches or pull requests
10 participants
@tmat @mjewkes @poke @davkean @Sebazzz @BrunoJuchli @ewinnington @ManishJayaswal @andrew-vdb @Aldebaran91