From 56f55f6d0c218c0beb59005d90080d9949c948b0 Mon Sep 17 00:00:00 2001 From: Tommi Hassinen Date: Mon, 9 Aug 2021 13:28:08 +0300 Subject: [PATCH 1/4] update README.md --- README.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/README.md b/README.md index e179d5fd8d4..e34ff0a9f35 100644 --- a/README.md +++ b/README.md @@ -1,3 +1,7 @@ +For my own developments see these braches: +------------------------------------------ + * `th2021_debugger_fixes`: Disable DotNetCoreProjectExtension usage, set extension dll for .NetCore targets while keeping extension exe for .NetFramework targets. + **PLEASE NOTE!** This is an effort to get monodevelop open sourced again. From fecb83fc558406bec9b9a21aae07b8bceae89294 Mon Sep 17 00:00:00 2001 From: Tommi Hassinen Date: Mon, 9 Aug 2021 15:13:41 +0300 Subject: [PATCH 2/4] update README.md --- README.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index e34ff0a9f35..4d5fd468be5 100644 --- a/README.md +++ b/README.md @@ -1,6 +1,8 @@ For my own developments see these braches: ------------------------------------------ - * `th2021_debugger_fixes`: Disable DotNetCoreProjectExtension usage, set extension dll for .NetCore targets while keeping extension exe for .NetFramework targets. +* `th2021_debugger_fixes`: + * Problem: when building and running DotDevelop without any of the dotnet-sdks installed, debugging apps did not work. However debugging worked after installing dotnet-sdk-5.0 and adding symlinks so that the assemblies were found. It turned out that DotNetCoreProjectExtension was not activated, and MonoSoftDebugger was activated instead, due to some new values returned by dotnet-sdk-5. + * Solution: since the recent mono-versions can handle .NetCore -projects as well, DotNetCoreProjectExtension usage is disabled. To allow debugger find the asseblies, file extension ".dll" is set for executables except for .NetFramework targets for which ".exe" is used as before. Now building and debugging works up to netcoreapp3.1 -targets (all targets supported by mono runtime at the moment). **PLEASE NOTE!** From a42167c81544cb60c3a284d5ff100f2f77a71ed3 Mon Sep 17 00:00:00 2001 From: Tommi Hassinen Date: Mon, 9 Aug 2021 19:29:18 +0300 Subject: [PATCH 3/4] update README.md --- README.md | 16 ++++++++++++---- 1 file changed, 12 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index 4d5fd468be5..85a73fc2d79 100644 --- a/README.md +++ b/README.md @@ -1,8 +1,16 @@ -For my own developments see these braches: ------------------------------------------- +For my own developments see these branches: +------------------------------------------- + * `th2021_debugger_fixes`: - * Problem: when building and running DotDevelop without any of the dotnet-sdks installed, debugging apps did not work. However debugging worked after installing dotnet-sdk-5.0 and adding symlinks so that the assemblies were found. It turned out that DotNetCoreProjectExtension was not activated, and MonoSoftDebugger was activated instead, due to some new values returned by dotnet-sdk-5. - * Solution: since the recent mono-versions can handle .NetCore -projects as well, DotNetCoreProjectExtension usage is disabled. To allow debugger find the asseblies, file extension ".dll" is set for executables except for .NetFramework targets for which ".exe" is used as before. Now building and debugging works up to netcoreapp3.1 -targets (all targets supported by mono runtime at the moment). + * Problem: when building and running DotDevelop without any of the dotnet-sdks installed, debugging apps did not work. However debugging worked after installing dotnet-sdk-5.0 and adding symlinks so that debugger was able to find the assemblies to be debugged. It turned out that DotNetCoreProjectExtension was not activated, and MonoSoftDebugger was activated instead, due to some new/nonvalid values returned by dotnet-sdk-5. + * Solution: since the recent mono-versions can handle .NetCore -projects as well, DotNetCoreProjectExtension usage is disabled. To allow debugger find the asseblies, file extension ".dll" is set for executables except for .NetFramework targets for which ".exe" is used as originally. + mono and dotnet-sdk-3.1: building and debugging works up to netcoreapp3.1 -targets. + dotnet-sdk-5.0: not working, perhaps due to mono-msbuild not being recent enough? see: + https://github.com/mono/mono/issues/20250 + https://github.com/dotnet/core/issues/6231 + +The ORIGINAL DotDevelop README-file starts now: +----------------------------------------------- **PLEASE NOTE!** From 6c1e38ecfe1c0e7032b18d5d44ea63ca5792e725 Mon Sep 17 00:00:00 2001 From: Tommi Hassinen Date: Mon, 9 Aug 2021 19:35:03 +0300 Subject: [PATCH 4/4] update README.md --- README.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index 85a73fc2d79..94e85267011 100644 --- a/README.md +++ b/README.md @@ -4,10 +4,10 @@ For my own developments see these branches: * `th2021_debugger_fixes`: * Problem: when building and running DotDevelop without any of the dotnet-sdks installed, debugging apps did not work. However debugging worked after installing dotnet-sdk-5.0 and adding symlinks so that debugger was able to find the assemblies to be debugged. It turned out that DotNetCoreProjectExtension was not activated, and MonoSoftDebugger was activated instead, due to some new/nonvalid values returned by dotnet-sdk-5. * Solution: since the recent mono-versions can handle .NetCore -projects as well, DotNetCoreProjectExtension usage is disabled. To allow debugger find the asseblies, file extension ".dll" is set for executables except for .NetFramework targets for which ".exe" is used as originally. - mono and dotnet-sdk-3.1: building and debugging works up to netcoreapp3.1 -targets. - dotnet-sdk-5.0: not working, perhaps due to mono-msbuild not being recent enough? see: - https://github.com/mono/mono/issues/20250 - https://github.com/dotnet/core/issues/6231 + * mono and dotnet-sdk-3.1: building and debugging works up to netcoreapp3.1 -targets. + * dotnet-sdk-5.0: not working, perhaps due to mono-msbuild not being recent enough? see: + https://github.com/mono/mono/issues/20250 + https://github.com/dotnet/core/issues/6231 The ORIGINAL DotDevelop README-file starts now: -----------------------------------------------