Announcement

Collapse
No announcement yet.

HS-634 - mono-vbnc deprecated

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • garyd9
    replied
    For anyone else trying to track down mono-vbnc, the following instructions work even on debian 12.

    https://www.mono-project.com/downloa...oad-lin-debian

    After adding the new repo following the instructions in the link, you can get the mono-devel as well as mono-vbnc packages.

    As a side note, isn't it about time for HS to move beyond mono and migrate to a supported version of .net? dotnet6 and dotnet8 are really robust and actually supported.

    Leave a comment:


  • ocgltd
    replied
    Any update on this issue as of July 16 2023 ? I.e. is mono-vbnc still required or can I safely skip it. The HS4 installation instructions still say to add mono-vbnc which I would prefer not to do. Is there a command I could use to test if vbnc is needed?

    I did a search for mono-vbnc it is no longer offer on the microsoft site. And I can't find it on github.

    I'm running AlmaLinux 9 (RedHat 9 clone) so there is also no mono vbnc package.

    Leave a comment:


  • pistacheL0
    replied
    So.. changed all vbnc to vbc in those files and tested it on my machine... it works. I do not know if they will approve ..

    best solution would be if hs4 change its call.

    https://github.com/mono/mono/pull/21507/commits

    Leave a comment:


  • Tillsy
    replied
    According to that link, it's G14 classified

    Leave a comment:


  • Guest
    Guest replied
    Originally posted by jon00 View Post

    Rich has fixed the mono issue in a test beta: https://forums.homeseer.com/forum/de...05#post1370405
    I missed this one. What have he done?

    Leave a comment:


  • Eman
    replied
    Originally posted by jon00 View Post

    Rich has fixed the mono issue in a test beta: https://forums.homeseer.com/forum/de...05#post1370405
    Nice one!


    Eman.

    Leave a comment:


  • jon00
    replied
    Originally posted by Eman View Post
    xbuild-use-roslyn-vbc.patch

    Caution! This is not my field but a question Can this approach be used to fix the mono issue by changing the version in this file :https://build.opensuse.org/package/v...patch?expand=1 by replacing it with the current version of mono which is mentioned here? (In other words "Hack it" ?) Or is it the same as it's expressed here #14 : https://forums.homeseer.com/forum/de...71#post1363571



    Eman.
    Rich has fixed the mono issue in a test beta: https://forums.homeseer.com/forum/de...05#post1370405

    Leave a comment:


  • Eman
    replied
    xbuild-use-roslyn-vbc.patch

    Caution! This is not my field but a question Can this approach be used to fix the mono issue by changing the version in this file :https://build.opensuse.org/package/v...patch?expand=1 by replacing it with the current version of mono which is mentioned here? (In other words "Hack it" ?) Or is it the same as it's expressed here #14 : https://forums.homeseer.com/forum/de...71#post1363571



    Eman.

    Leave a comment:


  • macromark
    replied
    logged

    Leave a comment:


  • Pete
    replied
    Hoping this is implemented in HS4. It works nicely in HS3 these days.

    Leave a comment:


  • Guest
    Guest replied
    Originally posted by rjh View Post

    There is a post a in this forum on a workaround, will that work for you?
    no! because of this ! this is an easy fix. Please reasd the thread entirely
    https://forums.homeseer.com/forum/de...ersion-3-0-0-1

    Leave a comment:


  • rjh
    replied
    I did ask the MONO group about this but no response so far so I have doubts that they will do anything about it any time soon. Also, Microsoft just announced they are no longer adding any features to VB so I suspect efforts regarding any work on it will be ignored, or priority lowered (just my guess).

    There is a post a in this forum on a workaround, will that work for you?

    Leave a comment:


  • concordseer
    replied
    Workarounds are fine in open source but I’d definitely leave this to HS on the commercial side. Best they resolve these issues directly with Xamirin and release an update to reflect their findings.

    Leave a comment:


  • zwolfpack
    replied
    A workaround to the embedded call issue is to split the embedded statement into two as I did in the example.

    As to what HomeSeer should do ... that's up to them. I've run with it about as far as I can; I'm no dotNet developer ... I installed Visual Studio less than a month ago

    Leave a comment:


  • Guest
    Guest replied
    So calling an object inside another one can’t be done with vbc.

    ex: I want to set a value tu the value of another device .


    at that point. Should just homeseer communicate to mono via github ...to change their code that use the depreciated vbnc when hs call vbcodecompiler class?? Or is the embedded call won work in that case too?

    Leave a comment:

Working...
X