I'll show you mine if you...

How did you think that title would finish?

Anyways, as i mentioned the other day I've got components we use internally for testing and i'll show you some of them, hopefully this will encourage more people to share their component packages with the rest of the Windows Embedded community.

I'm going to check with the lawyers and find out which components we can share here and which we can't. More than likely if we're not distributing third party files we should be ok, but what if I've componentized a third party feature and I share the resource *information* like the reg keys, files, component dependencies and FBA custom actions. And then point you to the location of where to download and extract the files so all you have to do is create your own repository. Is that a bad thing? More than likely if I have to ask then i guess we already know the answer, eh? I'll let you know the outcome.

In any case, i have a macro component we use internally for troubleshooting Font and Code Page issues that shotguns hundreds of those components to your configuration. For instance, if you're trying to componentize, let say, Adobe Reader and you think it's failing to load a non-intuitive Windows font you can either shotgun this Font Macro to your config and rebuild as an experiment to help the process along or you can dig in and try to determine the specific missing resource.

I'll clean up the "FONTs - Max" & "FONTs - Medium" macros for you this week and post a link from the blog so you can download it.

- Andy

Comments

• Anonymous
  April 14, 2005
  andy,
  That title seems deviated from the content. blame it on those corrupted minds ;)