c# - Debugging multiple projects in a single solution -


is there way around issue of debugger being raised each project in solution when debugging postsharp? have 14 projects in solution , trying debug 1 of them postsharp seems difficult because debugger attach window pops each project in solution. if choose attach wrong debugger process breakpoint have set not hit , then, when starts building next project pops window not have active vs instance in it. there flag on msbuild can use "use same debugger process requirements of debugger process" or effect?

as understand, you're debugging compile-time logic of aspect following steps postsharp documentation.

when set "attach debugger" property on command-line, shown below, property set projects involved in build. , attaching debugger invoked each of projects.

msbuild myaspects.test.csproj /t:rebuild /p:postsharpattachdebugger=true 

what can instead, set property 1 project need it, temporarily editing *.csproj file:

  <propertygroup condition=" '$(configuration)|$(platform)' == 'debug|anycpu' ">     <postsharpattachdebugger>true</postsharpattachdebugger>     <!-- ... -->   </propertygroup> 

if don't want edit *.csproj directly, can put postsharp.custom.targets file in project's directory, , define property in file.

<? xml version="1.0" encoding="utf-8" ?> <project xmlns="http://schemas.microsoft.com/developer/msbuild/2003">   <propertygroup>     <postsharpattachdebugger>true</postsharpattachdebugger>   </propertygroup> </project> 

Comments

Popular posts from this blog

javascript - Jquery show_hide, what to add in order to make the page scroll to the bottom of the hidden field once button is clicked -

javascript - Highcharts multi-color line -

javascript - Enter key does not work in search box -