Category: Development


How to convert a test project to a normal class library


Sometimes you make mistakes. One of the ones I make most often while using Visual Studio is creating a new project of the wrong type. Usually, creating using just the same one I usually created.

And just now, I added a unit test project to a project I was working on. Great, so that’s one job done. Now I needed to add the class library it was going to test – and added another unit test library. Doh!

Turns out this is fixable – simply edit the project file (the “Productivity Power Tools” extension provides a shortcut to this, if you don’t have it already) and remove the line:
    <ProjectTypeGuids>{3AC096D0-A1C2-E12C-1390-A8335801FDAB};{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}</ProjectTypeGuids>
then save and reload the project – which turns out to be easier than I thought.

Can’t claim I invented this trick – I found it the other way round on Adam Prescott‘s blog. But I’m putting it here because I know I’ll forget it, next time I need it.


AJAX Control Toolkit – bug!


For reasons best not gone into (or at least, not if I want my readers to stay awake), I’ve been working a lot with Microsoft’s AJAX Control Toolkit for .Net recently. If you’re unfamiliar with the ACT, it’s basically a bunch of additional web controls for .Net that do calendars, modal popups… general sorts of nice stuff.

And then suddenly on one page, I noticed a problem.

I had a hidden field, which I was using to store the value I needed when the confirmation came back yes. Let’s say (for the sake of argument) that it was either “badgers” or “cheese“.

Well, it worked the first time it ran.

And then the second time, I picked “cheese” instead of “badgers” and I got back this:

Badgers,,Cheese,,,,,,

Not. Happy.

After what felt like an aeon debugging the code, but was really only the time it takes between “Worthless Misery” and “Angel Of Agony“, I decided to debug the code.

Guess what? Turned out to be a bug in the ACT. PopupExtender controls don’t like being inside UpdatePanel controls. Who’da thunk it? What’s really amazing is that over the last 7 weeks, this is only the first time this issue has arisen.

Moral of the story, kids: keep your references up to date, and remember – it’s not always your code that’s at fault!


Convert Access 2007 forms to 97


You might be surprised by this, but you can still back convert Access 2007 forms, reports and modules to Access 97! (Why is another matter, of course, but let’s presume that you need to…)

OK, first of all, you need to export them to text, which is explained here in far more detail than I care to explain it.

So now, when you fire up Access 97, and try and convert them by running this line:

Application.LoadFromText acForm, "YourFormName", 
 "C:TempForm_frmTest.txt"

It fails, right? Well, you can easily change that by editing the text file itself…Read More »




Archives