I am running Intellitrace inside a Cloud Services instance. I have done so for a year or two and love it. I have done various updates including Windows from 8 - 10, Visual Studio to 2015 and its behaviour has changed and I don't know why.
One of the main benefits of it once you have pulled your historic data from Cloud Services you could double click on the error and it would take you to the code line which generated it.
In this case a Null Reference exception. It now opens up a diagsession with the exception in the Calls list but I can't dig any further.
By Calls list, do you mean the event table in diagsession. Please look at the screenshot at (in Events details section) https://blogs.msdn.microsoft.com/visualstudioalm/2015/01/16/intellitrace-in-visual-studio-ultimate-2015/
If so, you can
1. Double click the row with NullReferenceException thrown event.
or 2. Click the row with NullReferenceException thrown event. Then click "Activate Historical Debugging" hyperlink. Both take you to historical debugging mode.
The UI has changed. It used to take you to historical debugging mode when you just click the row in the IntelliTrace window. Now you have to do either one of the above action.
Keep in mind that if it doesn't find the symbol and source file, it won't take you to the code line.
Related
I have a setup created that installs an application, and still does, but it started giving a strange warning at the end out of the blue. So, when the installation process finishes, the following appears:
The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2810.
So I checked 2810, and it says:
On the dialog [2] the next control pointers do not form a cycle. There is a pointer from both [3] and [5] to [4].
I was not changing anything in the "User interface" or "Custom actions" so this came unexpected. Also the installation completes if you just click ok and everything works fine, it just doesn't look good from a user perspective. Any help or similar issues encountered?
Control_Next: This is probably just the tab-order for the controls on the dialog. See the Control_Next column of the Control Table. You need to find a way to visit each control of the dialog in sequence and sort out so there are no loops or double links.
TAB Order: In the dialog in question (launch the setup and get yourself to the FinishedForm dialog), try hitting TAB repeatedly to see what happens. It might work, but you might see the control order being messed up so TAB unexpectedly moves around the dialog haphazardly going in "reverse" selecting a control already visited or similar.
Fix: Fixing this depends on what tool you are using. You can "test fix" directly in the final MSI using ORCA or a similar tool to edit the Control Table directly (just open the MSI and do it). The real, lasting fix will be in the sources used to compile the setup. WiX, Installshield, Advanced Installer, Visual Studio Installer, or whatever tool you are using. Exact fix depends on tool. A screen shot of the Control Table content could give us the clue we need.
(combining comments into an actual solution)
If you're using the common script EnableLaunchApplication.js within a Visual Studio Installer project, then the 2810 error code is most likely caused by a single line within that script, along with a recent Visual Studio update.
The fix, as mentioned by user Olaf:
in the EnableLaunchApplication.js I changed the line INSERT INTO 'Control' ... and replaced the value 'CloseButton' with 'Line1'. – Olaf Jan 9 at 14:16
With the entire corrected script linked by user Shangwu:
Here is the latest JavaScript without causing error 2810. stackoverflow.com/a/59888956/6079057 – Shangwu Jan 24 at 0:49
The underlying reason can be found in answers by Adam cosby and Stein Åsmul.
I actually had the same problem and my Control Table was over populated just as you mentioned above. I beleive it was related or at least co-incided with the Visual Studio update from 16.3 to 16.4.2. For me I used the Visual Studio Installer too and on the older version of VS it compiles fine but the same commit number on a different machine with the new version it causes the same issue and the Control Table has a lot more Control_Next entries populated. Still not sure how to fix yet though in the source.
Edit:
Ok I discovered the problem. The issue with it now populating more of the Control_Next I can only put down to a the update. However, the automatic entries put in by Visual Studio would have been fine but I realised we had the MSI launch the exe after install using this: Visual Studio Installer > How To Launch App at End of Installer technique.
That meant I was injecting and modifying the Control_Next and thus caused the loop of Control_Next to be non circular. It is worth noting that the Control_Next is basically the tab order of the MSI screen and it must always be closed (imagine the tab without anywhere to go).. Anyway, it was ultimately caused by us modifying on the post build process the Control_Next to add in the checkbox. After working out the last entry on a build without our code running i just modified the original last entry and then slotted in out one there. Now it works fine.
Hope this helps
Essentially, I encounter the same problem as the question below, except that the accepted answer does not resolve it. I have neither warnings nor errors in the Error List:
See complete tooltip error message for Data Flow SSIS element in Visual Studio
Similar to the question noted above I can see a truncated warning message on the Data Flow design surface.
However, no corresponding warning is visible in Visual Studio's Error List view.
How can I view the entire warning?
This is a bit misleading from Visual Studio and could have been handled better. The long and the short of it is that the Error List window lists only messages that are related to build issues.
The warnings and errors that you see in design time are related to the execution flow. In other words, a package can be built correctly but is designed in such a way that it will generate an error. For more reading:
MSDN: Cannot see errors or warnings in SSIS - why ?
SQLServerCentral: Cannot see errors or warnings in SSIS – why ?
You will need to run the package in debug mode and then go to the Progress window. From there, you can see all messages (e.g., information, warnings, errors, etc.). Some messages may be so long that they cannot be seen. For those messages, you can click on them and paste them into your favorite text editor.
Note: when you stop debugging, the Progress window changes its name to Execution Results and the error List window becomes available.
Update
Per Hadi's follow-up comment, I was initially able to re-create the OPs problem by just modifying an existing package to create the warning message. I then built and ran the project with without receiving any error messages.
Now, after having left the office and shutting down Visual Studio, I am unable to recreate the error. The Error List window now populates with the messages. I tried building a new package from scratch without any luck either. My best recommendation at this point would be to, as with all Microsoft products, restart the application if it is not working as it should be.
This text truncation issue/bug is not just tooltips.
It's in SSIS Toolbox (description box at bottom) - no way to see the entire text describing the task/component (if not too big you can increase the width of the pane but that is not really acceptable).
(VS/SSDT 2019)
Many things to try
Try to change the combobox selected value from Build + Intellisense to Build only
Open and close the OLEDB Source by double clicking on it, since you tried to build the package the warnings disappears from the Error List, you must revalidate the component to show them
Try to update the Visual Studio 2017 to the latest release
I've been working on a C# project and I don't know the program flow. I want to know all the executing codes in a particular flow. I can press the pause button to check current executing code, but to check entire flow, I need to keep on pressing F11 or next line, which is cumbersome. BTW, I got it from here
Find out what line of code my app is currently running in Visual Studio's debug mode
I would like to know is there any way in visual studio to check currently executing code without pausing or placing break points?
I often use the VS debugging breakpoint or debug menu options like "Step Into/Out" or use the pausing button.
But if you don't want to use them, the Runtime Flow tool is a workaround I know which can help you see code that is executed:
Find out which line will be executed in Visual Studio debug mode
A feature request for VS IDE:
https://visualstudio.uservoice.com/forums/121579-visual-studio-ide/suggestions/17332198-is-there-any-way-to-check-currently-executing-code
In VS2017, debug has a new feature called "Run execution to here", I know that it doesn't really meet your requirement, but it is a better workaround if you don't want to step Into debugging one step by one step. Move your mouse to the icon and click the button, now your code will run and stop on that line the next time it is hit in your code path.
If you want this ability at debug time then consider IntelliTrace
ReSharper has a Call Tracking feature that can display incoming and outgoing calls sequenced in an interactive, graphical tree view.
See if this helps.
The issue here is that there is code running but you don't know where and you want to see what is going on. A good example is the code is stuck in a loop somewhere but you don't know where.
To break-into the running code:
Option 1: Select the 'Debug' menu item, and then select the 'Break All' menu item.
Option 2: Press keys Ctrl+Alt+Break.
This will break into the code where it is executing and you will step into debugging just as if you hit a breakpoint.
Happy debugging!
I have an F# program in Visual Studio 2013 that creates an object at the very beginning. I want to debug the code and look at the value of this object at many different points in time. I was previously able to do this by mousing over the variable in debug mode, but for some reason, I'm no longer able to do that. When I add a watch, it gives me the error:
The value for this item is stale due to a problem that occurred while evaluating it. Hover your cursor over the refresh button for details.
Old Value: The name 'MyData' does not exist in the current context.
Then hovering over the refresh button:
The value of this expression may be incorrect. It could not be evaluated because: 'The name 'MyData' does not exist in the current context' Click this button to attempt reevaluation now.
What is even stranger is that I know the variable works because it gets passed as a parameter to other external functions, and I can see all the values in those secondary functions, but not in the global scope! Does anyone know what is going on?
Go to the properties of the project and uncheck "Optimize code". Rebuild your code. If the problem persists, restart Visual Studio.
I frequently use Debug -> Exceptions -> check CLR Exceptions during debugging sessions. Sometimes, an exception gets thrown and handled, but I really want to find the source of the exception. In order to do this without seeing first-chance exceptions that I don't care about, I start my app, and then check CLR Exceptions:
This gets really tedious, and I'd love to have a toggle button in my VS2010 toolbar that allows me to only set/reset CLR Exceptions at will, without having to key in CTRL+D, E, check the box, and then click OK (and then do the same process again to turn off the exceptions). I went into the toolbar customization, but all I could get was a button that bring up the Exceptions dialog. This is obviously less efficient than hitting CTRL+D, E.
Does anyone know of another way to add this? Will it require a VS addin? A keystroke mapping would be nice as well.
I've never used the Macro Recorder in VS ever, but maybe this is one place where it's necessary?
Yes.
Use the macro recorder to record the steps.
Rename the macro to something mnemonic.
go to (tools)(customize)
at the bottom there is a keyboard button you can use to map that macro to a key or
the commands tab will allow you to (add command) to any specific menu or tool bar.