By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
431,650 Members | 753 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 431,650 IT Pros & Developers. It's quick & easy.

debug/release

P: n/a
Tym
Being new to dotnet from VB6 could someone please explain the
difference between the degun build and release build of the "deployed"
program?

Does this mean that the debug comment can be logged when running the
debug version? If so - how?

advTHANKSance
__

Tym

All this technology and it still takes forever to get anywhere.
Nov 21 '05 #1
Share this Question
Share on Google+
5 Replies


P: n/a
I "believe" that the difference is the debug build gives you for example a
line number and a "clear" error message in case of an error. A release build
will be faster because there will be more optimalizations and it hasn't got
the debug file attached to it, but there will not be "clear" error messages
withe linenumbers.

hth Peter

"Tym" <no*@any.time> wrote in message
news:3v********************************@4ax.com...
Being new to dotnet from VB6 could someone please explain the
difference between the degun build and release build of the "deployed"
program?

Does this mean that the debug comment can be logged when running the
debug version? If so - how?

advTHANKSance
__

Tym

All this technology and it still takes forever to get anywhere.

Nov 21 '05 #2

P: n/a
"Tym" <no*@any.time> schrieb:
Being new to dotnet from VB6 could someone please explain the
difference between the degun build and release build of the "deployed"
program?
Visual Studio -- Debugging
<URL:http://msdn.microsoft.com/library/en-us/vsdebug/html/vc_Debugging_Your_Application_home_page.asp>
Does this mean that the debug comment can be logged when running the
debug version? If so - how?


Visual Basic and Visual C# Concepts -- Tracing and Instrumenting
Applications in Visual Basic and Visual C#
<URL:http://msdn.microsoft.com/library/en-us/vbcon/html/vboriinstrumentationtechniquesdebugtracefornetfram ework.asp>

--
M S Herfried K. Wagner
M V P <URL:http://dotnet.mvps.org/>
V B <URL:http://dotnet.mvps.org/dotnet/faqs/>

Nov 21 '05 #3

P: n/a
The difference between the Debug and Release versions, beside the
ability to modify the configuration parameters for each, is the
inclusion of the pdb file when the application is compiled. The pdb is
essentially a resource file that maps the line numbers, class names and
additional source information into the error. When you throw an
exception in debug mode, the Exception.ToString will contain only
pointer information and runtime information - but no direct reference
to specific line numbers. In Debug compilation - this material is
available to the runtime - and the Exception will have that info.

Kevin M. Schreiner
VP Software Architecture
Business Intelligence Force (bi4ce)

Nov 21 '05 #4

P: n/a
The difference between the Debug and Release versions, beside the
ability to modify the configuration parameters for each, is the
inclusion of the pdb file when the application is compiled. The pdb is
essentially a resource file that maps the line numbers, class names and
additional source information into the error. When you throw an
exception in debug mode, the Exception.ToString will contain only
pointer information and runtime information - but no direct reference
to specific line numbers. In Debug compilation - this material is
available to the runtime - and the Exception will have that info.

Kevin M. Schreiner
VP Software Architecture
Business Intelligence Force (bi4ce)

Nov 21 '05 #5

P: n/a
Tym
Thanks to all who replied - more reading to do!!
__

Tym

All this technology and it still takes forever to get anywhere.
Nov 21 '05 #6

This discussion thread is closed

Replies have been disabled for this discussion.