Hi,
just downloaded the Trial and I can't make AppMap work in my VS. When I select new Project => App Map, it shows me the dependency container and platform selection dialog from prism. I kept default selection (Android iOS and UWP, DryIOC, show App map selected) and clicked next.
After that the UI Designer of AppMap is presented.
As soon as I drag any Page from the Toolbox into the design screen, my visual studio instance crashes.
The same thing happens when I deselect "Show app map" on project creation. I added app map Item manually to the project after creation. Then it crashes as well when I drag Page from Toolbox.
Attached ActivityLog from Visual Studio if that helps.
Thanks, Nicolai
ActivityLog.xml
I am unable to duplicate this issue locally. You can try to uninstall the extension and reinstall it from the marketplace. Sometimes when Visual Studio performs an update, it causes issues with the installed extensions.
I am having this exact issue, however, re-installing the extension did not work for me. Running Windows 10 ver. 1909, Infragistics 19.1, Visual Studio Professional 2019 Version 16.4.5. I have also run the Repair installation on both Visual Studio and Infragistics. Event Viewer indicates a Null Reference Exception
Application: devenv.exeFramework Version: v4.0.30319Description: The process was terminated due to an unhandled exception.Exception Info: System.NullReferenceException at System.Windows.Controls.Primitives.Popup.OnWindowResize(System.Object, System.Windows.AutoResizedEventArgs) at System.Windows.Interop.HwndSource.Resize(System.Windows.Size) at System.Windows.Interop.HwndSource.OnLayoutUpdated(System.Object, System.EventArgs) at System.Windows.ContextLayoutManager.fireLayoutUpdateEvent() at System.Windows.ContextLayoutManager.UpdateLayout() at System.Windows.ContextLayoutManager.UpdateLayoutCallback(System.Object) at System.Windows.Media.MediaContext+InvokeOnRenderCallback.DoWork() at System.Windows.Media.MediaContext.FireInvokeOnRenderCallbacks() at System.Windows.Media.MediaContext.RenderMessageHandlerCore(System.Object) at System.Windows.Media.MediaContext.RenderMessageHandler(System.Object) at System.Windows.Media.MediaContext.Resize(System.Windows.Media.ICompositionTarget) at System.Windows.Interop.HwndTarget.OnResize() at System.Windows.Interop.HwndTarget.HandleMessage(MS.Internal.Interop.WindowMessage, IntPtr, IntPtr) at System.Windows.Interop.HwndSource.HwndTargetFilterMessage(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef) at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef) at MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object) at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32) at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate) at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32) at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr) at MS.Win32.UnsafeNativeMethods.CallWindowProc(IntPtr, IntPtr, Int32, IntPtr, IntPtr) at MS.Win32.HwndSubclass.DefWndProcWrapper(IntPtr, Int32, IntPtr, IntPtr) at MS.Win32.UnsafeNativeMethods.CallWindowProc(IntPtr, IntPtr, Int32, IntPtr, IntPtr) at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)
Any other suggestions?
Make sure you are using the most recent version of the AppMap. What stands out to me is that nothing in that call stack is pointing to the AppMap code. I have seen one other report of VS crashing when something is dragged onto the design surface that could not be tracked down to a single line of code in the AppMap wizard. When does the exception occur for you?
We think we found the issue. It seems related to an update in Visual Studio. Please try version 2.0.18 from the marketplace and let me know if it works for you.
Thank you for the update. Since it is working on another version of VS for you, this makes the problem even more strange. Let me know if you are able to find anything. I am still unable to reproduce it on any machine or VM. SO it must be something specific to a VS install.
The exception occurs when I drag onto the design surface - i.e Visual Studio crashes and the exception shows up in the event log. I have another machine where AppMap works fine, so maybe I can narrow down what is causing the issue.