C# - Application Locks Up When It Should Get A Runtime Error During Debug?
Dec 18, 2009
I develop windows applications in VB.NET using Visual Studio 2008. Recently I reloaded my pc and moved from XP to Windows 7 64 bit. Now when I am debugging, when I should get a runtime error, the executable instead locks up when it should bring up the code with the line that it crashed on like you'd expect in debug.
This doesn't happen all the time, only when I get a runtime error in a separate assembly that is not in the assembly I'm debugging. It used to work fine, but now it locks up. If I run the executable outside of Visual Studio (without debug) I at least get a runtime error like you'd hope for. I don't even get that when debugging.
I have a Visual Basic 2005 program which runs fine if I execute the built Executable. However if I start the application in VS2005 debugger it gives a weird error
I want to update my database using formatsqlparam, but when I debug it, it has an error saying:"Incorrect syntax near ','."[code]I am missing some syntax, but I couldn't find where it is.
I have a Windows Forms application created in VS2005 which runs fine on the user desktop but when running in Terminal Server session it frequently locks up when the remote desktop window is minimised and the user is working locally.There is plenty of RAM on the server so this is not an issue, the only solution so far has been to force the user session to log off on the Terminal Server and then reconnect.
I have a quite simple application that is having some random locks up. It's just a few text fields that the user fill it up, 3 sets of Radio buttons, one of them with flags to chose the language and click the PDF button. The application uses iTextsharp to load a PDf template, insert the text into it, depending on the language loads some extra text from a .xml file, and depending on the radio button removes the images from the PDF, closes the pdfstamper and uses [Code] to open the file with whatever PDF application the user have installed and closes itself.
Sounds simple, but after the application is installed in the machine (never in debugging mode) it randomly locks up the application. I tried re-publish the application commenting out the Start(filename) line and the thing stopped locking. And I double checked it, re-publish with the line again and it locked after just a few attempts. [Code]
I'm have a quite big application which have 2 serial ports and access 1 DB (running on Background workers). I'm experiencing some random locks while the application is running and I started looking for something that could cause it. One of the obvious possibilities would be if I had in the GUI thread some While_End that would never return.I have one While_End in my GUI thread but IMHO it does not look like it would lock, so I want your opinion: Does the code below looks like will lock?? If 'yes', Why ?
[code]...
Does anyone can imagine a scenario where this While_End would not return ?
I have a do until loop. But whenever my program get's to it, it always locks the application so I can't click on anything until the loop is finished. How do I fix this? I want to be able to stop the loop with a stop button.
I'm using the SDK that my laptop's touchpad manufacturer, Synaptics, provides in order to extend the touchpad's functionality. In the SDK, there's a file named SynCtrl.dll, which contains a few ActiveX controls.Based on what I learned from the samples provided in the SDK (which are VB 5 old and don't compile), I wrote this little application:
I'm using VB 2010, and am trying to add a simple TTS function to my program. I'm able to create a voice object, and get it to speak (Voice.Speak("whatever") with no difficulty.
The problem I'm having is that while the "whatever" is actually being spoken, the program doesn't seem to respond to input. The input does show up once the audio is through, but I really need to be able to detect some input (say, a mouse or button click) during a message and respond immediately, perhaps even stopping the audio.
I have a solution in VS 2008 that creates a DLL. I then use that DLL in another application. If I go in to the DLL projects property pages and change the following configuration for a DEBUG build then the built dll no long provides the desired functionality. If I change it back and rebuild the DLL, then the DLL does provide the correct functionality:
When I debug this project, I receive the following error:"Arguments are of the wrong type, are out of acceptable range, or are in conflict with one another." It happens on the recordset open call.
rsData.Open "SELECT * FROM " & TempTableName & " WHERE 1 = 2", SQLConn, adOpenDynamic, adLockBatchOptimistic
The odd thing is that it only happens during debug. When I compile the .dll and use it, no error.I need to debug to filter review some data that is rejected in a later procedure.
Private Function CopyData _ (ByRef SQLConn As ADODB.Connection, _ ByRef SourceData As ADODB.Recordset, _
I've made some application in VB.NET 2005 and it works fine.I sent this application to the custemer and he is getting the following error at the application startup: "An unexpected error has occured. Would you like to restart the application?".
This guy is using Windows Vista. I've tested this application on several Vista machines and it works fine.
Do you have any idea how to debug it? Of course this guy doesn't have Visual Studio.
i've been making a tabbed web browser but when i debug and run the application the first page will come up but when I add a tab my web browser messes up and vb goes to this part of code [code]
I've started a project in Expression Blend and has been working the codes in Visual Studio 2008. It was alright, no problem. I've worked heaps of projects like that before without any problems. However, out of nowhere, my WPF designer in VS2008 now gives me the following error:
Object reference not set to an instance of an object. at MS.Internal.Package.VSIsolationProviderService.CreateIsolationProvider(String identity, AssemblyReferenceProvider assemblyReferences, IEnumerable'1 assemblyFolders) at MS.Internal.Providers.VSDesignerContext.GetIsolationProvider(IServiceProvider provider, [Code] .....
It displays the above instead of displaying the WPF designer. Also, I cannot Debug>Start Debugging the application anymore. I can still run/test/build it in Expression studio though. The funny thing is that if I restart a project in Expression blend, copy all the xaml codes, and copy all the vb .net codes from the original application, it works for some time, and then afterwards start giving me the same error at wpf designer in VS2008.
When i try to save my program an error pops up telling me that it cannot debug because some sort of file is missing... While my other projects just work, and while i repeat the same steps (placing an entity like a button, coding it), it just shows that error. Its really strange!
I have a backup program that is currently running in our Corporate Environment on about 70 machines. A mixture of Laptops, Desktops and Windows (xp-32, vista-32, vista-64, 7-32-7-64) with no problems.
There is one exception, and it's the reason I'm posting here for assistance.On one machine that is a Dell Latitude running Windows 7 64 bit with .Net 4 Framework installed the console application will crash immediately before it starts Sub Main. It simply give the generic windows error "A problem caused the program to stop working correctly." with no option to see debug info.
I changed default form icon in VB 2010. It worked perfect. But I re-changed this icon (form's icon property) to another icon, and when I debug or built the application it is still showing the old icon, through it shows it perfectly in design mode... What is the problem?
I have designed and published my small created app with WINDOWS FORMS using VB 2010 EXP on Windows 7. I can only install the app on the machine that I used to develop the app.I want to install the app on another computer but I cannot. I usually have error reports.
Example:Unable to install or run this application. This application requires Microsoft Common Language Runtime 4.0.3 to be installed on your computer.
what can I do to be able to install the app on a different computer which does not have .Net and does not have visual basic 2010 installed.
I'm getting the 403 Forbidden error while running a VS 2010 in debug mode. It gives me this error as it tries to read thru an XML File. See attachment. This is a web app and it's reading an XML file that retrieves the DB/Server information. It's not the Web.Config file but just a regular xml file. This file is read by every application in our system. Not sure why it suddenly started doing this. I've created the virtual directory on our IIS Server and set permissions on the C:inetpubwwwrootAppName directory of my C: drive where the app resides.
I've just installed Visual Studio 2010 Express on a new laptop running Windows 7 64 bit.
When I debug a VB project and an error is encountered a message is sent to the immediate window, but execution is not halted. This means I am unable to look at variables etc.
i have created a com class library with vb.net. i have registered the dll with regasm. Then i imported and used it to a vb6 project. I have noticed that if i unregister the library and register it again then i get the following error:
In order to make the library usable again, i have to rebuilt the library with different ClassId, InterfaceId, EventsId at the classes and then register the new dll.
PS: it also does the same thing if i overwrite the registered file with the same file or if i rename its folder and then rename it back to its previous name. Rebuid and re-registered is needed.
Simple question that does not seem to be covered: If I use a lot of Debug.WriteLine statements in my code, will they be completely absent in my production version?
I mean: Is the compiler smart enough to not emit any code for those calls? Or would I have to surround them by #if DEBUG..#end if directives?
