The SDK 'Microsoft.NET.Sdk' specified could not be found. #143
Comments
|
Thanks for the report, Do you only have a preview release from 16.x ? and seems like stable in 15.x
|
|
Pardon for the late reply! Here's the output: I've also had this problem (not sure if related): I've changed the xml file to the following as a workaround: <SdkResolver>
<Path>C:\Program Files (x86)\Microsoft Visual Studio\2019\Preview\Common7\IDE\CommonExtensions\Microsoft\NuGet\Microsoft.Build.NuGetSdkResolver.dll</Path>
</SdkResolver> |
|
I guess I could try reinstalling both Buildtools? |
Don't worry, this was actually fast :) Since -prerelease indicates the same result, could you please also check this command:
Hmm, it could be really similar to recent problem: #139 (comment) Thus, please show also result for this: |
It only outputs the following:
Output``` Visual Studio Locator version 2.7.1+180c706d56 [query version 2.6.32.15131] Copyright (C) Microsoft Corporation. All rights reserved.instanceId: 19ee2f3f instanceId: 3859cb7f |
|
Didn't mean to close it. Is my installation somehow broken? |
No, I'm seeing a two Moreover, last result for hMSBuild is also ok. Are you sure that What about this? and this |
Yup. Don't know why it happens though.
|
|
what about this: |
|
Only this: |
|
And please this: |
|
Sorry again for the late reply.. Closed the tab accidentally.
Output
Output |
|
The results confuses me a bit. Thank you for the new details! Before your last reply I thought about bug or changed behavior of the vswhere tool between local and remote versions. But the default command for hmsbuild points exactly on local use:
Where used 2.7.1 due to result from #143 (comment) But other forcibly use of 2.8.4 is also detects 16.6.29911.98 Can you please try again for this first command: If still, then I will look later problems as part of the hMSBuild project. For DllExport project more like we need add |
So, did I somehow break your project? Am a bit confused. |
|
I've opened DllExport and on the data tab there's this: DataIf needed, I could try using a normal .NET Framework project for this. |
No, I meant the bug that should be considered as part of other project. DllExport includes hMSBuild but this are different projects of course
This is other result from your first reply:
And it's more like this is what we need. Later I'll push solution with -prerelease key.
No, it does not related to netfx. |
|
Oh I see. Thanks a lot for your time! |
|
@NickAcPT Yes, please confirm solution 003360a |
|
Pardon the delay, but I can confirm that it just works. Thanks a lot. |
Good!
I don't think so :) You can close it if your problem is fixed now. Or it will be closed anyway after merging into master branch. @NickAcPT I don't have ETA yet for the new public release. I think we'll wait a bit to review the problem #141 and related. But you can use this CI build as a temporary solution in your case. Please don't use it in production before official release. |
I'll leave this opened until the PR gets merged so that it's easier to know what's been fixed and what wasn't.
Will do! Thanks a lot for helping 👍 |
|
FYI: corrected processing of -msb key after last fixes for this problem. Use 848e19b instead. |
* NEW: Pre-Processing feature. PR #146. Related issue #40 Official ILMerge support; https://github.com/dotnet/ILMerge Quick integration with Conari for most easy access to unmanaged features; https://github.com/3F/Conari +Other related tools and assembly manipulations. Manual configuring: #40 (comment) * NEW: Post-Processing. PR #148. Continues direction of Pre-Processing feature. PR #146 Related issue #144 Explanation and details: https://ko-fi.com/Blog/Post/ILMerge---Conari---Debug-information---DllExport-=-O5O61MV8A 1.7.1 Provides only basic GUI support for predefined options. Thus, *! Some Post-Proc features are not yet available in GUI. But you can already configure it with msbuild: ``` <Target Name="DllExportPostProc"> <!-- After activation, you can access the following properties and items: $(DllExport) - version $(DllExportSln) - full path to .sln which controls current project $(DllExportPrj) - full path to current project where processed .NET DllExport @(DllExportDirX64) - $(TargetDir)x64\*.* @(DllExportDirX86) - $(TargetDir)x86\*.* @(DllExportDirBefore) - $(TargetDir)Before\*.* @(DllExportDirAfter) - $(TargetDir)After\*.* @(DllExportDependents + populated property name) - each populated properties from DllExportProcEnv, e.g. DllExportDependentsTargetDir @(DllExportDependencies + populated property name) - each populated properties from DllExportProcEnv, e.g. DllExportDependenciesTargetDir @(DllExportSeqDependents + populated property name) - each populated properties from DllExportProcEnv, e.g. DllExportSeqDependentsTargetDir --> </Target> ``` #148 (comment) * NEW: Optional copying of intermediate files + x86+x64 directories into output for projects that dependent on projects where used DllExport. Issue #144. Including sequential referencing through other projects: #148 (comment) * FIXED: Fixed #140 ... failed to create safe SSL/TLS context. * FIXED: Pack of fixes for .net.dllexport.targets. PR #147. * Fixed "Cannot modify an evaluated object originating in an imported file". * Fixed possible duplication in .net.dllexport.targets when configuring. * Adds removing TargetsFile if not used. * Fixed possible loss of settings in .targets when configuring. * FIXED: Fixed #143 'Microsoft.NET.Sdk' specified could not be found. * FIXED: A multiple empty `<PropertyGroup />` in project files during new configuration. * CHANGED: Wizard. Dropped support for ssl3 + tls1.0 + tls1.1 * CHANGED: Wizard. Simplified notification for stable versions. * CHANGED: Manager. Access to hMSBuild tool (packed) via `-hMSBuild` key. https://github.com/3F/hMSBuild Since it uses packed version (while GetNuTool is integrated inside), you need use -dxp-version to control specific version. * CHANGED: Updated Cecil 0.11.2 https://github.com/jbevain/cecil/releases/tag/0.11.2 * CHANGED: Updated MvsSln 2.5.2 https://github.com/3F/MvsSln/releases/tag/2.5.2
Steps to reproduce:
I created a .Net Core 3.1 class library project.
DllExport -version: .NET DllExport 1.7.0.60761+0a002a7Information from
Datatab or log data:Demo Project files / Samples / etc.:
The text was updated successfully, but these errors were encountered: