A good place to get LiveSharp support (Discord server https://discord.gg/P6g8QSnnXW)
I just bought a license, set it all up and then whoops, my app won't start
livesharp: Transport type: LiveSharp.Support.Blazor.BlazorTransport
global.js?_v=637533468755104738:52 livesharp: Blazor update handler started
global.js?_v=637533468755104738:52 livesharp: error: Failed to load assembly types from Microsoft.GeneratedCode, Version=1.0.0.0:
global.js?_v=637533468755104738:52 System.NullReferenceException: Object reference not set to an instance of an object.
global.js?_v=637533468755104738:52 at System.Reflection.Emit.AssemblyBuilder.GetModules(Boolean getResourceModules)
global.js?_v=637533468755104738:52 at System.Reflection.Assembly.GetTypes()
global.js?_v=637533468755104738:52 at System.Reflection.Assembly.get_DefinedTypes()
global.js?_v=637533468755104738:52 at LiveSharp.ServerClient.KnownTypes.LoadTypesFromAssembly(Assembly assembly)
global.js?_v=637533468755104738:52 livesharp: Initiating handshake with https://localhost.livesharp.net:50539/connect/runtime
livesharp: error: Failed to load assembly types from DynamicProxyGenAssembly2:
global.js?_v=637533468755104738:52 System.NullReferenceException: Object reference not set to an instance of an object.
global.js?_v=637533468755104738:52 at System.Reflection.Emit.AssemblyBuilder.GetModules(Boolean getResourceModules)
global.js?_v=637533468755104738:52 at System.Reflection.Assembly.GetTypes()
global.js?_v=637533468755104738:52 at System.Reflection.Assembly.get_DefinedTypes()
global.js?_v=637533468755104738:52 at LiveSharp.ServerClient.KnownTypes.LoadTypesFromAssembly(Assembly assembly)
I want to completely exclude livesharp from our release builds. I know it is possible to use a build property to disable livesharp, but I need to completely remove the references etc. I tried a condition on an ItemGroup with the references, but that is apparently not supported as the reference is still included in the build. Also tried moving the references to a .targets file with no luck. Can you advise how I can completely remove livesharp from our release builds?
@cocots:matrix.org you need to update the LiveSharp Server tool
dotnet tool update livesharp.server --global
@brokenthorn are you using the latest LiveSharp NuGet package?
@yasserss yeah, this option doesn't do anything in the new server yet since the UI is only opened once when you run
livesharp command
@rsuk you can try something like this:
<ItemGroup>
<PackageReference Include="LiveSharp" Version="2.0.13" Condition="!$(DefineConstants.Contains('LIVESHARP_DISABLE'))"/>
</ItemGroup>
<ItemGroup>
<Compile Exclude="LiveSharp.dashboard.cs" Condition="$(DefineConstants.Contains('LIVESHARP_DISABLE'))" />
</ItemGroup>
you could try
http://localhost:50540
the server is still noticing changes to the source but not updating the browser
I've installed Livesharp and started the server. The browser opens after entering livesharp in the command window, but the website does not open with the url https://localhost.livesharp.net:50539 However it is available under https://localhost:50539/ The output window of visual studio shows that it can't find the url. I'm on Windows.
you can add it to your
.hosts file as 127.0.0.1 localhost.livesharp.net if DNS doesn't resolve it automatically for some reason
otherwise it'll just update the methods and won't refresh the UI
I am using LiveSharp for Xamarin.Forms and running on an Android Simulator. I have several issues. Page level changes are not being updated. E.G. Title = "XYZ"; or BackgroundColor = Color.White; does not update without re-starting the application. Some controls changes update others do not.
Hi @ionoy I've been using LiveSharp for a few months now and we recently switched our .net 5 ASP.NET Core app from publishing directly to a network share to using Web Deploy. For some reason Livesharp breaks this method of publishing in both release and debug mode with the following error:
Error : LiveSharp exception: System.MissingMethodException: Method not found: 'Void Mono.Cecil.Cil.ILProcessor.RemoveAt(Int32)'.
at LiveSharp.Rewriters.DelegateCacheRewriter.BuildDelegateCacheInitializer(ModuleDefinition module, RuntimeMembers runtimeMembers)
at LiveSharp.Rewriters.UpdateHookRewriter.Rewrite()
at LiveSharp.Rewriters.MainAssemblyRewriter.ProcessEverything(String projectDir, String solutionPath, String projectName, String nuGetPackagePath, String projectReferences, Boolean& isNonMsBuildConfiguration, Boolean isFullRebuild)
9>Build failed. Check the Output window for more details.
Having to remove Livesharp for every deploy now is a bit fiddly
More info on my issue: If I switch to Page B page before make changes to the code on page A and then go back to Page A, Page A updates correctly including at the page level! Making it on the same page will not display the update and makes the Flyout menu choices hang. I love the product and will gladly purchase a license if these issues can be resolved. Please advise on what to try.
@Swiftless I guess Cecil gets referenced during web deploy
do you have a special configuration for Web Deploy?
you could use a conditional symbol that would disable LiveSharp just for deployment
Mihhail, thanks for the fast response. No XAML only C#. Note that it might be related to the fact that that I have a TabbedPage within a Flyout menu. If changes are made in those tabbed pages, the changes are not visible and the Flyout menu will popup but Menu selections no longer work. If tabbed page changes are made while in another page, the changes in the TabbedPages ARE updated and the menu works correctly. I would be glad to share my code with you.
@JohnHDev I think you should have received an email with the details. I think it should be something like
www.livesharp.net/my-account/
@Swiftless do you deploy Release configuration?
@ionoy I have tried both Release configuration with the conditional symbol and Debug configuration without the conditional symbol. As mentioned File Publishing was fine but something with the Web Deploy publish profile is not happy with Livesharp and I've tried multiple combinations of publish profile settings within the Web Deploy profile.