Also try my PluginManager article, had to deal with the same issues. IIRC I had to create proxies (transparent cross domain objects) to prevent types jumping domain boundries. xacc-ide 0.0.15 now with C#, MSIL, C, XML, ASP.NET, Nemerle, MyXaml and HLSL coloring - Screenshots

nevermind, i just altered the file format to allow the assembly name as well.

Nevermind, I changed it to Maybe not that exactly, but it worked. Thanks for the help

It's possible, but c# was not designed to do such low level work. Besides, I think what you want already exists. Install a new local printer, chose FILE: as the port, when you get to picking the printer driver, install Generic/Generic Text. Then you can output whatever you want. You'll have to output the file format yourself so you better know the exact format of a TIFF file or what ever your going to print. RageInTheMachine9532 "...a pungent, ghastly, stinky piece of cheese!" -- The Roaming Gnome

See my reply here. smbecker wrote: But if I set cmp_name to a valid computer name, pbBuffer becomes an invalid pointer. And the return value is what? "When I was born I was so surprised that I didn't talk for a year and a half." - Gracie Allen

If you are referring to the AppWizard's question about the MFC library, then it is asking if you want the MFC library completely embedded into your application or whether you want to access MFC via a DLL (Dynamically Linked Library). From a programming point of view, there is no difference. Static linking makes the application more portable to weirdly configured machines (such as those with ancient MFC libraries or missing them altogether) but seriously increases the size of your application.

I made the change and I am still getting the same linking error as before. Any other suggestions? Thanks