With the recent (finally!) release of the RTM of the various Visual Studio productivity tools from DevExpress, its now possible for me to provide binaries of most of my plugins recompiled to run against the latest version of the DXCore API.
Although all of these plugins are open source and thus its easy for anyone to check them out compile them for themselves, as a convenience for others I am also providing compiled instances of them here for download as follows:
- DX_SourceOutliner
- CR_ClassCleaner
- Refactor_ClassCleaner_Menu
- CR_DeclareClassInProject
- Refactor_MoveTypeToFileInSpecificProject
- Refactor_UpdateNamespace
Enjoy~!
Thank you!
Hi,
Thanks for updating these plug-ins. I’ve just tried using the newly compiled CR_ClassCleaner within VS2010 with CodeRush 10.1.4 and it appears to throw an exception and the source file is left in quite a mess, although it works perfectly fine under VS2008.
@Rob:
Wondering if its possible for you to send me (via e-mail perhaps?) the source file that throws an exception when ClassCleaner is applied to it under VS2010 so that I can reproduce the issue on my side?
I’ve been using this version of ClassCleaner successfully under VS2010 for some time and so the only way for me to try to isolate the issue is if I can successfully reproduce it for myself.
Thanks,
-Steve B.
Thanks a lot !
Hello Steve,
Totally love this plugin (Source Outliner) for VS2008, but I have been having some trouble getting the DX Source Outliner running in VS2010. I installed the DXCore-10.1.5 and at first the plugin did not show up under DevExpress/Tool Windows. I then compiled the latest DX Source Outliner sources and now it does show up there (DevExpress/Tool Windows/DX Source Outliner — but the window does not display anywhere. I also looked for the old View/Other Windows to no avail.
FYI I am running VS2010 on Win7 x64 with 2x 24″ monitors. I have ReSharper 5.1 installed as well.
I will need to stick to VS2008 until I figure this one out – Source Outliner is one thing that I dearly miss! Made it so easy to organize and navigate my code.
Thanks in advance,
Mark
@Mark A:
I will investigate this tonight and let you know what I find — AFAIK it should “just work” once recompiled for DXCore 10.1.5. I think there is also a “VS IDE settings reset” sort of command-line switch that you can pass to devenv.exe when you launch it to reset your window locations, etc. in case that’s it.
Will report more investigation this evening when I get home and can experiment a bit further. I’d hate to be the reason you cannot move to VS2010 🙂
-Steve B.
The IDE settings reset is easy now: Tools/Import and Export Settings… and follow the wizard to reset devenv IDE settings.
I did the IDE reset and the behavior is the same – everything loads properly it seems but the window simply doesn’t display. 🙁
Also, do you want to remove “TRUNK_IS_NOT_IN_A_RELIABLE_STATE.txt” from your /trunk root?
Orthogonal question: why not port this over to the VS IDE Extensions world? Installing the DevExpress plugin gives me pause as a ReSharper user. I mean, weekend project, right?
Thanks again for your support!
@Mark A:
I think I know where your issue is: THE TRUNK ACTUALLY *IS* IN AN UNSTABLE STATE 🙂
Seriously, the ‘working’ code for the Outliner resides in the /branches/v1/ part of the repository right now. If you recompiled the thing from the trunk, its no surprise it doesn’t completely function properly. The trunk contains the work-in-progress of the v2 of the tool and isn’t at all intended to be used by anyone (yet!)
In the interim, as part of my attempting to diagnose your issue I have now recompiled the v1 branch against the DXCore 10.1.5 release and posted it here: http://code.google.com/p/dxsourceoutliner/downloads/list . Try that build and see what results you are able to get — it *should* work (it works for me on my VS2010 install just fine).
re: porting it over to the ‘non-DXCore-enabled’ VS2010 extensions world, the reason I don’t is that I am relying upon A LOT of DXCore infrastructure to make this thing run right now (everything from the DXCore CodeDOM being used to parse the source to the document eventing model that underlies when the tool ‘wakes up’ and notices it needs to update itself to the manner in which it invokes go-to-definition when you click a node in the tree). Even with the ‘smoother’ plugin model around VS2010, that’s a ton of functionality that I would be needing to reproduce in calls to the direct underlying VSAPI (which while better than pre-VS2010 is *still* a God-awful mess in many ways).
If this were a commercial product for which reducing adoption friction would mean increased sales such an effort would probably be worth the trouble. But as an OSS utility that makes me $0.00 there’s really no impetus for me to undertake such a thing. The DXCore-dependent ‘version’ of this meets my needs (and those of enough others that I’m OK with it remaining that way).
Honestly, I wouldn’t worry about installing the DXCore runtime (as a resharper user or otherwise) since its not as though DXCore is impeding the performance of your IDE unless/until you load a plugin (like mine) that makes use of it. Then if you close the SourceOutliner window the perf hit (such as it is) goes away. DXCore is a *very* light memory and processor footprint when its ‘idle’.
Yeah, its perhaps a less-than-ideal deployment story for my plugin to start with “First, visit DevExpress and download DXCore…” but other than the inconvenience it might cause there’s really only a negligible impact re: VS performance/speed IMO.
in any case, advise if the updated build on the google code site linked earlier works or not and if not we’ll try to investigate other possible causes for the trouble.
Let me know!~
-Steve B.
OMG IT WORKS! Recompiled the v1 sources and everything works as it should. Thank you! A few observations:
1. You ARE deriving income from this project! Didn’t you just get hired to do such “open-source-style-community-relations” work by a commercial entity? I would attribute $4.17 of your income to DX Source Outliner, which belies its utility to my daily life (which has probably saved me 5-7 minutes per day for months).
2. Isn’t there an SVN best practice guideline that the Trunk is always stable, compilable and functional? I guess I was led astray by the google code checkout command which points to the trunk.
3. Nice to see the dll is being placed in the VS \bin\Debug folder now instead of D:\Documents and Settings\sbohlen\My Documents\… 😉
4. Despite my ragingly fast computer and 12GB of RAM, VS does take a little while to load now with both ReSharper and the DevExpress stuff. Not a big complaint, but it is probably a 10 second hit to my 5-7 minutes of daily productivity gains.
Thank you, good times are here again!
FYI, During the drought without the Source Outliner, I tried the VX10 Code Map, and while it was handy, SO is much better IMHO because it shows the arguments for each item, whereas the code map did not. Kudos!
@Mark A:
Glad you got it working 😉
1) You’re (sort of) right about this — to a point. Getting *someone* to use my OSS projects is important, but getting *more* people to use them approaches a pt of diminishing returns without a direct business model (where more users eventually merely = more support burden)
2) Actually, AFAIK the developer community is divided on this pt. One course is (as you suggest) to keep the trunk stable and releasable at all times, do additional work on ‘feature-branches’, and then merge those feature branches back into the trunk once they are ‘ready’. But another practice many follow is the one I am following here: do volatile work in the trunk and past-working versions in branches. Usually this second option is preferable in cases where (as is the case here) the ‘new work’ is a pretty significant re-write with all kinds of complex-to-eventually-merge refactorings that would make an eventual merge of a ‘feature branch’ back into the trunk a kind of life-threatening experience 🙂
3) yeah, that always pissed me off too 🙂
4) true, there is no (completely) free lunch, merely great tasting lunches that don’t cost too much 😛
Glad you got it working and, yes, I agree that the ‘native’ VS tooling that would seem to ‘compete’ with SO aren’t really feature-complete when you look more closely at them.
Keep in touch,
-Steve B.
Just when you thought it was safe, MS released an update to their VS Productivity Power Tools that has something called “Solution Navigator” — basically a solution explorer with an expansion to all of the various class details. Kind of a mashup of the explorer plus class viewer. Pretty darn nice, actually, but I still prefer having the Source Outliner at the top right of my left monitor with VS 100% on the right monitor. That ways I always know where to look for the current file’s methods, etc.
http://weblogs.asp.net/scottgu/archive/2010/07/19/vs-2010-productivity-power-tools-update-with-some-cool-new-features.aspx
Once again, thanks for a wonderful tool and thanks for doing all the hard, free work!
Mark