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

visual basic interactive doesn't start for dotnet 6.0 #57911

Open
carellagermano opened this issue Nov 21, 2021 · 1 comment
Open

visual basic interactive doesn't start for dotnet 6.0 #57911

carellagermano opened this issue Nov 21, 2021 · 1 comment
Assignees
Milestone

Comments

@carellagermano
Copy link

Version Used:

Steps to Reproduce:

Expected Behavior:

Actual Behavior:
Hi,
I'm Germano, from Italy.
I cloned git repository in order to build visual basic interactive, that is not included in roslyn version for visual studio.
Before building I downloaded and installed dotnet 6.0.100 sdk, visual studio 2022 preview comunity.
So, I started developer prompt for visual studio 2022 and cloned git repository.
I ran restore.cmd and build.cmd -Config Release.
After process finished I went in artifacts\bin\vbi\release\net6.0 and ran vbi.exe.
Vbi.exe can't find all libraries, such as System.Collections, System.Threading.Tasks, and Microsoft.VisualBasicdll, that is in same folder; I attached log.txt file with the errors and warnings.
So I tried to run csi.exe from release\net6.0 folder and it worked, then I ran vbi.exe in release\net4.72 and it worked.
The code is the same, but in release\net6.0 folder of vbi.exe there are vbo.runtimeconfig.json and vbi.deps.json, that in release\net4.72 folder are absents.
What can I do? I would include vbi.exe in roslyn\bin folder of my couple of visual studio.
log.txt

@dotnet-issue-labeler dotnet-issue-labeler bot added Area-Interactive untriaged Issues and PRs which have not yet been triaged by a lead labels Nov 21, 2021
@paul1956
Copy link
Contributor

Don't know about VBI but every one of my apps that I ported to VS 2022 and .Net 6 broke the same way. If you open in VS you will see you are missing reference to System and Visual Basic libraries that were previously always included in VB projects.
I had to add to get my projects to work and I don't use VisualBasic.DLL or I would been to add that as well

  <ItemGroup>
    <Import Include="System" />
    <Import Include="System.Collections.Generic" />
    <Import Include="System.Data" />
    <Import Include="System.Drawing" />
    <Import Include="System.Windows.Forms" />
  </ItemGroup>

@jinujoseph jinujoseph added Bug and removed untriaged Issues and PRs which have not yet been triaged by a lead labels Dec 1, 2021
@jinujoseph jinujoseph added this to the Backlog milestone Dec 1, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants