VB 2005 Win Application Can Run In Debug Mode But Cannot Run In Compiled / Release Mode
Oct 14, 2010
i am using visual studio 2005 on win 7 with office 2007. i have developed win application. i am using microsoft activex spreadsheet component in my program. so it automatically creates reference to AxInterop.OWC11.dll When i run program in debug mode (open program and click RUN in toolbar it works) but if i run directly .exe (go to bin elease doubleclick .exe) it give error at loading point of that component. It says "Attempted to read or write protected memory. This is often an indication that other memory has been corrupted." An unhandled exception occurrs.
I work for a shop that maintains a fairly new app. The app still has its fair share of bugs, with numerous tickets coming in daily. The error information we're given with those tickets is not as useful as it might be because the application was compiled in Release mode, which I read is smaller and faster (makes sense).
Are there any ramifications to deploying a .NET application to production that was compiled in Debug mode? I would expect it would be a bit slower, but I've read the difference is nominal. This would assure us that when we get errors on tickets we have line number associated with those errors and this, of course, makes debugging much easier. major red flags that would prevent you from doing this? I'm tasked with researching the possibility.
I have several VB.NET Windows Form applications connecting tp several Network databases. When I build, update and test my apps, I want them to connect to a testing database as opposed to connecting to the production databases when the app is released.Right now, I change a setting in my coding before releasing the app, but I would like this to be automatic, to prevent any testing data in the Production database and vice versa.I found this piece of coding on the web, but it doesn't seem to ever be in DEBUG mode and by DEBUG mode I mean when I click the "Start Debugging" button or the F5 key. [code]
I have an x86 VS2010 app running on a 64 bit machine that hangs in debug mode. Both the interpretive version and the compiled debug .exe hang. If I step through the interpretive version it runs. The release mode works fine. Doesn't seem like system memory is a problem as I'm reporting 1.8 gig free after I load the app. I've googled this and don't see anything pertaining to debug environment specific behavior. Is there a limit to what the debug .exe supports?
Both projects are set to build in release modeBoth projects are in the same solutionThe solution is set to build in releaseBoth projects output to a Release folder in bin / objEverything seems to be okay except for one thing.When inspecting the files with a tool such asI tracked this down to a setting in the Advnced Compiler Options for the pdb files.If the debug info output for VB is set to anything other than none - then the project builds in debug mode (keep in mind it still outputs to the release folder).
i create a simple webbrowser in a form , it works perfect on debug mode , but in release i always get this page cant not be displayed , no matter the website.
i am using visual studio 2005 on win 7 with office 2007.i have developed win application. i am using microsoft activex spreadsheet component in my program. so it automatically creates reference to AxInterop.OWC11.dll But when i run program in debug mode (open program and click RUN in toolbar it works) it works. But if i run directly .exe (go to bin release doubleclick .exe) it gives error at loading point of that component. It says "Attempted to read or write protected memory. This is often an indication that other memory has been corrupted." An unhandled exception occurrs.AxInterop.OWC11.dll is in release directory.Is this office 2007 error or Win 7 ?
I have a several C# console applications that basically parse tons of data in memory (LINQ) and output the results to a text file. Now, forget about the writing to the text file for a minute because this is not where the problem is occurring.
When I run the application in debug mode, I will never get it to utilize more than 50% of cpu usage. It will be parsing/massaging hundreds of thousands of records, but only go X fast and utilize 50% of the cpu AT MOST (as viewed in the Task Manager).
I would really like to use 100% of the CPU to make the processing go faster. Does anybody have any insight? I am running Windows XP Professional with Service Pack 3. I have Visual Studio 2008 Professional with Service Pack 1 installed. I have manually set the affinity of the process in Task Manager to a single core on the dual CPU. Sometimes I can catch it utilizing 51% or 52% of the CPU.
Whenever I make any changes in my project, they don't work and aren't visible in debug mode. They are all visible in my designer mode. It's the same with newly added code, it just doesn't work (even a simple command like showing a test messagebox doesn't work).
How could this be? It all worked fine until recently. I don't want to start over with my project, because it's a pretty big one.
My trial version of VS9 professional just expired and wanted to uninstall it, however upon loading, it goes into debug mode and displays the message;an unhandled win32 exception occurred in setup.exe [3816]If I do go into debug mode, then it loads VS but since my version is already expired, I can't do anything but close it...I can't repair it since I dont have the original installation files (its VS9 professional ENU, and microsoft doesnt have it up for downloads anymore.. but here is a SS of the other programes installed which are related to VS9.[URL]..
I have a custom control that as a custom property. The property has several preset values to chose from a drop down. The control can be added to a form. The property can be viewed and set in the properties box in the IDE. It all works fine.
Here's the problem: I can create new versions and recompile the control and/or the application without the properties preset value being lost as long as I do it in Debug mode. However, once I try to recompile in Release mode the custom property values predefined setting is lost. I first thought it was something with going from debug mode to release mode. But it seems to be ANY time I recompile in Release mode the custom property values are lost. Is this a quirk in VS that needs a configuration setting, etc. to get around it?
I'm wondering if there is any code that I could use in VB.net so it can determine the computer's startup mode (such as safe mode or safe mode with networking).
I have a few DLLs that I have added to my project. I placed directly into the BinRelease directory and set Copy Local and Specific Version to true. Now if I move to debug mode, it doesn't copy those DLLs into the debug folder, so it won't compile. If these are just 3rd party DLLs, and not being built by my program, is it normal practice to throw these into the Release and Debug folders every time?
I have a project that was download from the net. It is a open source project.I can run without anyerror with IDE 2005. But i cannot enter the debug mode. I have set the project build to debug. But i cannt still enter to debug.I also got the following message when i run the project.The following module was built with optimizations enabled or without debug information :E:Project.exeTo debug this module, change its project build configuration to debug mode. To suppress this message, disable the "Warn inf no user code on launch" debugger option
The solution and all the projects within it are set for Debug;I deleted the .suo file as recommended in one posting.I ran rebuild on each and every project individually and the entire solution.I deleted the files in binDebug and did the whole thing over again. Still can't debug.
While stepping into (F8) I did get the hollow debug symbol in the margin and when just running the program (F5) the program starts up without stopping at any of several breaks in different functions and subs.
I'm using VS2008, and I have a project that will not start when I press F5 or when I click the little green triangle in the toolbar. The screen flickers once, like the project is going to run, and then it doesn't. The build message claims the build was successful, but the project won't start.In the Configuration Manager, my 'Active solution configuration:' is set to Debug, and in the 'Project contexts' list, the 'Configuration' column for my Project is set to Debug. I've even switched them back and forth between Debug and Release and then back to Debug, all with no effect. The project that I'm trying to run is set as the 'Startup Project' in my solution.If I go to my inDebug folder and double-click the .exe, (which shows the proper time-stamp on the file) my app runs just fine.Any ideas why I can't get the silly thing to run in debug mode?
EDIT: It's a winforms application. My version of Visual Studio is 9.0.30729.1 SP
the code seems to be working fine when i am debugging but when i run the normal way no sms is send. the following is my code,see where i am going wrong.
dim smsPort As New SerialPort smsPort.PortName = "COM18" smsPort.BaudRate = "921600"
What this program does is it it moves the firewall tab on my Zonealarm from Medium to High thru a 2 timers and I can put how long for it to say on High and how long to stay on Medium
I ran into an issue today where VB is behaving differently from C#. The issue is as follows.
Also note this is for .Net 4.0.
Both projects are set to build in release mode Both projects are in the same solution The solution is set to build in release Both projects output to a Release folder in bin / obj
Everything seems to be okay except for one thing. When inspecting the files with a tool such as http://assemblyinformation.codeplex.com/ the VB projects show as Debug and the C# projects show as Release.
I tracked this down to a setting in the Advanced Compiler Options for the pdb files. If the debug info output for VB is set to anything other than none - then the project builds in debug mode (keep in mind it still outputs to the release folder). C# does not exhibit this behavior.
I did a blog post here to work around the issue - but would love to know the root cause if any one knows.
How can i Auto update or manual update my Software version. when i build my project on debug mode. Software version only auto increment when i publish the software. but dont want to publish my software yet. my project is developing state.
I have got a serious problem and I cant solve it. Images on my form are not displayed during debugging. When I build the application, there is no problem. But in debug mode no images are displayed. What can I do about it?
From my DLL project I have succeded in making AutoCAD launch by pressing F5 from VB.net IDE (Visual Studio 2008) en route to try to make debugging of the DLL easier ...
... however one last obstacle is currently in the way and the obstacle is that for some reason when I hit F5 and AutoCAD is launched my breakpoints are not recognized at all... and program runs from start to finish instead of allowing me to debug ...
It issues a strange message which says "The following module was built either with optimizations enabled or without debug information... to debug this module, change its project build configuration to Debug mode..." and it is all weird because as far as I know I am not in release mode .. but in debug mode (anyhow I am relatively new to Visual Studio .NET so I am thinking that my impression could be that I am in debug mode when in actuality I maybe in release mode)...
Here is why I think I am debug mode ...
1. From Solution explorer ... when I click on the Solution Name and view its properties ... the Active config property says Debug|Any CPU
2. When I look at the properties of the project and look at the compile tab it says that the Configuration is Active (Debug) and under Platform it says Active (Any CPU).
3. Under the Advanced Compile Options of Compile Tab from project properties ... Enable optimizations is UNchecked ...
Anyhow with all the settings mentioned above it seems that I have everything okay but then the message above proves otherwise ... and so at this point I know that I am still missing something ... like a setting somewhere... wondering what else do you think am I still missing?
As additional info...there are seven projects in the solution and it is the main one (the one that I set as startup project) whose properties I refer to in all the paragraphs above.
I want the designer to catch the error when I am debugging and I want the user to see my friendly message if an error occurs for them. I know I can acomplish this with the following:
[Code]...
I do not want to have to write all the #statements and having them cluttering up my code. It seems like this should be a common need and there has to be a better way. Does anyone know a better way?
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 have an app that runs silently everytime the user logs in. But I want to be able to pass it a parameter to make it print to the console. I use a conditional if statement to do this now, but I would have to recompile the project to set it to false or true.
