Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    William Obando
    @wocar
    That would be very much appreciated
    David Rettenbacher
    @warappa
    @wocar Do you mean the dashboard? It should be disabled by using livesharp --hide-dashboard if I remember correctly.
    William Obando
    @wocar
    @warappa ha! Thank you very much thats what i was looking for. Let me test it. Ty
    ricibald
    @ricibald

    @ionoy I have two questions:

    • how can I start the server configuring my static public IP address? I need to connect using Internet, not my Intranet (I'm using MacInCloud to host my iPhone Simulator)
    • I have configured LiveSharp in my Xamarin.Forms project. Now I want to configure it also in my specific Android & iOS project, how can I do it? I receive a warning because it can't find a startup class, I just need to declare my startup class & method?

    Thanks

    Mihhail Maslakov
    @ionoy
    1) I can add an attribute for that
    2) Here is a code from existing project [assembly: LiveSharpStart(typeof(MainActivity), nameof(MainActivity.OnCreate), typeof(Bundle))]
    @ricibald would something like [assembly: LiveSharpServerIp("192.168.1.88")] work in your case?
    Mihhail Maslakov
    @ionoy
    LiveSharp.1.6.36.nupkg
    8 replies
    here you go, @ricibald the previously mentioned attribute should work now
    Mihhail Maslakov
    @ionoy
    @ACertainDeveloper alright, thanks!
    ricibald
    @ricibald
    @ionoy you are impressive! Thanks
    Mihhail Maslakov
    @ionoy
    :thumbsup:
    David Rettenbacher
    @warappa
    I see, in 1.6.36 you implemented a reconnect and reinitialize if an unrecoverable error happens - nice.
    Although the update takes longer (reconnect, reinitialize) but then it works again.
    On my non-repo project I get some exceptions about incompatible generic parameters. I will file another issue, a repo may be not so easy...
    David Rettenbacher
    @warappa
    (PS: despite generics issues, but it still updates after reinitialize)
    Mihhail Maslakov
    @ionoy
    it seems like the disconnect issue is due to the SignalR NuGet package version mismatch or something
    I couldn't catch any actual exceptions
    David Rettenbacher
    @warappa
    Good point. I use SignalR 5.0.0, but server seems to use 3.1.3, that's the problem. And not easy to handle both Versions in a global dotnet tool...
    Andrew Camilleri
    @Kukks
    Every now and then, whenever I stop the application I am debugging that has Livesharp hooked in, LiveSharp seems to stay locked to the dlls and not allow me to start my application until I kill the livesharp server
    Mihhail Maslakov
    @ionoy
    @Kukks I still haven't found a reason for this, unfortunaly
    what would help if the next time it happened you noticed what dll's are locked, the project ones or references
    Andrew Camilleri
    @Kukks
    So, I have 2 projects in 1 solution with Livesharp in them. One of them is a razor Class lIbrary, the other is a WebAssembly that references it. Pretty sure it is the Razor Class Library that gets locked up
    still using dotnet 3.1 and in Rider if that helps
    Benjamin Vertonghen
    @vertonghenb
    @ionoy Having some issues with Generic Components using Blazor, the project runs fine without livesharp.
    error CS8627: A nullable type parameter must be known to be a value type or non-nullable reference type. Consider adding a 'class', 'struct', or type constraint.
    Benjamin Vertonghen
    @vertonghenb
    @ionoy //Fixed, was because of nullables in C#9
    Andrew Camilleri
    @Kukks
    When runnin as Blazor WASM project with livesharp, refreshing the page removes all the applied changes since i first ran the project
    Mihhail Maslakov
    @ionoy
    @Kukks LiveSharp should output message like "Project x is out of date. Sending diff." when it sees that there is a newer version available
    not sure what's going on in your case
    Andrew Camilleri
    @Kukks
    info: Microsoft.AspNetCore.Routing.EndpointMiddleware[1]
      Executed endpoint '/livesharp'
info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
      Request finished in 304667.0233ms 101
info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
      Request starting HTTP/2 OPTIONS https://localhost.livesharp.net:50539/livesharp/negotiate?negotiateVersion=1
info: Microsoft.AspNetCore.Cors.Infrastructure.CorsService[4]
      CORS policy execution successful.
info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
      Request finished in 0.5561ms 204
info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
      Request starting HTTP/2 POST https://localhost.livesharp.net:50539/livesharp/negotiate?negotiateVersion=1  0
info: Microsoft.AspNetCore.Cors.Infrastructure.CorsService[4]
      CORS policy execution successful.
info: Microsoft.AspNetCore.Routing.EndpointMiddleware[0]
      Executing endpoint '/livesharp/negotiate'
info: Microsoft.AspNetCore.Routing.EndpointMiddleware[1]
      Executed endpoint '/livesharp/negotiate'
info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
      Request finished in 0.7047ms 200 application/json
info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
      Request starting HTTP/1.1 GET https://localhost.livesharp.net:50539/livesharp?id=7jkmk2ibqjKBLnV8kAfPhg
info: Microsoft.AspNetCore.Cors.Infrastructure.CorsService[4]
      CORS policy execution successful.
info: Microsoft.AspNetCore.Routing.EndpointMiddleware[0]
      Executing endpoint '/livesharp'
09:48:34.707: Workspace loading finished in 247ms
09:48:34.748: watcher created at C:\Git\Blazor.Ionic\Blazor.Ionic.Demo\
09:48:34.748: watcher created at C:\Git\Blazor.Ionic\Blazor.Ionic\
09:48:34.749: Starting job: Dry run for Blazor.Ionic.Demo
09:48:34.749: LiveSharp Server connected
server: 1.6.7.0
nuget: 1.6.33
09:48:36.552: Ended job: Dry run for Blazor.Ionic.Demo (1802)
    that's what I get on livesharp server after I refresh
    Mihhail Maslakov
    @ionoy
    @Kukks I'll take a look
    Wayne Hiller
    @WayneHiller
    @ionoy Yes I am using the Nullable Reference Types feature.
    Wayne Hiller
    @WayneHiller
    @vertonghenb I am having the same issue. Did you just disable Nullable Reference Types to fix it. I hate to do that because I get a lot of value from them.
    Benjamin Vertonghen
    @vertonghenb
    @WayneHiller yeah I had to disable them...
    Wayne Hiller
    @WayneHiller
    @vertonghenb Other than that issue are you finding that it works well?
    Benjamin Vertonghen
    @vertonghenb
    @WayneHiller I bought a yearly license to support the project because I can believe in it. But ATM it's pretty buggy and gives a lot false positives for Blazor (wasm + hosted). However the project is being actively maintained by the owner so I'm keeping my hopes up.
    e.g. OYIon/LiveSharp#104 is pretty annoying. for example:
    Create a new component
    Use it in another component
    Add a parameter in the child component (created in step 1.)
    Use the parameter in the parent component.
    Breaks the app and livesharp.
    But again, the potential can be huge, so yeah @ionoy has my support.
    Wayne Hiller
    @WayneHiller
    @vertonghenb It looks like a cool project and the idea is great. Unfortunately if the tool is unstable and you can't trust it 100% of the time you end up just building and refreshing anyway. Hopefully they can get some of the bigger issues ironed out. I think MS will build something at some point mostly a matter of when I think.
    Mihhail Maslakov
    @ionoy
    @vertonghenb I'll add the nullables support in the next stable version. Or I could create a build for you in the meantime
    @vertonghenb "parameter in component" is a little bit more difficult to fix because it relies on getting property via reflection. LiveSharp doesn't actually modify the type, so it's impossible to fake. But have a potential solution that just needs some time to work out.
    @WayneHiller LiveSharp is a new project so there might be rough edges. But I'm working on it daily, and it gets better with each release.
    Wayne Hiller
    @WayneHiller
    @ionoy Thats good to hear, I think it is going to be a very popular project. It you get the Nullable Ref types issue fixed I will give it another try.
    Benjamin Vertonghen
    @vertonghenb
    @ionoy any ETA for OYIon/LiveSharp#104 ? (adjusting parameters)
    Mihhail Maslakov
    @ionoy
    @vertonghenb I'd say a week or two at least. this is a considerable feature I need to implement.
    but I need it for other cases too, so it's at the top of my priority list
    @WayneHiller alright, thanks. it will probably come in the next public release
    Alberto
    @3DSX
    I have a question, I'm using Rider with a Blazor Server project and for some reason changing a text or a value does not invoke the StatusHasChanged method (I invoke anything else that causes rendering again and the update shows ofcourse). Here is the log:
    02:13:54.593: Starting job: Handling Razor update: Pages/Counter.razor
    02:13:54.702: Updating obj/Debug/net5.0/Razor/Pages/Counter.razor.g.cs
    02:13:54.731: Ended job: Handling Razor update: Pages/Counter.razor (137)
    02:13:54.736: Received C# update
    02:13:54.742: Received update for method Counter.BuildRenderTree
    I have started it on the Rider command console and after then my project, as instructions say.
    Mihhail Maslakov
    @ionoy
    @3DSX can you test it on other pages? maybe it's some specific page structure that confuses LiveSharp?
    or is it just a usual Blazor sample?