.net - Debug Information For .NET Assembly In Release?
Dec 11, 2009
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.
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.
I 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.
If 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?
I'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.
I'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.
I 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]
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.
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 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.
Every time I compile a new release build in vb.net 2009, the file version number of my main exe is correct, but the assembly version number is the same as the last build instead of the current version even though I manually change the file and assembly version in the design studio to be the same prior to compiling.The only way I can get the assembly version to be correct is to close Visual Studio and delete the obj folder. Then if I open the solution and recompile, all is well.
Here is the information copied from the About box in VS:
Microsoft Visual Studio 2008 Version 9.0.30729.1 SP Microsoft .NET Framework
I 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.
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
I am debugging an assembly which I loaded dynamically with Assembly.Load(Byte[]), but I am facing some problems.First of all, I can't move the yellow arrow in Visual Studio 2010 to step into other lines of code, and also I am getiing exceptions ("Cannot find the method on the object instance.") when trying to do a quick watch on objects from a third party library (controls from Infragistics for example.)
Dim data = My.Computer.FileSystem.ReadAllBytes(file.FullName) Assembly.Load(data)
When using Assembly.Load(String), everything works fine, and there are no problems.
EDIT: I tried loading the debugging symbols for my assembly with Assembly.Load(byte[]. byte[]), but it I sitll get Exceptions when trying to debug objects from third party libraries.
when I build I get this warning "Found conflicts between different versions of the same dependent assembly"the target for the application is any cpuI went through all refernced project/solutions - they are all any cpu, .net 3.5. There are some externally supplied dll from microsoft, sybase which I don't have control.
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.
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 am using 2008 Express Edition. I am trying to make a Release build instead of a Debug build.Under Tools->Options, Projects and Solutions->General - I checked Show advanced build configurations. The option to switch configurations does not show up in the IDE.
After this, I went to the Project Properties->Compile and switched the Configuration from Active(Debug) to Release.After building, I looked in my project directory, however only in the Debug sub-directory was the .exe and nothing in the Release sub-directory.I have used Visual C++ Express Edition, where I noticed that if you do not change to Release in the IDE than after changing to Release in properties, resets the project to the last configuration setting which is usually Debug.how to make the Debug/Release box available in the IDE, since Tools/Options does not make it show up?