-
Notifications
You must be signed in to change notification settings - Fork 155
FileNotFoundException trying to load assembly System.Configuration.ConfigurationManager #169
Comments
Do you have a repro project? |
@paulomorgado which version of the .NET Core SDK and Visual Studio 2019 do you have installed? We need to load your project with the desktop version of MSBuild to do the conversion and it looks like something is blowing up in the process of doing that. |
Don't start try-convert from the Visual Studio 2019 developer command prompt. If you start it from the VS developer command prompt you get this error. If you run it from a normal powershell instance or the regular command prompt it works fine. Source: I just got the same error and this was how I fixed it. |
hmm I cannot repoduce this in my developer command prompt. which version of the .NET Core sdks do you have installed? |
According to Add/Remove Programs I had the following .NET Core versions installed on the machine where I can reproduce the issue:
Most of these were probably installed by Visual Studio updates. But like I said, it works fine if you're not using the VS developer command prompt, so hopefully that works for other people who run into this. |
@Sappharad if you run |
@jmarolf No, they both say 3.1.100 |
@jmarolf, @Sappharad is right. It doesn't work on the This is my
|
Ah ha! Developer powershell. I had been testing it on cmd, thanks!
|
Unfortunately I am not able to reproduce this. If someone could set COREHOST_TRACE = 1 on a machine where this is happening that would allow us to get more info about where the runtime is looking for assemblies. |
@jmarolf I've attached try-convert.txt. The project converts fine using a regular cmd, but fails when using the Developer Command Prompt and Developer PowerShell (opened through Visual Studio). |
First time I tried, I got:
What am I missing here?
The text was updated successfully, but these errors were encountered: