From: mick on 12 Mar 2010 05:52 Can someone tell me **exactly** where in the machine.config file that I place the <configuration> <system.windows.forms jitDebugging="true" /> </configuration> entry. An example script snippet would be more helpful than a general "under system.windows.forms bit" answer. TIA, mick
From: Jeff Gaines on 12 Mar 2010 06:50 On 12/03/2010 in message <OS5qvIdwKHA.4492(a)TK2MSFTNGP05.phx.gbl> mick wrote: >Can someone tell me exactly where in the machine.config file that I >place the ><configuration> ><system.windows.forms jitDebugging="true" /> ></configuration> > >entry. > >An example script snippet would be more helpful than a general >"under system.windows.forms bit" answer. Good to see it's not just me who gets this wrong! The last few lines of my machine.config are: <commonBehaviors><endpointBehaviors><Microsoft.VisualStudio.Diagnostics.ServiceModelSink.Behavior/></endpointBehaviors><serviceBehaviors><Microsoft.VisualStudio.Diagnostics.ServiceModelSink.Behavior/></serviceBehaviors></commonBehaviors></system.serviceModel> <system.windows.forms jitDebugging="true"/> </configuration> So you don't need an additional <configuration> even though the instructions can be read that way. -- Jeff Gaines Dorset UK That's an amazing invention but who would ever want to use one of them? (President Hayes speaking to Alexander Graham Bell on the invention of the telephone)
From: mick on 12 Mar 2010 08:56 "Jeff Gaines" <jgaines_newsid(a)yahoo.co.uk> wrote in message news:xn0grjuxa32cqcl001(a)msnews.microsoft.com... > On 12/03/2010 in message <OS5qvIdwKHA.4492(a)TK2MSFTNGP05.phx.gbl> mick > wrote: > >>Can someone tell me exactly where in the machine.config file that I >>place the >><configuration> >><system.windows.forms jitDebugging="true" /> >></configuration> >> >>entry. >> >>An example script snippet would be more helpful than a general >>"under system.windows.forms bit" answer. > > Good to see it's not just me who gets this wrong! > > The last few lines of my machine.config are: > > <commonBehaviors><endpointBehaviors><Microsoft.VisualStudio.Diagnostics.ServiceModelSink.Behavior/></endpointBehaviors><serviceBehaviors><Microsoft.VisualStudio.Diagnostics.ServiceModelSink.Behavior/></serviceBehaviors></commonBehaviors></system.serviceModel> > <system.windows.forms jitDebugging="true"/> > </configuration> > > So you don't need an additional <configuration> even though the > instructions can be read that way. Cheers Jeff. I`d actually set this up on my old system before but couldnt remember how to do it. mick
|
Pages: 1 Prev: graphics in c# console application Next: Referencing .NET 2.0 but end result uses .NET 3.5 |