I have a very basic Visual Basic Program that I created in Visual Studio 2010. It's a form application where clicking a button runs a simple calculation and then outputs the answer with MsgBox. When, I debug it works properly, however when I successfully build and run the exe, nothing happens. What could be going on here?
Are you doing anything like this?
Debug.Print(MsgBox("Your answer is 7. Try again?", vbYesNo))
In other words, are you making use of a library that is only available to a debugging session (in this case, System.Diagnostics).
Related
I'm writing a VB program where I want to be able to "push" an Exit button with a keyboard shortcut to close the program. I understand that if I put an & in the text of the button (E&xit), I can create a Alt-X shortcut to exit.
I've written programs where it's worked before; it's simple, but now it's not working. In fact, it's not even underlining the x in the text on the button. It's like a setting is telling it to be ignored. (I'm using the latest version of MS Visual Studio.)
I have found that if I turn on the form setting KeyPreview=True, it will work, but the x is still not underlined, so there is no visual indication of the shortcut being available. I feel like I'm missing some setting or switch that make this activate normally. Can someone explain or point me in the right direction? Thanks.
jmcilhinney, well, now it's working, both on new and existing apps, even with keypreview turned off. I think there was something strange going on with Visual Studio that day. Other parts of my program (with KeyPress handling) were not working correctly either at that time. Then suddenly everything started to behave as expected. Or maybe it was something I was doing with Keypress that messed up the Access Keys. I wish I could explain better, but now I can't reproduce the problem.
Why does my VB.Net Project disappear instead of giving an error message?
This only started happening recently, but when debugging with Visual Studios instead of getting errors, the program just closes as though the stop button was pressed. This doesn’t happen for all error types but it consistently happens if there is some sort of casting error.
This is an overly simplified example, but the lines below would cause a program to vanish as soon as they run.
Dim i As Integer
i = "A"
One other interesting part of this is that if that was in a try catch block the error would be caught instead of closing the program.
I’m in an office setting so I’ve been able to test a number of configurations and have found that this problem only affects Windows XP PCs, but not Windows 7. And it consistently happens with Visual Studios 2010 Professional and Ultimate, Visual Studios 2008.
Anybody have any ideas? Besides that we apparently we all need Windows 7.
The Visual Studio Cant expect error of casting first of all he have to underline your error. Then you have to correct it before debugging.
Your VS shows you the red underline in errors or not ??
And if the VS shows you that errors exist when you debug ?
We're using Reportviewer and rdlc files in our application. I had drillthroughs working fine and we put the app on the backburner to work on other projects. Now that the Users wanted a new build I revisited the app and tested with a new password in the connection string. To my surprise the Drillthroughs no longer work. To my further surprise I can't even click on the textbox that fires the drillthrough. I checked TFS and there have been no changes to the Report definition or the ViewModel that handles the Drillthrough. All I changed were the connection strings.
If anyone can point me in the right direction on how to figure this one out I'll be very happy.
I figured this out if anyone else is interested. I installed Visual Studio SP1 which apparently causes a few issues with ReportViewer.
Hi we have had the same problem and finally found a hotfix which works. You only need to download the file VS10SP1-KB2549864-x86.exe . Install and try again. Should work.
http://connect.microsoft.com/VisualStudio/Downloads/DownloadDetails.aspx?DownloadID=37409
I am having a weird issue with VS 2008 when I go to debug my program. When I click on the play button to run the program it flashes real quick and goes back to the VB IDE. No matter how many times I click on the play button it continually flashes and then goes back without displaying my form window or anything.
What type of setting would I need to change in order to correct this issue? I've been through most settings in the "my project" section and i do not see anything that could be causing it to do something like this.
My older vb apps I've made seem to work just fine when I click the play button on them. Only noticed this problem whenever I go and make a new vb app.
update video of what's going on
http://tinypic.com/r/2eycaas/7
Try this?
"
Did we install some third party Add-ins in your machine? If we disable Add-ins (“Tools” | “Add-in Manager”) and run “devenv.exe /safemode”, do we still have the problem? This can eliminate the possibility that third party Add-ins are causing problems.
We also can try to run devenv /resetsettings (Commonly, it makes sense than re-installation) or devenv /setup in Visual Studio Command Prompt.
"
--http://forums.asp.net/t/1324737.aspx/1
Just check your output window.
Accessible from Menu-> Debug-> Windows -> Output. (Check image:1)
In output window select Show output from: Build combobox. (Check image:2)
This will give you perfect idea what is happening.
Following are the guesses.
The VBC installer is not installed or corrupted.
Some addon is registered to run before compiling and is creating problem.
....Long list until you tell whats shown in output window.
Also check Show output from: Debug in output window and Final check would be Immediate window.
I feel this three would give you hint whats going wrong.
Fixed.
Changing it to x86 instead of Any CPU worked!!!! :) But question is, why me having an Core i7 Quad doesn't support the program when i choose x64.....
David
Is the startup form correct? You can see that in project properties.
I'm buisy on a DirectX10 game engine and i'm having a problem which has nothing to do with DirectX :P The problem is that in the DLL which contains the engine sometimes a DialogBox is called, just like you would do in normal win32. With the only difference that instead of the HINSTANCE i use the HMODULE which i get when loading the DLL.
Everything seems to be working fine, if i step through my code with F10 (Visual C++ 2008) i can even see it going through my DlgMessageProc function and do everything it should do. The only weird thing is that no dialog is shown and that all of a sudden it jumps out of the message loop and just continues with the rest of the code???
Weirly engough I have the same problem when calling MessageBox from inside my DLL, I get no errors, everything seems to be working fine but no window is shown, nor is the code halted (as normal with messageboxes)
The funny thing is that I have some code from a book which uses the same basic architecture as me and if i compile that everything shows just fine??
So my question, is there any hidden option, pragama comment or other thing i should look at if i want to be able to show MessageBoxes and Dialogs from my Dll?
No as i thought, chaning the manifest doesn't help at all. I also created a separate project where i just test the dialog and its proc function and there everything works perfect (links to a .exe instead of dll)
In the visual studio resource editor's property page for the dialog resource there should be an option in which you can specify - "No Fail Create: True".
Usually dialogs fail to create because a common control cannot be created - usually because InitCommonControlsEx has not been called. Setting the No Fail Create flag lets you see dialog and determine which controls are missing.
Other things to check:
Is there a message in the debug window about a first chance exception? Perhaps its 'jumping out' because of an exception that is being caught and silently handled by Win32. Turn on debugging of first chance win32 exceptions in the Dev Studio exceptions dialog to track that down.
Even this wouldn't explain how a MessageBox call would fail to create a message box.
The only times Ive seen MessageBox fail to work were when:
Resource leaks had made the process run out of available user32 handles - have you checked your apps handle counts using task manager?
the system was in the process of being shut down. Have you called PostQuitMessage and then tried to create a dialog/MessageBox?