Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Andrew Camilleri
    @Kukks
    let me do super clean by deleting bin/obj
    Andrew Camilleri
    @Kukks
    nope still the same
    Mihhail Maslakov
    @ionoy
    @Kukks this is a weird issue, I also see it sporadically. try this build
    LiveSharp.2.0.27.nupkg
    Paramjit Singh
    @HobDev
    LiveSharp is not working on VisualStudio 2022 preview with dotnet maui
    Tony
    @WithAnOrchid
    The document states "Install the LiveSharp NuGet package into the project where you need the hot-reload functionality.",
    but when I start my app, Livesharp gives "Program does not contain a static 'Main' method suitable for an entry point", could anyone help please?
    My app has 2 projects, A for the UI form(winform), B for the logic. When A started, it calls methods in B.
    I installed Livesharp to both the projects, debugging A (the UI form) is totally fine, but any change in B triggers the above error
    Tony
    @WithAnOrchid
    ^ fixed by adding a dummy public static void Main()
    Paul Charlton
    @paul-charlton
    @ionoy - any chance of getting the latest up on nuget? the local one keeps playing hell with my build process :(
    Paramjit Singh
    @HobDev
    How to cancel the subscription
    Mihhail Maslakov
    @ionoy
    @paul-charlton I have published the latest build to NuGet
    Paul Charlton
    @paul-charlton
    Thank you
    ukappmasters
    @ukappmasters
    Hello, using .net 6, Blazor and the lastes NuGet I get the following starting my app now.
    Assertion: should not be reached at /w/1/s/src/mono/mono/mini/../sgen/sgen-scan-object.h:91
    GlobalFunctions.js:160* Assertion: should not be reached at /    w/1/s/src/mono/mono/mini/../sgen/sgen-scan-object.h:91
    dotnet.…0.3.0ydvpfptwr.js:1/__w/1/s/src/mono/mono/sgen/sgen-gc.c:3993 <disabled>
    MarkoK
    @mapkokam
    hey @ionoy , i have the same "error CS0229: Ambiguity between" as @Kukks had. Is there any official advice what to do in this case? Nothing seems to help, including cleaning the solution by deleting all bin/obj folders in all projects.
    using all latest builds
    MarkoK
    @mapkokam
    and i also get this one 
    1>AspectInjector|2.7.2 : error AI_ERR0: Processing failure: Mono.Cecil.Cil.SymbolsNotMatchingException: Symbols were found but are not matching the assembly
1>   at Mono.Cecil.ModuleDefinition.ReadSymbols(ISymbolReader reader, Boolean throwIfSymbolsAreNotMaching)
1>   at Mono.Cecil.ModuleReader.ReadSymbols(ModuleDefinition module, ReaderParameters parameters)
1>   at Mono.Cecil.ModuleReader.CreateModule(Image image, ReaderParameters parameters)
1>   at Mono.Cecil.ModuleDefinition.ReadModule(Disposable`1 stream, String fileName, ReaderParameters parameters)
1>   at Mono.Cecil.ModuleDefinition.ReadModule(String fileName, ReaderParameters parameters)
1>   at Mono.Cecil.BaseAssemblyResolver.SearchDirectory(AssemblyNameReference name, IEnumerable`1 directories, ReaderParameters parameters)
1>   at Mono.Cecil.BaseAssemblyResolver.Resolve(AssemblyNameReference name, ReaderParameters parameters)
1>   at FluentIL.Resolvers.KnownReferencesAssemblyResolver.LookupAssembly(AssemblyNameReference name, ReaderParameters parameters)
1>   at FluentIL.Resolvers.CachedAssemblyResolver.Resolve(AssemblyNameReference name, ReaderParameters parameters)
1>   at FluentIL.PatcherBase.ReadAssembly(String assemblyFile, IAssemblyResolver resolver, Boolean readSymbols, Boolean verbose)
1>   at FluentIL.PatcherBase.Process(String assemblyFile, IAssemblyResolver resolver, Boolean optimize, Boolean verbose)
1>   at FluentIL.PatcherBase.Process(String assemblyFile, IReadOnlyList`1 references, Boolean optimize, Boolean verbose)
1>   at AspectInjector.Compiler.Execute(String filename, IReadOnlyList`1 references, Boolean optimize, Boolean verbose). Please submit an issue to https://github.com/pamidur/aspect-injector
1>AspectInjector : error AI_FAIL: Aspect Injector processing has failed. See other errors.
    it is a .NET6 project, running both as WebAssembly and server mode. The odd thing is that hot reload actually worked the first time i've ran it. From then on it either hits above AspectInjector error after Ctrl+F5 or it goes crazy with "Ambiguity between". :)
    MarkoK
    @mapkokam
    what i did notice is that the "watcher created at" is displayed multiple times for each project. And the first error in the console is this:
    Microsoft.NET.Sdk.Razor.SourceGenerators\Microsoft.NET.Sdk.Razor.SourceGenerators.RazorSourceGenerator\Pages_Error_razor.g.cs(16,33): error CS0111: Type 'Error' already defines a member called 'BuildRenderTree' with the same parameter types
    MarkoK
    @mapkokam
    good news, version 2.0.25 works fine
    William Obando
    @wocar
        <PackageReference Include="LiveSharp" Version="2.0.28" />
    Not working
    .net 6
    server side
    have the same "error CS0229: Ambiguity between"
    Mihhail Maslakov
    @ionoy
    @mapkokam @wocar Working on it guys, sorry for the delay. I'm in a bit of a crunch at the moment, that's why it takes longer. I expect to have more time for it soon.
    mytrix
    @mytrix
    Hi @ionoy, can I ask you, if there are some code length limits? I have the project where Livesharp throws exception during startup "System.StackOverflowException: 'Exception_WasThrown'". This error throws app.UseDefaultBlazorHandler(); in LiveSharpDashboard.
    When I tried remove some random parts of code from the project, the error is gone.
    An unhandled exception of type 'System.StackOverflowException' occurred in System.Private.CoreLib.dll
    mytrix
    @mytrix
    System.StackOverflowException
    HResult=0x800703E9
    Message=Exception_WasThrown
    image.png
    Unfortunately, any other details are not available. Thank you.
    mytrix
    @mytrix
    And I'm nearly sure, that some issue was reported by @yyw10242 on 7th September, 2021.
    Jared Schnelle
    @jaredschnelle
    @ionoy I have a problem that I've resolved, but want to know more. I updated NuGet package from 2.0.24 to 2.0.28 and the hot-reload for Blazor stopped working. I got a lot of errors in console about how a method for XYZ already existed. Downgrading to .24 resolved errors. Did I make a mistake in not also updating the Server package or something? I can give you more info, but I wonder if I missed something basic here.
    Mihhail Maslakov
    @ionoy
    @mytrix I don't think I can fix that without a sample project. This stuff happened a few times before but it's probably a new issue now.
    @jaredschnelle I've updated Roslyn dependencies in the latest build. Something must have changed that causes razor files to generate code. I didn't have enough time to figure it out yet.
    Mihhail Maslakov
    @ionoy
    @/all Since there is now a built-in hot reload in .NET, there is no point in trying to sell LiveSharp anymore. I decided to make LiveSharp free and open source. More information here: https://livesharp.net/news/
    Lyndon Hughey
    @lhughey
    @ionoy Thank you for the incredible work you've done with LiveXaml and LiveSharp over the last 4-5 years. Your products were instrumental in keeping me in the Xamarin space. Thank you for open sourcing the codebase.
    Marco Milani
    @markjackmilian
    livesharp stopped working for me after the last release, has this happened to others?
    Mihhail Maslakov
    @ionoy
    Thanks for all the support @lhughey !
    William Obando
    @wocar
    @ionoy Thank you very much!

    @ionoy Thank you for the incredible work you've done with LiveXaml and LiveSharp over the last 4-5 years. Your products were instrumental in keeping me in the Xamarin space. Thank you for open sourcing the codebase.

    Same for me

    livesharp is my last hope here, im developing on mac... so microsoft hotreload is broken.
    William Obando
    @wocar
    Reverted to <PackageReference Include="LiveSharp" Version="2.0.24" />
    And now it works, im so excited hehe thank you!!!
    William Obando
    @wocar

    Sometimes I'm just getting the error:

    04:51:14.840: error CS5001: Program does not contain a static 'Main' method suitable for an entry point

    I think it might be because of the async task on main:

        public static async Task Main(string[] args)
    The work around was:
        public static void Main(string[] args)
    {
        Task.Run(async () =>
    I don't know if it is that easy to patch, if you point me in a direction i can submit a PR
    <3
    William Obando
    @wocar
    ionoy/LiveSharp#2