-
-
Notifications
You must be signed in to change notification settings - Fork 133
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
Configure fails for unknown reason #139
Comments
Thanks for the report, Is there any reason why are you using an offline version? Did you try with normal full version? I'm watching problem with incorrect msbuild instance in your environment. Thus, can you first show the result for the following command via hMSBuild:
And via vswhere.exe
|
@3F I used the offline version because the Online version for some reason shows these two strange messages:
But probably those messages aren't related.
and
same output for |
The first message is related to another issue, thanks for the information!
Since vswhere indicates the same result, I think the problem is related rather to the installation API but not to DllExport.
Can you describe more about installation way (part of what is) and actual paths to the actual tools? What full version of the instance? Also, can you try with
If still nothing, please report here about results using vswhere command above: https://github.com/microsoft/vswhere/issues |
MSBuild is included with dotnet core SDK 3.1 which comes with visual studio 2019 currently installed on my device, visual studio 2019 currently is pending an update.
|
I forget to mention the dotnet core SDK path: C:\Program Files\dotnet\sdk\3.1.102 |
Well, this is it:
I'm not really sure about incomplete stage for the products. And I am not ready to support it today. But anyone else can open PR to consider some additional support with surely tested environment where only incomplete products. You need to complete the installation for today and please make sure you have installed MSBuild component in addition to mentioned .NET Core 3.1 SDK:
I close the issue due to irrelevant problem for the current project. Feel free to continue for some related purposes. |
I forgot to say, an additional MSBuild component above is required only when you're trying .NET Core based projects and/or modern SDK style. At least today. Who follows me also should know about future planned changes in this area. Hope for this. |
How to reproduce:
... Launch DLLExport.bat in the solution directory
... Choose a .Net standard 2.1 project or .Net core 3.1 project
... Click Apply
... Nothing happens, the project isn't changed and DLLExport isn't found.
-version
: v1.7.0.60761+0a002a7-build-info
:S_NUM: 1.7.0
S_REV: 60761
S_NUM_REV: 1.7.0.60761
S_REL:
bSha1: 0a002a7
bName: master
bRevc: 201
MetaCor: netstandard1.1
MetaLib: v2.0
Wizard: v4.0
Configuration: PublicRelease
Platform: Any CPU
cfgname: Release
revDeltaBase: 2016/10/12
revDeltaMin: 1000
revDeltaMax: 65534
Full command to Manager: ./DLLExport.bat
Project type: .Net standard project or .Net core project
Environment ( VS, MSBuild, ...): .Net core 3.1, IDE IS Rider 2019.3 not Visual Studio, MSBUILD version is 16
log:
DotNetCoreProblem.log
The text was updated successfully, but these errors were encountered: