IDE :: Debug.Print Doesn't Show Anything In The Immediate Window
Dec 17, 2007
I tried using: dim x as double= 10.0 debug.print(x.tostring) in my Visual Studio 2005 program but it doesn't display anything in the immediate window. It works in my Visual Basic Express 2008 program. How can I get it to work in Visual Studio?
I have made some changes in my code but when i do debug it doesn't show the changes.For example: In my code i create a simple text file in "C" drive.I have change the path to the desktop and when i do debug it still create it in the "C" drive.
According to MS documentation The question mark (?) is an alias for Debug.Print This is clearly not 100% true, as the two statements exhibit differing behaviors in the example above. If it makes any difference, I am using the Express Edition of VB 2008.
When I add a debug.print line to my code, it doesn't send the output to the immediate window. I did a search of the forum for debug.print, and found the identical problem, but, the solution listed did not work for me. Basically it said to set the solution configuration to "Debug" as opposed to "Release".
Public Class MyCollection Inherits ObservableCollection(Of MyCollection) Private _Name As String
[code]....
EDIT: I know that I can use DebuggerDisplay, but unfortunately it is very limited. The class in reality is quite complex and I need to have the possibility to define a logic in what I show during debugging, if possible.
I have a fellow employee who is learning Visual Basic and in one of her assignments she is using the debug.writeline statement. Example: Private Sub Form1_Load(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles MyBase.Load Debug.WriteLine("This line always prints") End Sub When you run the program, nothing prints to the Output window. I have tried it in VS2008 and VS2010. Brian Allison
I have a project that the debug.print "something" function has stopped showing in the "immediate window", or any other window. This has been working fine.If I create a new project the "debug.print "something" works fine.I did have to do a uninstall/reinstall of VS 2010 yesterday maybe something changed.Is there a setting that tells "debug.print" where to print?
I have attached my project. I have made a web browser I don't get any errors but it doesn't run/debug.I don't know why but i checked everything. If somebody could tell me what's wrong with my project it would be awesomeBill Wiz, on 17 June 2012 - 12:30 PM, said:I have made a web browser I don't get any errors but it doesn't run/debug.[url]...
And here I am with a new problem in my program When I debug it everything works fine (the buttons, progressbars, pinger, spambot,When I compile it and run the Executable file, it works too.When I run the Executable file on another computer (tried on 4 different ones) the program stops working and I get this error: {$ exception. "Failed to create the form For more information, see Exception.InnerException error: File or assembly \." Microsoft.VisualBasic.PowerPacks, Version = 9.0.0.0, Culture = neutral, PublicKeyToken = b03f5f7f11d50a3a \ "or one of its dependencies not found. The system can not find the file specified .."} System.Exception {System.InvalidOperationException}
I am developing an application using Visual Basic .NET 2005. The application works fine in the PC which Im using to develop it. I make the setup.exe I install the application in other PC and the application doesnt work but it I replace the app.exe with the one in my debug folder it will work.
I opened an older project and it works fine. Using syntax: debug.print ("OK") and look for printed line in immediate window. Is there some setting I could have inadvertently disabled or have maybe discluded some imports? Only import is forms.
Follow up to Direct access to full string representation of object.
I am trying to log the contents of an object to a text file. I can get the property-value pairs I want to log by executing this line in the immediate window[code]...
I was running Visual Studio 2008 on my computer went through a whole VB progamming course with no problems. I recently had to have my computer hard drive erased and reloaded with windows xp to eliminate a virus. When I got it from the shop Visual Studio 2008 had not been backed up so I reinstalled the Professional edition from my disc. I opted fo the recommended installation. Every thing seems Ok except when I put a debug.Writelie (" Hello"} in the code nothing appears in the immediate window when it is executed. If I go to the immediate window and type the same line and hit return the string appears in the immediate window. If I assign a value to a variable in the program and put the debug.writeline command in the code module nothing appears in the immediate window, but if I go to the immediate window and type debug. writeline (var) and hit return the value of var apppears in the immediate window. i went to the debug menu and selected windows then clicked on immediate but it didn't highlight or show check mark. When the project builds after start debugging the immediate window appears. In the help it talks about a trace listener and insertig a line of code in the compile command line.
I am trying to list all the current threads that are running in my application. According to various posts, this can be simply done by selecting Debug -> Windows -> Threads however the threads window is not there. I am using Visual Basic Express .net 2010, am I doing something wrong, or is it not implemented in this version ?
If it is not implemented, is there a simple way to display all the threads that are running. I don't want lots details about them, just what they are ?
I am using Visual Studio 2010 Professional in trial mode... and suddenly the Output window won't show my Debug.Write() stuff. It had been showing it for the past month.I have been using the 2010 version for 30 days (after upgrading from Visual Studio 2003) in trial mode. I just renewed the trial for the extra 60 days, and the "About Visual Studio" window says I still have 59 days left.
I have verified that the application is running properly, without errors. When I purposely generate an error, the Output Window properly shows the error and the stack trace I've already checked my Build>Configuration... it's in "Debug" mode, not "Release". The Debug.Write() text is not going to the Immediate window, either.One other point, I tried running the same application in the Visual Studio 2010 Express Edition, and it complained that it could not debug the specified code, though it did properly build it so that it would run in the build. Could Visual Studio 2010 Express have modified something in my project files to disable the debugging output?
I have the Immediate window option available in my menu, but when I click it or do the keyboard shortcut, nothing happens. It's quite difficult to debug an application without an Immediate window.I've tried resetting my settings to general developer and all of the other suggestions I found on the web, but still, no immediate window shows up when I click it or do the keyboard shortcuts..
Since reinstalling VS2010, it has not been displaying proper debug info. I don't think I changed any settings but I have had a hunt through the options and can't see anything I might have messed up. I have had a quikck search and other people seem to have had the same problem but no solution. I'm running Windows 7 x64 with latest updates, if that matters.
Private Sub BugReportsCentral_Load(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles MyBase.Load WebBrowser2.Navigate("http://xxxxxxxxxxx.net/update/link/on-off/threadreport.html")
[code]...
Why this code doesn't work? It doesn't print the label with the correct thing.
I'm still somewhat new to visual basic and programming in general (started teaching myself in December so I could learn how to program), and up till now I've been very successful at troubleshooting my more difficult problems with liberal use of google and forum-browsing. However, this is the first problem I've had that I can't find mentioned anywhere else.In the design view, my form looks perfectly fine. But for some reason—somehow—at runtime the form doesn't line up properly in its window (white space between the border and the grey area where the background begins). I haven't altered the size programmatically, nor have I changed any settings (as far as I know) that weren't changed in other forms as well (this is the only one that's messed up).
I should also mention that I don't have any code that interacts with the form's own design code or events, except for the Load event (where I assign values to three tooltips).
Form in design mode Form at runtime
The only clues I've gotten to what may be the issue are that if I try to resize the window with the mouse (at runtime), the pointer gets stuck resizing (it can't "let go" of the window). The other clue is that if I click on the white part itself, I'm able to drag the window around (like I were clicking the bar at the top of the window, that I just realized I don't know the name of, which is kind of embarrassing...). Other than that, everything in the form works as it should (including the three half-buttons).
I'm trying to put data in my listview but the data doesn't show in my listview.
When i put this code in my form i dont have any problem but when i put this inside the module the data doesn't show up.
Code: Public Sub getEmployee(ByVal myConnString As String) Dim mySelectQuery As String = "SELECT names FROM employee ORDER BY ID ASC" Dim myConnection As New MySqlConnection(myConnString)