IDE :: Debug & Release Builds Overlap In VS2010 SP1
Mar 16, 2011It appears there is a major change in behavior with my projects now that I've installed SP1 for VS2010.
[Code]...
It appears there is a major change in behavior with my projects now that I've installed SP1 for VS2010.
[Code]...
I 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 RepliesWhen 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?
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 RepliesIm 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 RepliesWhat 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.
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?
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 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 RepliesIs 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 RepliesVS2010 - Cannot edit while paused in debug
View 8 RepliesI'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 having a strange issue when building assembly's for one of my modules.I was getting errors when running on 64bit which I traced back to being related to the assembly being 32bit specific. Our modules are(or should) all be built to be bit agnostic.Running CorFlags.exe on the assembly showed the following.
Version : v2.0.50727
CLR Header: 2.5
PE : PE32
[code].....
if you are debugging or releasing a projet , vs writes exe or bin files to the bin and obj folder in a release and debug version, are ther differences bewteen these files with the same name in 4 folders ?, eg myproject.exe
View 3 RepliesWill setting the DLL to release hide descriptive names & class info?
View 4 Repliesdebug the managed / unmanaged boundry environment: VS2010 on Win7 64bit
View 1 RepliesI have seen a different behavior before, but this time my application just doesn't work properly when debugging, while it does everything perfectly after compilation.
My project is beginning and does just one thing: monitor the clipboard and save its contents to a XML. It has just one form (frmMain), which, when loaded, puts itself in Windows clipboard listening, via WIN32 API. Then, whenever receives a message, the form has to check if it's from clipboard and, if so, saves the actual contents.
The code is below:
Public Class frmMain
Private Const WM_CLIPBOARDUPDATE As Integer = &H31D
Private XmlDocument As System.Xml.XmlDocument
[CODE]...
So, as I've said, after compiling, everything works perfectly. However, when debugging the "AddItems" function is never called. I set a stop point in the line Win32 API is called (in frmMain_Load) and the execution NEVER STOPS THERE! Debugging line by line, I found out that after executing some lines from frmMain_Load, VStudio just jumps to WndProc and never comes back to frmMain. I mean, the form is shown, and the rest of its initialization code is never executed. Because of that, my form is never added to clipboard listening (this command is at the end of frmMain_Load) and, consequently, all messages my window receives are not from clipboard, and, therefore, nothing is saved.
Is it normal to VStudio just bypass some code because a event triggered other method? This could lead to lots of complications and it's not consistent with after compiling behavior. A proof that what I said is actually happening is this: I passed the last 5 lines from frmMain_Load (where the Win32API is called) to the beginning, so my program would call the API before initializing the XML file. OK, now what I have: the API is called, but the XML commands are never executed. Consequently, "AddNewEntry" is called, but I have a null-reference error, because my XML was never initialized. Have you ever faced that bizarre behavior? What can I do so my debugging is correct and I don't have to compile my program for each test I want to do?
I have a Form with a Media Player in it. Which plays a Song.
[Code]...
It's playing in the background since the Form is hidden. When I play itin Debug, everything works fine. When I run the app outside Debug, I get this error: [URL] The Music File is there, but strangely, there comes this weird error.
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 a project written in Visual Basic.NET and at each action I do have a statement for handling the exceptions (if any) :
Try
{what to do}
Catch exc As Exception
lib.WriteToLog("text", lib.GetLine(exc.ToString()))
End Try