I just got handed a click event with 19 pages of code. Yep, you read it right: nineteen pages!
What can I say? My need for a refactoring tool that works in Visual Basic 6 became immediate. Luckily I found CodeShine through a little googling.
It doesn’t do a lot, compared to Refactor! and Resharper, but the things it does are invaluable. Its functions are: Extract method, Introduce Explaining Var, Extract function, Localize module variables and Rename.
The current job is about defining/refining and documenting a system that is a couple of years old. I was a big part in building it initially but it has grown without much control since then. As I see it, the main reason it is hard to get a grasp of it now is because there is (or has never been) a central role to consolidate the development. For each little project there has been a new project manager who only wanted to do his part at the lowest cost or him.
I’m just about done reading Professional Team Foundation Serverand at the end I found this little gem:
This tip needs the Team Foundation Power Tool (tfpt.exe) to work.
When you are working offline you just clear the read-only attribute on the files you want to edit. Later, when you are online, you open the command line, navigate to your workspace and run:
Now the power tool will find all those writable files and create a change set from them.
When I moved logview4net to SharpDevelop I got the dreaded CodeDomSerializerException in the WinForm designer. It complained about resources not existing.
Since everything worked in Visual Studio and the application compiles and runs I started looking for other things. After some digging around I found that the properties in the typed resource class was declared internal. I changed the modifiers to public instead and now the WinForm designer works again.
In light of the recent controversy of using plugins in Visual Studio Express and getting some inspiration after listening to the DotNetRocks episode with Christopher Wille on SharpDevelop I thought I should give SharpDevlop a chance again. I am working on two utilities that I plan to release as shareware and as I do not want to rely on tools supplied by my employer I have been using Visual Studio Express until now.
Here Dan Fernandez explains the technical reason Microsoft claims TestDriven is in violation of the EULA.
I had not understood how much of a hack the integration is. Hijacking a process and injecting code is not something you do by accident.
So my rule is in favor of Microsoft, but I hope they can solve it without taking TestDriven out of business.
This article is revisited here.
There is an ongoing conflict between Microsoft and Jamie Cansdale regarding TestDriven.NET.
I think Microsoft is really wrong here. Is anybody really going to buy one of the non-free Visual Studio SKU’s because they want TestDriven to work? The companies that are so cheap that they don’t use the ‘real’ Visual Studio SKU’s now will probably not buy them anyway. It is still possible to run the unit test outside of Visual Studio so the cost isn’t justified for TestDriven alone.
Visual Studio Express Editions The free editions of Visual Studio are just fantastic. If you’re developing for Windows they are the best free IDE:s out there. TortoiseSVN Lets you use Subversion from Explorer. It doesn’t get much easier than that. With OpenSVN you have no excuse to program without source control. Testdriven.NET Run your unit tests from within Visual Studio. You don’t have to release buggy code because you are using free tools.
I’m trying hard to not make this blog a place where I drop links, but some tools I just can’t ignore.
GhostDoc 2.0 has been released:
Roland Weigelt : GhostDoc 2.0.0 Released
… and there is a lot of fuzz in the cloud because of these: 09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0
… or you get an ‘Object not set…’ when trying to expand the DataSource list in the properties window,it might be because you have a corrupt datasource in your solution.
Press ALT+SHIFT+D to open the data sources window.
If there is one with a yellow sign in front of it; delete it and Visual Studio should start working again.
I got a corrupt DataSource when I imported a solution to TFS.
Attrice Corporation Team Foundation Sidekicks
From the site:
Team Foundation Sidekicks is a suite of tools for Microsoft Team Foundation Server Administrators and advanced users providing Graphic User Interface for administrative and advanced version control tasks in multi-user TFS environments.