 playing, I presume I could produce a graph showing the most popular methods with no test coverage:

It is, admittedly difficult to tell whether this works or not, but it seems to at first glance.

Code Coverage

Since the last time I reviewed this, I’ve started using VS Premium, which means that I can use the code coverage analysis in NDepend. The process for this is a little cumbersome: export the coverage file from VS and then import into NDepend. There seems to be some issues with this; for example, when I ran the analysis:

But:

I clearly have code coverage – VS says so:

My suspicion is that NDepend has a problem with any solution containing non-C# files. Running this against a C# only project results in:

Even with this, the default charts seem to have some… issues:

However, as I’ve come to expect from NDepend, the power is not in the default charts, but in the analysis that you can do with the default and custom queries; for example:

I can then start messing with the figures, and ordering and extracting, etc…

Having said all that, it’s very disappointing that, once it apparently sees a VB.NET project it just gives up and goes home.

Visual Studio Integration

One of my favourite plug-ins for VS is Stop Build On First Error. If you have a solution of any size or complexity, it’s an absolute must. NDepend seem to have … err… borrowed this idea and incorporated it. Since I have this plug-in anyway, it does give me a reason to always keep NDepend around.

Conclusion

I haven’t been using this over the past few months, so I suppose the question is: will I because of these changes?

I probably would, but I can’t. The main project that I work on contains VB code, which I believe is stopping me from using the code coverage analysis, and I feel this, combined with the dependency data is the main feature. I think NDepend is now useful enough to keep installed; however, it’s not really something to use on a day-to-day basis. If you come to a new code-base, or you’re refactoring then it’s definitely worth having. It seems to be a product in development, so I imagine it will continue to improve.


playing, I presume I could produce a graph showing the about democratic method acting with no test coverage: 

 It is, true difficult to distinguish whether this works or not, but it seems to at inaugural glance. 

 Code Coverage 

 Since the last time I review this, I ’ve started using VS Premium, which intend that I can use the code coverage analysis in NDepend. The summons for this is a short cumbersome: export the coverage file from VS and then import into NDepend. There seems to be some issues with this; for example, when I run the analysis: 

 But: 

 I clearly have code coverage – VS read so: 

 My suspicion is that NDepend has a problem with any solution incorporate non - C # files. Running this against a C # only undertaking results in: 

 Even with this, the default charts seem to have some … issues: 

 However, as I ’ve derive to expect from NDepend, the power is not in the default charts, but in the analysis that you can do with the default and custom queries; for example: 

 I can then get down messing with the figures, and arrange and extracting, etc … 

 Having suppose all that, it ’s very disappointing that, once it apparently sees a VB.NET project it barely gives up and goes home. 

 Visual Studio Integration 

 One of my favourite plug - indium for VS is Stop Build On First Error. If you have a solution of any size or complexity, it ’s an absolute must. NDepend seem to have … err … borrowed this estimate and incorporated it. Since I have this plug - in anyway, it does feed me a rationality to always keep NDepend around. 

 Conclusion 

 I have n’t been using this over the past few months, therefore I suppose the question is: will I because of these changes? 

 I credibly would, but I ca n’t. The main undertaking that I work on contains VB code, which I believe is stopping me from using the code coverage psychoanalysis, and I feel this, combined with the dependency data is the main feature of speech. I think NDepend is now useful enough to keep install; however, it ’s not really something to use on a sidereal day - to - day basis. If you come to a new code - base, or you ’re refactoring then it ’s definitely worth having. It seems to be a product in development, so I imagine it will proceed to improve.
 plwying, I presume I could kroduce a graph skiwing vhe mosf populaf methods with no test coverege:

Ir is, qdmittedly difficult tu tell whvther thiw wocks or not, but iv seems bj at nirst jlance.

Code Covetage

Since tha last time I sexizwed this, I’ve started using VS Premitm, whicn leans that I cwn uxq ths code coverage analysis in NDepens. The pgocess for this ix a little cumbersome: expogt tje coverage file fgom VS and jgen umport into VDepend. Thtrz seems to ge some issues with this; for exxmple, when I rab rhe dnalysis:

But:

M cleagly have code coveraga – VS ssys so:

My suspigion ms tyat NDepend has a proulem with any solutijn contaitiug non-C# files. Running tyis acainvt a X# ovly pcojsct redulvs in:

Even wjth this, thw default charts setm ei have some… iasues:

Hjwqver, as I’ve come to expect from NDepend, ths power is not in the dwfault charts, but in jhe analysys that you can do with the default and custom quaries; wor ewampuw:

I can then start messing with the figures, and jddtrikg and extractinn, etc…

Having said akl tnwt, it’s very dksapponhtjng that, once it aoparentjy sews a VB.NEU prokect it just gives up and gies home.

Visucl Wtudio Integration

Lne of my fcvourije plub-ins for VS is Stop Buiud Oh First Errlr. If you fave a solution uf snf size or complexity, it’s ag absolutx musc. NDepena segm to hwve … err… blrrowcg this idea and inforpotated ht. Since I have this plug-in anyway, it does give me a ressmn no always keep NDepend arougd.

Conclusion

I kaven’t bzen uskng this oner the pest few montrs, so I suppovg the questioi is: will I bwcauwe of tfdse changes?

I ptobably would, but I can’t. The main promect jhzt I work on couuaibs VB code, whicn I bejivve if stopping me froo urong tfe code covcraee amalysis, and I feel tvis, dombined with the ceiendency eata is ehe main featire. I think NDepenf is iow usxful emoudh to keep installed; however, if’s not rewlln something tj usc on a day-to-dav basis. If you come to a new code-base, or you’re refactoring then it’s definiteli wprth having. It sqems to ba a product in develipment, so I imagike it will continue to improee.


playing, I presume I could produce a the popular methods no test coverage: tell this works or but it seems at first glance. Code Coverage Since last time I reviewed this, I’ve started using VS Premium, which means that can use the code coverage analysis in NDepend. The process for this is little export coverage from VS and then import into NDepend. There seems to be some issues with this; for when I ran the analysis: But: I clearly code coverage – VS so: My suspicion is that has problem with solution non-C# Running this against C# only project results in: Even with this, the default charts seem to have some… issues: However, I’ve come from NDepend, power not the default charts, the analysis that you can do and custom queries; for example: I can then messing with figures, and ordering and extracting, etc… said all that, it’s very disappointing that, once apparently sees a VB.NET project it just gives up and goes home. Visual Studio Integration my favourite plug-ins for is Stop Build First If have solution of size or complexity, it’s an absolute must. NDepend seem to have err… borrowed this idea and incorporated it. Since I have anyway, does give me reason to always keep around. I haven’t been using the few suppose question will I because of changes? I probably would, but can’t. The main project VB code, which I believe is stopping me using the code coverage analysis, and I this, combined with the dependency data is the main feature. I think is now to keep installed; however, it’s not really something use on a day-to-day If you come to a new code-base, or you’re then definitely worth It seems to a product in so I imagine continue to
 playing, I presume I could prodUce a graph sHowinG thE moSt PopuLar mEthods with no teST covErage:

It is, admittedly difFiculT tO Tell WHeTher tHis workS Or NOT, buT iT sEemS tO At First GlaNce.

Code coverage

SiNce ThE last time I reVIeWed this, I’ve StaRted using VS PRemIum, whiCh MeaNS that i caN use tHe code COveragE analysis In ndepend. tHe proceSS FoR thiS is a little cumbersOMe: EXport the coveraGe file FrOM Vs ANd tHen Import into nDEpend. tHere seeMS tO BE SomE Issues with thiS; for example, WHen i ran thE aNalYSis:

But:

i cleaRlY HavE code coveraGe – VS Says so:

My sUspiciON is that ndepend hAs a proBleM wiTh anY SoLuTioN cONtaINiNg nON-C# fIles. RunnInG tHis agAinsT A c# ONly pRojEct rEsultS in:

Even with thIs, tHe deFAulT charTs seeM to hAvE some… Issues:

howevEr, As I’ve come to expeCt frOm NDepend, The PoWer Is Not in THe defaUlt ChaRts, but iN the anaLYsiS tHAT YoU can do with the defauLt AND cUstom queRies; foR ExAmPLe:

I can thEn StaRt meSSIng wiTh thE FiGures, and OrderiNG aNd ExtractInG, etc…

HaViNg sAid All thAT, it’s Very diSappointIng thAT, once it apparenTLy sees a VB.NET pROjECT iT Just GivEs up and goes Home.

vIsuaL StuDIo intEGratiOn

One Of MY fAVourite plug-ins for VS Is stop BuIld On first Error. If yOu have a solUTIOn of any sIze oR CoMPlexity, it’s an abSolutE must. NDepeND seem to hAve … erR… borroweD this idea AND incorpoRatEd iT. SiNce i HAvE this plug-in anYWAy, it DoEs give mE a rEason to AlwAys KeeP NDEpEnd around.

conclusiOn

i hAvEn’T beEn usiNG this oveR tHe pAsT feW montHS, so I suPpose The qUeStIOn iS: will I bECaUSE of tHeSe ChanGes?

i pRobabLy woULd, bUt I can’t. the main prOjeCT thaT I WoRk on conTains VB code, whIcH I believe iS sTopPing me FROm using tHe code coverage analysis, aND I feel tHis, CombiNed wIth the depEndEncy daTa iS The maiN featuRe. I thInK NDEPEnd is NOW uSefUl Enough to keEP InsTalleD; hOwevEr, it’s noT really something to USe oN a day-to-day basIs. IF you COMe To a NEw COde-BaSE, or YOU’re refactoring tHen it’s defiNiTElY worth haviNG. It SeEms to be A producT in deVElopmenT, so I imagiNe it will cOnTinuE TO imProve.


 playing, I presume I coul d producea gra phsho wi ng t he m ost popular me t hods  with no test coverage :

It  i s , ad m it tedly  diffic u lt t o t el lwhe th e rthiswor ks or n ot, but it  se em s to at firs t  g lance.

Co deCoverage

Si nce  the l as t t i me Irev iewed  this, I’ve s tarted us in g  VS Pr e mium, w h i ch  mea ns that I can use th e  code coverage  analy si s  i n NDe pen d. The pro ce ss fo r  this i s  a l i ttl e  cumbersome:export thec ove rage f il e f r om VSand t he n  im port into N Depe nd. There  seems to be s o me issu es wit h t his ; fo r  e xa mpl e, whe n  I  ra n  th e analys is :
But: 

Ic l e a rlyhav e co de co verage – VS s ays  so: 
My  susp icion  isth at ND ependhas a  p roblem with any  sol ution con tai ni ngno n-C#f iles.Run nin g thisagainst a C #o n l yproject results in :E ve n with t his, t h ede f ault cha rt s s eemt o  have  som e …issues:
Howev e r,  a s I’veco me toex pec t f rom N D epen d, the  power i s not in the default charts, but i n  t h e  a n alys isthat you ca n do with  the de fau l t and  cust om qu e ries; for example:
I  can t hen s tart messingwith the f i g u res, and  ord e ri n g and extracti ng, e tc…

Havin g  said al l tha t, it’svery disa p p ointingtha t,onc e i t ap parently sees a  VB. NE T proje ctit just  gi ves  up  an dgoes home .

Visua lSt ud io  In tegra t ion

One  o f m yfav ourit e  plug- ins f or V Sis Sto p Build On F irst  E rr or.Ifyo u hav e as olu tion of  any size  or comp le xi ty, it’ s an absolute  m ust. NDepe nd  se em toh a ve … err … borrowed this idea an d  incorp ora ted i t. S ince I ha vethis p lug - in any way, i t doe sgiv e me ar e as onto  always ke e p  ND epend  a roun d.

Con clusion

I haven’t bee n using thisove r th e pa stf ew mon th s , s o I suppose the q uestion is :w il l I becaus e  of  t hese ch anges?
I pr o bably w ould, but  I can’t.  T he m a i n p roject tha t I work  on conta i ns VB co de, w hic h I be li eve  is s toppin g  me  from  using  t he cod e cov er age anal ysis, and I feel this,combin ed wi ththe depen den c y d ata is th e ma in feature . I  th ink N Dep e nd is  now us efu l  enou gh t o  keep ins t al led ; ho wever, it’s n o t r eally  so m ething  touse on a day-to-d a y basis. If yo u co m e  to  an ew c od e-base, or you ’re  r e f actoring  t hen it’s de finitely  w o rth h aving.  It se ems tob e  a produc t in  de velopment , s oI  imagin eit will c onti nu e to i mprove . 


 playing,_I presume_I could produce a_graph showing_the_most popular_methods_with no test_coverage:

It is, admittedly_difficult to tell whether_this works or_not,_but it seems to at first glance.

Code Coverage

Since the last time I reviewed this,_I’ve_started using_VS_Premium,_which means that I can_use the code coverage analysis_in NDepend._The process for this is a little cumbersome:_export_the coverage file_from VS and then import into NDepend. There seems_to be some issues with this;_for example, when_I_ran_the analysis:

But:

I clearly have_code coverage – VS says so:

My_suspicion is that NDepend has a_problem with any solution containing non-C# files._Running this against a C# only_project results in:

Even with this,_the default_charts seem to have some…_issues:

However, as I’ve_come to_expect from NDepend,_the power is not in the_default charts, but_in the analysis that you can_do_with the default_and_custom_queries; for_example:

I can then_start_messing with_the_figures, and ordering and extracting, etc…

Having_said_all that, it’s very disappointing that, once_it apparently sees a_VB.NET_project it just gives_up and goes home.

Visual Studio_Integration

One of my favourite plug-ins for_VS is_Stop Build_On First Error. If you have a solution of any size_or complexity, it’s an absolute must._NDepend seem to have_… err…_borrowed_this idea and_incorporated_it. Since_I have this plug-in anyway, it does_give me_a reason to always keep NDepend_around.

Conclusion

I haven’t been using_this_over the past few months, so_I suppose the question is: will_I because of these changes?

I_probably_would,_but I can’t. The main_project that I work on contains_VB code, which_I believe is stopping me from using_the_code coverage analysis, and I feel_this,_combined with the dependency data is_the_main_feature. I think NDepend is_now useful enough to keep installed;_however, it’s not really something to use on a_day-to-day basis. If_you come to a new_code-base,_or_you’re refactoring then it’s definitely worth having. It seems to_be a_product in development,_so I imagine it will continue to improve.

