You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Remote Debug fails for projects that multi target several frameworks (Error NETSDK1129) #36
[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]
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.
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.
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.
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.
Activity
MagicAndre1981 commentedon Jul 7, 2021
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 commentedon Jul 8, 2021
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
ProjectPropertiesand set it inCopyFromto value ofFriendlyTargetFramework, but this is always the first value from TargetFrameworks and not the value from the debug settings of the project.MagicAndre1981 commentedon Jul 12, 2021
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
IActiveDebugFrameworkServicesand 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 commentedon Jul 13, 2021
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 commentedon Jul 20, 2021
I created now the PR #38 with
nuget.configthat gets the required packages @jefflillfixed nforgeio#36 : Error NETSDK1129 for projects that multi target s…
MagicAndre1981 commentedon Dec 19, 2023
@jefflill are you working again on the extension?
jefflill commentedon Dec 19, 2023
MagicAndre1981 commentedon Dec 19, 2023
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.