Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Andres G. Aragoneses
    @knocte
    why would you need the full monodevelop?
    @ekrogh as far as I understand, you just need to install the mono-msbuild or msbuild apt package
    @ekrogh I packaged a xamarin gtk project as a snap too, in case you want to check out how I did it, check my GitHubActions workflows here: https://github.com/nblockchain/geewallet
    (the frontend branch, not master)
    Eigil Krogh Sorensen
    @ekrogh
    Thanks! I did not know msbuild existed in apt package ! (The reason I want msbuild is that I want to compile my .csproj. I have no makefile - and I don't know if visual studio or vs code can make one. I don't know much about Makefile)
    zygon.sisyphus
    @zygon.sisyphus:matrix.org
    [m]
    Hi! is poassible to build modevelop/dotdevelop with msys2/mingw and mono ?
    Nikolay Mishev
    @NikolayMishev

    Hi guys,
    We are having an issue with a Visual Studio for Mac Extension build. Currently we have dependancies to MonoDevelop.Ide and MonoDevelop.Core and we have hardcoded version(17.0) the problem is that for example if Visual Studio for Mac 2022 Preview release new version17.2 our extensions stops working bacause it cannot find the dependancy with the correct version. So is there a way to build an Extension that would work in more than one Visual Studio for Mac 2022 release or we have to release new version of the Extension each time Visual Studio for MAC 2022 releases a new version?

    Excuse me if this question is not for this group, just did not find specific group for VS for Mac.

    Matt Ward
    @mrward
    @NikolayMishev Unfortunately this is not possible. There was an API break in VS Mac 17.3 so your extension would need to indicate it supports 17.3. The app compatibility version was changed from 17.0 to 17.3 due this API break which means extensions that target 17.0 will not be loaded by VS Mac 17.3. The main reason for this is if you are relying on the older API you may cause problems in 17.3 - my log monitor extension caused VS Mac 17.3 to crash, for example. You cannot have the same addin support both 17.0 and 17.3 without rebuilding it. Typically we avoid API breaks and an extension that targets an older VS Mac 17.x version would continue to work on later versions - this was the case for VS Mac 8.10 but we took an API break in 17.3 this time unfortunately.
    Nikolay Mishev
    @NikolayMishev
    Thank you a lot @mrward :)
    Derbazi
    @Derbazi
    Hello people,
    I am having a i guess rather simple question though I just can't get it to work. I was trying to setup remote debugging via Soft Debugger and MonoDevelop. I added the "MONODEVELOP_SDB_TEST" variable to 1 or YES (different sourced advice to using different values i tried both though I do not think it make any difference). Unfortunately the "Custom Command Mono Soft Debugger " menu item, that is referenced everywhere i looked, never shows up. Some sources apparantly use MonoDevelop 4.0. Was the feature removed in later versions? I am using MonoDevelop 7.8.4.
    Thank you in advance.
    Jonathan Kirszling
    @eoli3n
    Hi
    could anyone tell me when monodevelop will be officially available for the new Ubuntu 22.04 ?
    jammy is not listed
    Andres G. Aragoneses
    @knocte
    eoli3n: monodevelop is deprecated; the successor is dotdevelop
    Nikolay Mishev
    @NikolayMishev
    Hi guys me again.
    After I update VS for Mac 2022 to latest version I begun getting this error whenever I tried to build my extension.
    "Could not find a global instance of Visual Studio for Mac or MonoDevelop. Try providing an explicit value with MDBinDir"
    Any thoughts?
    I have VS for Mac 2019, VS for Mac 2022 and VS for Mac 2022 Preview installed if that helps.
    Dominique Louis
    @CartBlanche
    @NikolayMishev if you are loading your extension in VS2022 make sure its building using dotnet and not msbuild. Right click the project solution and there should be an option to uncheck in there under Build->General.
    Nikolay Mishev
    @NikolayMishev
    Thank you for this but it does not seems to fix the issue.
    ShalokShalom
    @ShalokShalom
    @knocte why not renaming the repo, then?
    Does anybody in the team care about fsharp?
    Andres G. Aragoneses
    @knocte
    @ShalokShalom because the maintainers of dotdevelop are not the same as the maintainers of monodevelop
    @ShalokShalom good question, I'm an F# dev myself too
    Nikolay Mishev
    @NikolayMishev

    Hi guys,

    Previously we were trying to migrate our VS for Mac extensions to VS for Mac 2022 so we kinda succseeded by following the steps from this wiki https://github.com/mhutch/MonoDevelop.AddinMaker/wiki/Migrating-AddInMaker-projects-to-support-Visual-Studio-2022-for-Mac-v17.x But one of our extensions uses gtk-sharp to show some custom dialogs within Visual Studio and this functionality is failing runtime after the migration with this error (System.TypeInitializationException: "The type initializer for 'Gtk.DialogAttribute' threw an exception." ---> System.DllNotFoundException: "Unable to load shared library 'libgtk-win32-2.0-0.dll' or one of its dependencies). This is working within VS for Mac 2019.
    Any help on this would be greatly appreciated.

    Matt Ward
    @mrward
    @NikolayMishev VS Mac does not support gtk#. You would need to port the UI to use native macOS appkit. VS Mac itself targets net6.0-macos and needs the macos dotnet workload installed to do the UI. I do not use the VS Mac sdk/extensions so not tried doing custom UI with it - in theory installing the macos workload and having your project target net6.0-macos should be enough. With my extensions I directly reference the dlls from the installed VS Mac, including the Microsoft.macOS.dll, so I can avoid anything to do with workloads - mrward/monodevelop-nuget-extensions@17e3e42
    Nikolay Mishev
    @NikolayMishev
    @mrward Thank you a lot.
    Nikolay Mishev
    @NikolayMishev

    Hello again @mrward another question I have regarding Visual Studio for Mac 2022. So we have custom project templates that we install in VIsual Studio and they work fine and all excep the part when we try to open specific project template through a command in the menu in that case we it seems that the method we use to open the specific template fails and fallbacks to the latest used template. This is the line we use(that by the way was working fine in VS for Mac 2019): IdeApp.ProjectOperations.NewSolution("TemplateID", false);

    The templates are visible in the VS new project wizard and are working correctly. So the issue should be just with line above.
    So is there something that is changed in VS for Mac 2022 and is there a place we can track such changes to the extensibility model of VS for Mac.

    Thank you in advance.

    Matt Ward
    @mrward
    Not really sure. If they are working in the New Project dialog then using ProjectOperations should work. This is with custom .nupkg files and the template id is unique?
    Will have to see if I can repro.
    Matt Ward
    @mrward
    Yeah something is not right here.
    Unless I am using the wrong template id :)
    Matt Ward
    @mrward
    Yeah it is broke. The port to native UI changed the behaviour. When the NSTableViews are loaded it gets a selection changed event which sets the selected template back to the first one in the recently used list.
    Nikolay Mishev
    @NikolayMishev
    Thank you @mrward so is there some place where we can folow the progress and see when this is resolved?
    Matt Ward
    @mrward
    I have an internal bug for this and a fix which should go into VS Mac 17.5. I suspect this will not be backported though and there is no real workaround here.
    Nikolay Mishev
    @NikolayMishev
    Thanks @mrward looking forward to the 17.5 release then :)
    Nikolay Mishev
    @NikolayMishev
    Hey @mrward quick question do you have some approximate date for the 17.5 release?
    Matt Ward
    @mrward
    @NikolayMishev Visual Studio for Mac 17.5 preview 1 is out now, as of a few minutes ago. That should include a fix for the new project dialog.
    Dan-Essin
    @Dan-Essin
    I'm new here, trying to install on windows. Encountered numerous problems. I start wi the first one:
    on https://www.monodevelop.com/download/
    "Download Gtk# on monoproject.com", click and get:
    ResourceNotFoundThe specified resource does not exist. RequestId:a84b55e5-601e-0043-2da0-f7a10d000000 Time:2022-11-13T20:42:01.2245635Z
    I'll post the others, but I took the immediate fact of encounter this error as a bad sign of what was to come
    Lex Li
    @lextm
    @Dan-Essin No one is now working on MonoDevelop for Windows. Please switch to other alternatives such as VS Code or JetBrains Fleet
    Dan-Essin
    @Dan-Essin
    What platforms are being worked on? How does one do "cross-platform development" if windows is not one of the platforms?
    Lex Li
    @lextm
    Dan-Essin
    @Dan-Essin
    Thanks. There is a Mono doc called Application Portability. It has a section labelled "Using Windows.Forms as a cross-platform API" that has no content. Is this because there are no significant issues using WinForms?
    Lex Li
    @lextm
    @Dan-Essin Mono as a whole is also going away, https://halfblood.pro/the-end-of-mono/ So, spare yourself from documentation that wasn't updated for a very long time. .NET Core is the unified platform for the future.
    Mr. Cookie
    @MrCookie0
    I know that monodevelop is ended, but can you tell me how to compile it?
    Lex Li
    @lextm
    @MrCookie0 In its last few months of life, the repo was not compilable. So, don't waste your time on mono/monodevelop repo unless you are really a C#/MSBuild guru that can help yourself. If your goal is to somehow compile it on Linux alone, dotdevelop/dotdevelop is getting closer to a full feature release, https://github.com/dotdevelop/dotdevelop