All posts by Julie

FoxPro DOS (yes, DOS) and those new-fangled printers

Just Rambling

I have an ancient FoxPro DOS app that churns out reports in a way that can’t be done too easily (not worth a rewrite) in Windows. It used to print these on an HP LaserJet II (back in the days when we listened to music on those big flat round discs with a needle) and has been printed on a LaserJet 4Si for about 12 years or so. I just got a sweet little LaserJet 1320t and expected all of this printing (which is done in PCL) to continue to work. But it didn’t – at least not without some sweat and tears – and I had a few lessons to learn.

1) The new printers are very special and create their own ports on Windows for printing. I finally realized that to print from DOS at all, whether a print command from the DOS prompt or from within FoxPro, I needed to change that to LPT1. (And have to remember to switch back for all of my other printing.)

2) Somehow my application was communicating enough to the printer by saying “legal paper, please” that the printer would find the right bin, even if I moved the legal tray to the upper bin or the lower bin. With the new printer, I needed to explicitly send the PCL code for legal paper and lower bin (esc&l3A  and esc&l4H)

3) My reports were printing out based on 117 lines per page (legal) . I could no longer get that to work (two hours was enough time spent on that problem, wouldn’t you say?). So I had to accept sticking with 102 lines and 8 lines per inch. I literally print this report using line and column #s for positioning, so this is a big deal for me. Of the 400 reports that get printed (one per entity), not too many of them needed that full length, so I will just have to keep an eye out for those and make sure the two page functionality I have built into this program works properly.

Hopefully this will help some other dinosaur who is moving partially to the modern ages (funny that I have one foot in the dark ages and the other dipping into the bleeding edge with the rest of my work). As long as Raymond Chen and team continue to allow me to use this reporting tool on Windows XP and beyond, I have no incentive to try to duplicate the process in windows.

Don’t Forget: www.acehaid.org

Talking about ADO.NET on ACADEMICDOTNET.com

dotNET

Earlier this month, Matt Cassell interviewed me (with great questions) for his podcast show, www.AcademicdotNET.com that is aimed at highschool programmers.

Matt is himself in high school, but at 15, has still been programming a lot longer than many of us!

My interview was #4. The first was Ted Neward, and he is about to push up #5, with Regional Director Barry Gervin.

It was a lot of fun to do the interview (and he even taught me how to use skype). What impressed me was that he had very specific questions so that he could be sure that the discussion was at the proper level for his target audience. I think that anyone at any age who is new to programming and new to .NET will find these podcasts very helpful.

Don’t Forget: www.acehaid.org

Chris Williams” INETA Website Marketing committee Chair

Community Cheerleading

Just noticed this on Jason Olson’s blog. Not being tightly associated with INETA, any more it’s been difficult to keep up with the frequent board and committee changes that have occurred since the [nearly] total board changeover in June. I’m not quite sure what a “Website Marketing” committee does (I know there was a Marketing committee and an Infrastructure (aka website) committee … perhaps they have merged), but I know that whatever Chris and Jason are working on, they bring great energy to the table!

Don’t Forget: www.acehaid.org

Confession – I’m still running vs2005 on a separate box

Just Rambling

I know I know. I have told many people that you can run vs2003 and vs2005 side by side. But I have this honker application to port and I don’t want to do it on the same machine where I need to be able to get at it (in vs2003) in emergencies. Plus I wanted everything super clean. The solution has many many assemblies and references a lot of 3rd party tools. Plus I had to move everything from WSE 2.0 to WSE 3.0. Too much for side by side if you ask me. Some of those 3rd party tools will be getting upgraded, like Janusys (finally moving to 2.0) and others.

So for the time being, I have taken my beautiful dual monitor setup and dedicated one screen to my other computer (until I find a solution as sweet as my VGA KVM cables that will work on DVI and isn’t a $200 switchbox). I’m still feeling the dual monitor vibe though. I’m coding on one screen and emailing, etc. on the other.

I could do this as VPC, but I had a whole computer just sitting there…begging for new bits!

Don’t Forget: www.acehaid.org

WSE3.0 and SoapContext.Security (obsolete)

WSE

In WSE2.0, the recommended way to do authorization, was to attach a principal with role information to a SecurityToken in a custom UsernameToken manager (which you would be using to authenticate against anything but A.D.). Then in your web method, you can just get at that principal by returning the Context.Security.Tokens from the RequestContext. But that is now obsolete. In fact if you use it, you will get a warning that SoapContext.Security is obsolete and to write a custom filter instead.

However the samples and the documentation in WSE 3.0 still show the old method. So, I’m not a Michele or Benjamin or William or Clemens or Christian. And most people using this stuff aren’t (cause those guys have all moved on to INdigo, but I have a live app that needs ws security…). Now what?

I guess I am going to learn how to use filters today. (so much for my fantasy of cutting out for 2 hours after lunch to go skiing because we got about 4 inches of new snow last night. whaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa)

Don’t Forget: www.acehaid.org