—

One of the really unsettling events before the launch of the TouchSmart PC was that Engadget somehow got a hold of some pictures that had been prepared for the launch in early 2007 at the Consumer Electronics Show. It was billed in the first sentence as “AMD’s sweet new rig”, which was a little bit of a slap in the face, since most of the real work fell outside of AMDs realm. I remember the team meeting when our program manager came in and told us about the “leak”. He had heard it from Microsoft just a few moments before joining the meeting. The mood in the room instantly turned. People started feeling both mad at the leaked information (and the leaker) and depressed about the potential impact this would have on our launch at CES. Microsoft especially was disappointed, since the TouchSmart PC represented a big investment on their part, carrying some of the Vista messaging. The TouchSmart PC was to be billed as one of a few “dream” PCs at CES. Having gone through an experience like that, I now always think about how the people involved must feel when I see “leaked” information about upcoming products. It’s not fun to have it happen to you.

On a happier note, the TouchSmart PC seemed to make quite a splash at CES. At the last minute I was asked to attend the show to help with technical support on the show floor. This was my first time attending CES and going to Las Vegas, and I quite enjoyed the experience. I ran into quite a few of the people that had worked with us on the project, and it was fun to see the crowds milling about the TouchSmart PCs at the HP and Microsoft booths. Having backstage access was a unique thing, but it involved a lot of walking around, helping the people doing demos by making sure the software was installed properly.

Since then, the HP TouchSmart PC has received numerous awards (including spot number seven on PC World’s list of most innovative products of 2007) and for a short while even had a fan website, the HP TouchSmart Owner’s Club.

—

This is the tentative end of the series. If you’re curious about other aspects, let me know, and if I can talk about it, I’ll see if I can accommodate your curiosity.

Share This

—

The guiding principles for HP SmartCenter and the other touch-optimized applications were to provide quick, “transactional” experiences, to have the applications be as intuitive as possible to use, and have them look polished and clean. HP SmartCenter was to be the “home page” for touch-based interactions with the PC. It had to easily give the user access to key Media Center experiences (TV, music, games) as well as two other touch-optimized programs HP was developing (HP SmartCalendar and HP Photosmart Touch). Finally the user had to have the ability to add access to a certain number of programs of their choice.

To enable some of the quick, “transactional” experiences using a touch screen, HP SmartCenter had to have large “target” areas that are easy to hit using a finger. This requirement helped making decisions about the layout of the “tiles” that the user touches to “launch” something.

We wanted to highlight a few of the key features of the TouchSmart suite of software. We decided that three tiles would be larger than the remaining ones, and that those three would be able to show more details from the underlying program than the smaller tiles. The calendar tile, for example, will pull three upcoming events out of the calendar program and display key information about those events right within the calendar tile. The Photosmart Touch tile will look for pictures in the My Pictures folder and display five of those in a rotation. The weather tile will display high and low temperatures expected for the day as well as the current temperature as reported by the weather service. The analog and digital clock tiles will display two additional clocks (probably configured for different time zones) in text form, in addition to the main clock, which is shown in a larger, graphical look.

The three user configurable tiles would be able to either start a program on the system or a web page, using Internet Explorer. We settled on only having three configurable items, since there was an overall limit in the graphical design at nine small tiles plus three large tiles, and we wanted to encourage people to stick with tiles that didn’t take you out of a touch-optimized / touch oriented environment.

Beyond picking a software development technology (WPF), our other challenges were the many changes in both Windows Vista and WPF as both matured. WPF introduced “breaking changes” several times in our short cycle, and we discovered numerous problems with the integration of WPF and Windows Media Center. We worked closely with Microsoft to get these addressed. But a few problems remained, one of which is that every time you start one of the programs we developed, the computer screen will go black for a few seconds. It gives you the unsettling feeling that something went wrong, but it’s actually a consequence of the interactions between certain software components that are controlling the graphics card (DirectX, WPF and Media Center). As much as we didn’t like it, we were out of time to address these problems by the time our shipping date came.

—

That’s a wrap for part 3. Next time you’ll hear about the reactions from the team when information about the TouchSmart PC was leaked to Engadget way before the actual launch event, and I’ll also talk a little about the launch at CES 2007.

Update (2008-04-30): Part four is now posted.

Share This

—

I hacked together a very simple first version of HP SmartCenter (then codenamed LaunchPad, which still is the name of the executable, incidentally) in HTML and my colleague Maguy added some rough graphical elements to give our design firm an idea of what we were looking for.

My quick HTML mockup

Improved graphics

From about February 2006 until April 2006 we then iterated with our design firm on the GUI and user experience design. Towards the end of May 2006 we took final delivery of the work from them. I was to turn their beautiful work into a living application with page navigation, drag-and-drop functionality, configuration options, and settings persistence. They had provided a solid foundation to build on, including well thought out namespaces, classes, animations and navigation design.

But there was still a lot of work to be done during the next three to four months. In addition to the application itself I was also responsible for delivering an installer, a supporting “touch optimization” program, and integration with our factory PC build process, including dealing with the “sealing” process that prepares the master hard drive for replication.

We participated in Microsoft’s early adopter program for Windows Presentation Foundation and Windows Vista, which gave us access to builds of the WPF bits, with a seemingly never-ending stream of Community Technology Preview versions. Windows Vista was in a similar state of flux, and I had my hands full, wiping out and reinstalling test machines and updating my developer machine to keep up with the changes.

At the same time I climbed the learning curve for WPF (which Simon Middlemiss once described as more of a cliff), trying to figure out how to get the mostly fixed-content XAML pages that the design company had delivered turned into malleable components and re-configurable layouts.

The initial design from the outside company included two components that pull information from the web: weather and stocks. We had to drop the stocks piece for business reasons early on, and had big challenges working out the business issues for the weather feed integration. We wanted our own high-quality images to illustrate the weather conditions and had to get approval from the owner of the feed data. I thought several times that the weather feature was dead, but stubbornness overcame pessimism, and we pulled all the right people from several companies together to get our images approved within 24 hours before the final code submittal deadline. I remember pulling a work-at-home weekend to fine-tune the weather feature where I had to stop working because I was hit with the flu. I was out for three days. After something like that happens you don’t give up a feature without a fight.

One benefit of being part of the early adopter program for WPF and Vista was that Microsoft arranged for training and troubleshooting sessions. I made two trips to Redmond under this program, once to get more in-depth training on WPF and Vista, and once to get help with troubleshooting performance issues we had run into. That’s when I learned that there is such a thing as a “managed memory leak“, which can be introduced in WPF without the programmer necessarily realizing it. Towards the end of the program three of my colleagues and I got to spend a couple of days with Microsoft again, this time at their Platform Adoption lab (Building 20), going over some last minute design and performance questions with their WPF developers one-on-one. This especially helped with getting HP Photosmart Touch into better shape for final release. We got a lot of tips and strategies for dealing with images, collections and containers in these sessions.

—

That’s it for part 2. Next time I’ll dig a little more into the guiding principles that were used for the implementation of HP SmartCenter, as well as some of the challenges and problems I encountered on the way.

Update (2008-04-30): Parts three and four are now posted.

Share This

My involvement with the HP TouchSmart PC began in about December of 2005. The decision was made to invest in software that would be best suited for the touchscreen that the unit would have. One of the results is HP SmartCenter as seen here (screenshot from my developer machine, not necessarily representative of the final product):

We had tight deadlines. Our final bits would be due in about six months, around June / July 2006. Our product marketing folks decided they wanted the touch application to provide quick access to TV and music as primary features. Windows Media Center was our software of choice for delivering TV and music experiences, and so we made HP SmartCenter run within Windows Media Center. This helped to avoid waiting for Media Center to start up when the user wants to watch TV or listen to music. In other areas the choice created lots of challenges. The initial one was picking a software development technology.

I had just attended PDC05 and was pretty excited about Windows Presentation Foundation (WPF) and the speed I could sense it would give developers and designers for rapidly creating exciting software. I had learned that Media Center in Windows Vista would support WPF, and my recommendation to use it for our apps to make the deadlines while delivering a polished user interface was accepted.

An interface developed in HTML would not have had the same quality (read: look-and-feel). Using the Media Center Markup Language (MCML / SplashFX) was not an option, since that was not going to be revealed in any useful detail until about March 2006, way too late for us to learn how to use it and produce a product.

At PDC05, it had been mentioned that a well-know design company had worked on some XAML styles for the show. We approached them to help out with the application design and asked them to deliver their stuff as working XAML / WPF code. They were pretty excited about the idea and signed on.

—

That’s it for now. Check back soon for the next installment of this mini-series, where I’ll show you a few screenshots of very early prototypes.

Update (2008-04-30): Parts two, three and four are now posted.

Share This

HDAUDIO\FUNC_01&VEN_14F1&DEV_5047&SUBSYS_103C30A5&REV_1000
HDAUDIO\FUNC_01&VEN_14F1&DEV_5047&SUBSYS_103C30A5

I’ve tried just restarting the sound services (as admin: net stop “Windows Audio”, net stop “Windows Audio Endpoint Builder”, net start “Windows Audio Endpoint Builder”, net start “Windows Audio”), but that doesn’t work. Restarting the computer works, obviously, but is too slow to be a proper solution.

One thing I can to do to get sound back without restarting is remove the “High Definition Audio Device” from Device Manager and then Scan for Harware Changes. But it’s still annoying to have to do this. Since there’s no crash involved (no Windows Error Reporting possible) and no “yellow bangs” in Device Manager, I’m not sure how I would report this to Microsoft. They probably wouldn’t do anything about it anyway. They’d say it’s a driver issue. Talk to the driver vendor. Nice idea. Trouble is the laptop is older (it scores a 3.2 Windows Experience Index, not half bad) , and the vendor probably won’t bring out Vista drivers for it. So it looks like I’m stuck with a broken package.

Maybe a kind soul (at Microsoft?) will read this at some point and get in touch to help me troubleshoot the issue.

Oh well. Feels good to get it off my chest, though.

Share This

Microsoft undoubtedly knew they could never afford to release a Server version in the state the code was in at Vista release. Corporations running mission critical things on Server would never adopt anything not rock solid. So Microsoft took the time they should have put into the “Client” version to finish things off properly for Server. Hindsight 20/20 and all that.

What can be expected of Windows “7″ after this? My guess is Microsoft will cave to market pressure again and release something not quite ready for the consumer market. With Vista, part of the reason for releasing too early was that Windows XP seemed to be getting too old. For Windows “7″ part of the reason will likely be a perceived need to catch up with Apple’s OS X.

With Vista, Microsoft was incredibly open about providing early builds to lots of people in order to get the quality right. And yet it wasn’t enough. It also seems that the biggest “achievement” that came from the openness was that people weren’t much impressed when the final product came out. In my view that’s a bit of a shame, because there are lots of truly great innovations in Vista (one of which is WPF). Microsoft will probably be more tight-lipped about Windows “7″ as a result. They might take a more Apple-like approach and keep things secret until the last minute. Surprise the world when they release Vista’s successor.

The problem is that Microsoft doesn’t seem to understand what it is about Apple’s offer that makes it so compelling. It’s not OS X. It’s not iLife or iWork. It’s how it’s all wrapped up in an end-to-end package. Beautiful, well performing hardware; good OS; good everyday software with features that people find useable and useful, integrated with revenue generating .Mac Internet services. And all because Apple has control of the entire chain, from hardware to software and services. Heck, they even control the retail experience.

Microsoft doesn’t have an answer for that. They play a different game. They play in many arenas and with many, many different partners. The ecosystem Microsoft provides the basis for is much, much bigger than Apple’s. Microsoft can never be Apple. And I don’t think they should even try to be.

I’m hoping that Microsoft will not cave in to market pressure but chart their own course for Windows “7″. Perhaps kick off work for another “NT” project (from the Dave Cutler/NT 3.x days) and focus on creating an operating system that is focused on the total consumer experience. Throw away all backwards compatibility in the consumer market, if needed (ironically, sort of like Apple did for OS X.) Provide backwards compatibility through virtualization or by keeping a separate line for corporate mission-critical applications. But mainly chart a course that doesn’t look too much at Apple or Linux or anything else, but follows new visions for what can be done with software running on ever more capable hardware. They have enough smart people to lead the way. There’s no need to follow anyone.

Share This

Anyway, if you’re having trouble with .NET 3.5 on Vista x64, try uninstalling the KB110806 update. I’m going to assume you know where to do that if you’re reading this.

Share This

So head on over to the CardSharkV page and take a look! I think you might find the program useful, if you like keeping your digital photos organized right in the file system and not just in some photo management program.

If you have any comments on the program, I’d like to hear them.

Share This

It’s a bit of an experiment, and I’m looking for some real-world “beta” testers. My plan is to try my hand at charging for the program. But to see if word will spread, I’m planning to give out 50 or so licenses without charge while I work out any kinks that might be in the program.

If you’re interested in trying it out, download the program, install and run it, and then click the “Request License” button.

Read more about it on the CardSharkV page.

Update (2007-11-25): CardSharkV depends on the .NET Framework 3.0. It’s thus meant to be installed on Vista systems only. If you have XP and the .NET Framework 3.0, it should still work. Also, since I posted the whole thing Saturday night after a whole day of re-shaping my first, never published version, I didn’t test the install too well. I’ve since had a little time to test and found some issues, especially with the license mechanism. I’ve posted version 1.0.2.0 to correct those issues and to improve the installer as well.

Share This

Deprecated features

The following features have been deprecated:

• Hosting for Microsoft .NET Framework 3.0 Extensible Application Markup Language (XAML) browser applications (XBAPs).
• The Triple-tap/Soft-keyboard ActiveX control for hosted HTML applications.
• Support for using alternative shells to run and host HTML applications.

The reason I’m surprised is that Microsoft announced the support for WPF based extensibility apps at PDC05 with some fanfare.

I guess interest among developers just hasn’t been there for WPF-based Media Center apps, and Microsoft needs to make judgment calls on where to invest in their extensibility platform. The rest of the deprecated features seem to have been made for the same reason: limited interest among developers for these features. In addition I think there might be issues of an architectural nature that just make the three things that got dropped too expensive to maintain or improve.

I’m sad about this development, mostly because I still don’t see a great set of development and design tools around for MCML. WPF seems to me to have a whole lot more momentum than MCML (WPF has the Expression suite of tools and has been billed as the “GDI for the next 20 years”), but who knows what may be coming for Windows 7, or even an earlier interim update for Media Center?

Share This

There is a workaround, if you really need UAC elevation, which you shouldn’t. But at a high level, it works like this. You create your ClickOnce app like you would normally. To go with it, you create a helper app that you equip with an embedded elevation manifest. You then add a test to your ClickOnce app to see if it’s running elevated. If it isn’t you make it call the helper app. It will cause a UAC elevation prompt and in turn launch the ClickOnce app anew. Since the helper got elevated, the ClickOnce app now runs elevated too. Of course, by doing this you might end up with users not accepting the elevation request. But from what I’ve seen real users do with those elevation prompts, it won’t matter much. Anyway.

The trick is getting the helper app included in the regular ClickOnce app. There may be better ways, but here’s one I’ve spent quite some time on to work out. Maybe it will help someone out there save time, like I’ve saved time by reading posts on elevation checks using managed code. So here are the steps I’ve followed to make this work:

1. Modify your ClickOnce app’s entry point to include elevation checks as described at http://www.itwriting.com/blog/?p=198. If the app is not running elevated, make it run the helper application and exit. The launch looks something like this:

   ProcessStartInfo

   psi = new ProcessStartInfo(“Helper.exe”);
   psi.UseShellExecute = true;
   Process.Start(psi);

   The UseShellExecute flag makes sure the UAC prompt will happen.

2. Create your helper application with an elevation manifest (the process for that is at Catherine Heller’s blog) and have it launch your app with something like this:
   
   string appExe = Environment.GetFolderPath(Environment.SpecialFolder.Programs) + @”\YourClickOnceApp\ClickOnceApp.appref-ms”;
   Process.Start(appExe);

   As you can see the whole scenario only works if you let the ClickOnce app create a Start Menu entry.

3. Build and publish both applications, making sure they use the option to rename the published files to .deploy extensions. This helps tremendously with web deployment.

4. Find the published helper .deploy files and copy them to the folder that contains the ClickOnce application’s .deploy files.

5. Open the ClickOnce application’s .exe.manifest file using MageUI. Go to the Files section and click the Populate button to include the helper app and its manifest in the fileset for the ClickOnce app. Save and sign the manifest. I used a stored certificate for the signing.

6. Open the ClickOnce application’s .application deployment manifest using MageUI. This is probably in the directory above the .deploy files. Open the Application Reference section. Click the Select Manifest… button and browse down to the manifest you modified in step 5. Save and sign the manifest. I used the stored certificate from step 5.

7. Now you have all the needed files packaged for uploading to your web server.

This is what will happen when the user downloads the app for the first time: A verification window shows briefly, followed by a download warning, followed by a download progress window. Now the UAC prompt will come, and if accepted, another verification window. Then the app will show.

On subsequent launches of the app the user will see the verification window, followed by the UAC prompt, followed by another verification window. Then the app will show.

It’s not pretty, but at least it works.

If you try these steps out and they don’t work, I’d appreciate an opportunity to correct them.

————————————————-

P.S.: The manifest generation step looks like this for C# projects:

“$(DevEnvDir)..\..\VC\bin\mt.exe” -manifest “$(ProjectDir)$(TargetName).exe.manifest”  ?outputresource:”$(TargetDir)$(TargetFileName)”;#1

The .exe.manifest for the helper needs to look something like this (you can leave out the commented parts):

<?

xml version=“1.0“ encoding=“utf-8“ ?>

<assembly xmlns=“urn:schemas-microsoft-com:asm.v1“ manifestVersion=“1.0“>

<assemblyIdentity version=“1.0.0.0“ processorArchitecture=“msil“ name=“Helper“ type=“win32“ />

<description>Helper</description>

<trustInfo xmlns=“urn:schemas-microsoft-com:asm.v3“>

<security>

<requestedPrivileges>

<requestedExecutionLevel level=“requireAdministrator“ />

<!–<requestedExecutionLevel level=”asInvoker” />–>

<!– <requestedExecutionLevel level=”highestAvailable” /> –>

</requestedPrivileges>

</security>

</trustInfo>

</assembly>

Share This

Share This

Imagine my surprise when I was greeted with only this message after typing in the Product Key from the box I just bought this morning:

!

We’re sorry, the following error(s) have occurred:

No Offer Found

Bummer. I guess I won’t be spending another $100 for my two extra copies.

Even more curious is that there’s no way to contact Microsoft about problems with the order page. Maybe they don’t want my money?

Share This

————————–

Call me a fanboy all you want. I went out to a local Best Buy this morning and got myself a copy of the Vista Ultimate Signature Edition. I figure Vista put bread on my table, so I need to give back a little. And no way am I going to do that without getting something a little out of the ordinary.

I got to Best Buy a little after ten and checked the shelves. No Signature Editions to be found. Luckily I went to the service desk to ask, and just as I was doing so, they brought out the four boxes they had at that store. Two got put aside by (for?) the employees, and I grabbed one of the remaining two. Talk about good timing. I think I also picked a good store to go to. It’s fairly new and people don’t seem to know it’s there, so there was very little “competition”.

Here are some unboxing pictures for your viewing pleasure:

Box front

Open back

System requirements on the side

Feature comparison list on the back

Other side

Outside cardboard box and inside plastic box

Inside plastic box front

Inside plastic box back with Bill Gates comments

Plastic box side

Opened plastic box with DVD / media holder

Leaflets inside media holder

CD order information

Back of media holder with key sticker

Share This

I had set my system up according to Tim Sneath’s post on the perfect WPF developer system, including VS 2005 SP1 and the beta version of the Vista extensions for VS 2005. I was running VS “as administrator”.

As it turns out there are some technical details around starting XBAP debugging sessions from an elevated VS process that cause this behavior if you already have another instance of IE running when starting the debugging session.

Thanks to Tim Sneath and Chango Valtchev at Microsoft for helping in tracking this down!

Moral of the story: If you want to debug an XBAP from VS 2005 under Vista, run VS non-elevated, or make sure you have no other instances of IE running when you start the debugging session.

Share This

Anyway, I found that the in-box drivers for an “Atheros Wireless Network Adapter” seem to do the job.

Here’s the drill: Start Menu - Computer - Right click - Properties - Tasks: Device Manager - Find the device in the list - Right click - Update driver - Browse my computer… - Let me pick from a list… - Find “Atheros Communications Inc.” and pick “Atheros Wireless Network Adapter”.

Share This

What I’ve been waiting for is also ready: the ability to request a key for your Vista development system. I’ve got mine and am writing this from Windows Live Writer running on my shiny new Vista Ultimate work laptop. Yay!

Share This

That may actually be the case, since, as far as I understand it, RC2 is built from what’s called the “RTM branch” in the source control system Microsoft uses to keep their code neat and orderly.

The thing about the way Microsoft uses source control is that they create “branches” of source code at certain points in time. This is documented at http://www.usenix.org/events/usenix-win2000/invitedtalks/lucovsky.ppt. Granted, this presentation refers to Windows 2000, but I doubt the principles have changed much.

The point that I want to make is that the RC2 source code (from the “RTM branch”, according to http://www.istartedsomething.com/20060901/windows-vista-beta-features-vs-content/) may have been branched off from the main trunk some time after the RC1 branch, but may not have had some of the RC1 code integrated back into it. Some code from the RC1 branch may not make it into the RTM branch at all, if it’s judged to be of dubious quality.

Judging by the fact that what Microsoft terms the “RTM branch” started with build numbers at 5700, and that RC2 has a build number of 5744, calling it “RC2″ is a bit of a misnomer, really. It would more accurately be called an “RTM preview”, but since lots of folks have been screaming for an “RC2″, that’s what Microsoft probably decided to give them.

It would be interesting to hear some Microsoft folks comment on that news.com review or my little commentary here.

Share This

It tells you about crashes that happened in the past, applications that installed or uninstalled with failures, hardware failures, windows failures and so on, and then it compiles all that data into a nice visual to give you an impression of how stable your system is / was.

If you click on a graph point in the past, you get a report of what exactly happened on that day. In the graph above, I was playing around with getting OneNote 2007 Beta 2 TR installed after I had upgraded an Office 2007 Beta 2 install that didn’t include that particular component originally. I had lots of installer crashes and app crashes that day, and it shows in the dip in the graph.

Of course, the Performance graphs are not too shabby either:

It finally includes a hard drive monitor as well, not just CPU, memory and networking!

You can find it in Performance Information and Tools - Advanced Tools (or by typing “rel” into the Start Menu Search Box):

Share This

Unfortunately the machine I had this problem on didn’t have the secpol.msc file on it (I still don’t know why), so I dug some more and found that there is an equivalent raw registry key:

HKLM/System/CurrentControlCset/Control/LSA - LMCompatibilityLevel

It’s 3 by default on Vista RC1 (NTLM2 only) and I had to change it to 1 (LM & NTLM, NTLMv2 if negotiated).

I’m afraid that this will bite some other folks like me who have “unorthodox” network setups at home. I hope Microsoft has a good reason to ship with this default setting, but I’d advocate they change it.

Update: A friend at Microsoft helped me realize that enabling LM & NTLM can be a potential security risk. Passwords can be stolen when using LM and NTLM. Vista uses NTLM2 by default to guard against the known vulnerabilities of NT & NTLM authentication.

In my personal situation I’m not that worried about changing the setting, since my computers stay isolated on my home network, but it’s probably not for everybody.

Share This

I found some instructions using Google (https://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=181082&SiteID=1) and here is the gist of what needs to be done (to spare you from having to read the whole thread):

Run a command prompt as Administrator and do the following:

BCDEDIT /set {bootmgr} device boot
BCDEDIT /set {default} device boot
BCDEDIT /set {default} osdevice boot

Then run Ghost 8.x like this:

ghost.exe -fdsp
or
ghost32.exe -fdsp

I tried this with two hard drives (once with a test drive, then with the real one), and it worked beatifully.

Share This

With Vista, not only do you get the .Net Framework 2.0 (much improved over the previous versions) in the box, but also the amazingly powerful Windows Presentation Foundation (which is what I’ve worked with), Windows Communication Foundation and Windows Workflow Foundation (two pieces I know nothing about yet).

This will lower the barrier to entry for applications developed using these powerful tools to zero. As long as you’re writing your application for Vista you can be sure the basic requirements are there.

There will be issues with certain features of WPF (rendering in software vs. hardware, especially for 3D), but the framework helps you detect these issues and makes it possible to adapt your application to lower its “flashyness” (RenderCapability.Tier, remember this needs to be shifted down by 16 bits if you want to use 0, 1 and 2 as the human readable values).

To me Windows Presentation Foundation is the most important technology to come out of Microsoft for a long time. I’ve never written too much actual Win32 or even MFC/ATL UI code for client applications, but I’ve done a lot of HTML / CSS stuff and pure business object stuff (COM/ATL). More about that in my next post. I don’t want this to get too long.

Share This

Share This