I'm surprised to get a compile error in release mode with the following code.I have a DEBUG only function declared
#If DEBUG Then
Private Function DEBUG_Check() As Boolean
'Do some checks[code]....
I get a compilation error "DEBUG_Check is not declared"I thought calls to Debug.Assert were completely removed from Release compile?
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.
[Code]...
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]
View 5 RepliesI 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?
View 4 RepliesBoth 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).
View 1 RepliesI'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.
View 2 RepliesIt read some data from a database and put the result into a word document. In this document is a blanc table with a bookmark to indicate the start position.In debugmode this works fine and after distributing thsi is still working fine.A user called me to say that the word document was a complete mess. I ran the application in production mode and yes it is a complete mess. Because the bookmark is not found, the data will be enterd into the wrong column.When i return to debug mode, the apllication is still correct and the result on the word document is good. Behalf of this, there are users who don't have this problem at all.
View 3 RepliesI cant figure why the VB JIT Debugger control transfers the error to the program when I run in Debug mode and goes on in an infinited loop... I am using VB.NET 2008 and MS Access as the database backend.What I am trying to do here is that whenever I catch an exception (I have some C# code dll added to this main program and it should catch the unhandled exception and the addhandler routine will follow suit. So the moment any unhandled exception is caught MyHandler method is invoked and I need to take the backup of the database (Delete if the original file exists, copy the *.bak file as the original file name(was created during new file development) ,name it as *.mdb ) show a customized messagebox warning the user to abort (custom crash dialog instead of the standard default one)Somehow Myhandler goes in an infinite loop stop at line Globals.startBackup inside Private Sub MyHandler..Any idea on this weird AppDomain.Unhandled exception and how to prevent this from happening? [code]
View 1 RepliesI just updated to VS2010 SP1, but I cannot be certain this problem didn't exist prior to the update.When I build my project the version in /bin/debug builds, but nothing builds in /bin/release. I do not remember making any changes that would affect this, but nothing I do now will get the release version to build.
In the Application settings under "Compile" I have Configuration set to Release and the Build output path is "binRelease For Debug I also have Configuration set to Release.
There doesn't seem to be anything else left to change/adjust - but no matter what I seem to do nothing builds in the bin/release folder.
How can I get in my application at runtime in which mode it has compiled? The compiler is VB.net (VS 2005). Something like in C++ #if defined(_DEBUG).
View 1 RepliesI am confused about the folders that setup creates. What are Debug, Relese and Bin folders and what folder I need to give to my user while distributing the application.
View 2 RepliesWhich is the toolbar with the dropdown for release or debug?
View 4 RepliesI have a Linq-to-SQL class diagram in my web application containing the two tables in my database (held in a DBPro database project in the same solution). All was working fine yesterday. I start doing some work tonight and note that the solution compiles fine in Visual Studio, but when I run the web app I get a compilation error:
Description: An error occurred during the compilation of a resource required to service this request. Please review the following specific error details and modify your source code appropriately.
Compiler Error Message: BC30002: Type 'FrostAlertDatabaseDataContext' is not defined.
[code]....
When an error occurs in any of my .NET assemblies the user just gets a generic error saying "MyApp has encountered a problem and needs to close. We are sorry for the inconvenience." I would like the user to to see the error message and line number if possible.From what I understand you need to deploy the pdb file along with your assembly. I did that, but it had no effect. This is a Windows application.
View 1 RepliesIf I have Debug.WriteLine method in my code, do I need to comment all these methods before producing the Release version? Or does the compiler just ignore them?
View 3 RepliesI'm having a problem with the Debug/Release selection combobox disappearing in the VS.2008 toolbar.I can't find it anywhere in the toolbars.The same thing also happened in the VS 2010 beta now.
View 2 RepliesI'm using VS2008. Is there anyway I can determine in my code whether or not the program is running as a debug EXE or a release EXE? I know you can see a lot of the project properties using My.Application.Info.
View 4 Replieswhat is the difference between Debug and Release folders?
View 2 RepliesI created a vb dll using class library in visual studio 2010 [URL]... I have accessed this Dll in Excel VBA by referencing it through (Tools>>Reference)...I obtain different results when i run my program from Excel and when I run it from Visual Studio during debugging (here the debugging starts Excel as an external program). The results are exported by the dll function as a structure array ( The required values
are in double format in a constituent 1D array). The difference is as high as 5%.
What might have caused this difference? Could someone please help me with this?
Im new to VB 08 and i made a project that runs fine when i debug from inside the VB solution explorer. When i go to my BIN folder and try to run my project, the project runs but the button event seems to be none exsisten, also my message box does not appear on load, it should give an ERROR message if it does not detect the process writen in the module.
View 3 RepliesI have no idea why when I compile and run my application in x64 mode or anycpu my application crashes some time. some times it returns : Unhandled Exception
Attempted to read or write protected memory. This is often an indication that other memory is corrupt. and some times just says x has stopped working w/o details, any one knows anything about it ?
What is a good approach to managing a debug and release connection string in a .NET / SQLServer application?
I have two SQL Servers, a production and a build/debug and I need a method of switching between the two when my ASP.NET application is deployed.
Currently I simply store them in the web.config and comment one or the other out, however that is error prone when deploying.
It appears there is a major change in behavior with my projects now that I've installed SP1 for VS2010.
[Code]...
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.
View 3 RepliesIm using Visual Studio 2008 in Windows 7. Recently I cannot debug(F5) any projects because this following error is appearing
Error while trying to run project: Could not load file or assembly 'WindowsApplication5' or one of its dependencies. The module was expected to contain an assembly manifest.
I'm using MSBuild (via NAnt) to compile a bunch of VB.NET assemblies. Because these assemblies depend on COM Interop, I need to guarantee that they run in 32-bit mode on 64 bit OS's. I can get the executable assemblies to compile to 32-bit by changing the project in Visual Studio, but I'd really like to be able to force all of the executables to be compiled to 32 bit mode on the build server.I've tried a number of command-line parameters to MSBuild with no luck:
/p:Platform=win32
/p:Platform=x86
/p:ProcessorArchitecture=x86
Is there a performance difference between these two compiling options?
View 5 RepliesI have a solution with multiple projects (vb.net) , with some projects I have the optino to choose between the configuration: and in other projects I don't have that option. (I've had the option before). Has anyone an idea to show the option again. I can change it in project file (with notepad) but that's not userfriendly.
View 1 RepliesI 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?