Remote Debug fails for projects that multi target several frameworks (Error NETSDK1129)

[MagicAndre1981]

The remote debug fails for projects that multi target several frameworks added in the csproj:

<Project Sdk="Microsoft.NET.Sdk">

  <PropertyGroup>
    <OutputType>Exe</OutputType>
    <TargetFrameworks>netcoreapp3.1;net5.0</TargetFrameworks>
    <AutoGenerateBindingRedirects>true</AutoGenerateBindingRedirects>
  </PropertyGroup>

</Project>

Trying to debug generates an error message

[raspberry]: INFO: Checking for native Windows OpenSSH client
[raspberry]: INFO: Building: D:\FooApp\FooApp\FooApp.csproj
[raspberry]: INFO: Build succeeded
[raspberry]: INFO: Publishing: D:\FooApp\FooApp\FooApp.csproj
[raspberry]: ERROR: Publish failed: ExitCode=1
Microsoft (R)-Build-Engine, Version 16.10.1+2fd48ab73 für .NET
Copyright (C) Microsoft Corporation. Alle Rechte vorbehalten.
  Wiederherzustellende Projekte werden ermittelt...
  "D:\FooApp\FooApp\FooApp.csproj" wiederhergestellt (in 89 ms).
C:\Program Files\dotnet\sdk\5.0.301\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.Sdk.CrossTargeting.targets(27,5): error NETSDK1129: Das Ziel für "Publish" wird ohne Angabe eines Zielframeworks nicht unterstützt. Das aktuelle Projekt verwendet mehrere Frameworks als Ziel. Sie müssen das Framework für die veröffentlichte Anwendung angeben. [D:\FooApp\FooApp\FooApp.csproj]

when I only use 1 targetframework, debug works

[MagicAndre1981]

any update? When I try to debug the extension from source code I only get a ghosted VS2019 window and VS is not responding

[MagicAndre1981]

ok, on a second VM debugging works and I can see in PublishProjectAsync the --framework option is not set.

So I added a property Framework to ProjectProperties and set it in CopyFrom to value of FriendlyTargetFramework, but this is always the first value from TargetFrameworks and not the value from the debug settings of the project.

[MagicAndre1981]

ok, I fixed it in my local copy. I need to use IActiveDebugFrameworkServices to get information about debugging info (configuration, platform and targetframework).

And when I pass this retrieved targetframework to dotnet publish command in DebugHelper, the publish and debug works.

But there is an issue. The stable nuget package Microsoft.VisualStudio.ProjectSystem.Managed 2.0.6142705 on nuget.org misses the required Interface IActiveDebugFrameworkServices and I have to use the pre-release feed on azure to get the 16.10 version.

Now there is the question what to do? Is it ok to use a lot of pre-release packages?

[MagicAndre1981]

any update @jefflill ? Should I create a PR by using a lot of pre-Release nugets from Azure feed? I added a nuget.config wit the feed so build will work.

[MagicAndre1981]

Should I create a PR by using a lot of pre-Release nugets from Azure feed? I added a nuget.config wit the feed so build will work.

I created now the PR #38 with nuget.config that gets the required packages @jefflill

[MagicAndre1981]

@jefflill are you working again on the extension?

[jefflill]

Yeah, I’ve been thinking about releasing the VS 2022 support pull request, but I’ve been busy with another project. Want to help? —Jeff

…

On Mon, Dec 18, 2023 at 11:56 PM MagicAndre1981 ***@***.***> wrote: @jefflill <https://github.com/jefflill> are you working again on the extension? — Reply to this email directly, view it on GitHub <#36 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABFOLD37JENTJELNFOZC5HLYKFCBPAVCNFSM46Y3ISVKU5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TCOBWGIZDQMBWGA2Q> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[MagicAndre1981]

where you able to get the 2022 versions of my added libs? The user who forked it and added VS2022 support reverted my PR because we was not able to get the prerelease libs from private nuget feeds. I haven't checked if those feeds are still valid.