Fabio, A typical case is that I am at a client, using release bits, and need to figure something out. Having pdb there + symbol server support means that I don't need to do anything. Having to compile a debug build (especially if I need a particular version), is a pretty long process in comparison. And it is not like NH is only about delegation. A LOT of stuff happens internally, after al.
On Tue, Mar 2, 2010 at 4:42 PM, Fabio Maulo <[email protected]> wrote: > PDB are to step in NH... when ? in debug. > To "cut the bull head" we can release two sets of binaries (compiled in > release and compiled in debug) and the user can choose when and where use > one or other (for us is only a matter of modify the NANT's "package" > target). > btw we should apply the same thinking to ours dependency; for example: > You have a problem with a LINQ. You try to step in NH's sources and you > can't find the problem so you need to step in re-linq and there you will > need re-linq PDB... same for ANTLR3.NET same for any bytecode... > > In any case we are talking about very few guys and those guys know how > create a test to re-create an NH's issue. > > 2010/3/2 Ayende Rahien <[email protected]> > > Fabio, >> Why not for release? >> Generating PDB for release binaries has no impact on the runtime, only on >> the amount of info you can get >> >> >> On Tue, Mar 2, 2010 at 3:32 PM, Fabio Maulo <[email protected]> wrote: >> >>> We saw the issue in our JIRA and we will fix it in some moment for the >>> DEBUG compilation (not for release). >>> >>> 2010/3/2 Marcin Mikołajczak <[email protected]> >>> >>> Hi, >>>> >>>> We would like to provide symbol and source server suuport for >>>> NHibernate at http://www.symbolsource.org. Unfortunately, NHibernate >>>> release binaries are not released or even compiled with PDB support. >>>> Would it be possible to enable this in the build system? A similar >>>> question was posted some time ago and issue NH-2046 created for >>>> exactly the same request, but it did not get much attention: >>>> >>>> >>>> http://groups.google.co.uk/group/nhibernate-development/browse_thread/thread/b2835a0455c25e8d/b026b32da8cd3095?hl=en&lnk=gst&q=pdb#b026b32da8cd3095 >>>> >>>> http://216.121.112.228/browse/NH-2046 >>>> >>>> Here is the patch contents for current trunk code: >>>> >>>> Index: build-common/common.xml >>>> =================================================================== >>>> --- build-common/common.xml (revision 4949) >>>> +++ build-common/common.xml (working copy) >>>> @@ -161,7 +161,7 @@ >>>> >>>> <target name="set-release-project-configuration" >>>> description="Perform a 'release' build"> >>>> <property name="build.release" value="true" /> >>>> - <property name="build.debug" value="false" /> >>>> + <property name="build.debug" value="pdbonly" /> >>>> <property name="build.name" >>>> value="NHibernate-${project.version}" / >>>> > >>>> </target> >>>> >>>> Our goal is to be able to support the next 3.0 (pre-)release and any >>>> releases that come after that. SymbolSource is a new project that aims >>>> at providing a public symbol and source server for widely used open >>>> source library projects. Currently our focus is on the .NET platform >>>> and tools supporting Microsoft's symsrv technology - >>>> Visual Studio, WinDbg and others. >>>> >>>> To use it you need to configure a symbol server the same way you do >>>> for the Reference Source server from Microsoft. Then you'll be able to >>>> debug NHibernate source code from within your own projects that use >>>> it. Instructions for configuring Visual Studio are provided on the >>>> website. >>>> >>>> Best regards, >>>> Marcin Mikołajczak >>>> Co-founder of SymbolSource.org >>>> [email protected] >>>> >>> >>> >>> >>> -- >>> Fabio Maulo >>> >>> >> > > > -- > Fabio Maulo > >
