Planing - Scripting/XML Export

[GeorgeS]

The codewindow is a rich text box with context sensitive checking. I found much of the code and examples on the net. This was by far the hardest part to work.


GeorgeS

[samandhi]

ahhh I see, so you can export from more than one table (or all related things across tables). I like the idea behind that...

P.S. My program will have backup options in the future. ^-^ It's just taking some time. I'm only one person.

Oh dont take me wrong, I didnt mean for you to hurry, I am just trying to stay involved and help where I can, but I dont code, and am not very good with sql, or even perl. I've just been following the project long enough (and used to help support problems with servers on versions like 0.53) to kind of learn some things just by osmosis =P ... I think what everyone does here is totally amazing (or as they say on benchwarmers ama-zi-zing hehe)

[Kayot]

Originally Posted by GeorgeS

The codewindow is a rich text box with context sensitive checking. I found much of the code and examples on the net. This was by far the hardest part to work.

I'm making my own control for this ^-^ so when I'm done I can just drop in the control and select which code syntax it has to use. Thats why it's taking me so freaking long. But when I'm done, it will be one serious control. My only fear is that I won't be able to merge it with the program. I'm trying to avoid Multiple DLLs. So I might have to drop the code into my program which will be a bummer.

Speaking of DLL's any one know a way to merge DLLs into an EXE? I want to merge the XML and MySQL DLLs into my program. When this project is finished I only want two files in the dir. The EXE and the Config file.

[samandhi]

If you use VS .NET this might help

We made a command line tool which takes parameters and sends e-mails. We wanted to distribute this as an .exe but couldn't because it referenced a .dll. This meant that we had to send along the .dll and that it had to be in the same directory as the .exe. We wanted a way to have just one .exe but Visual Studio .NET doesn't offer this (a linker). Luckily, at the Microsoft Research Download Page there is a free tool called ILMerge which does just this. This is how you use it:

• download ILMerge
• put "ILMerge.exe" in your \WINNT directory
• In VS.NET, right click project, Properties, Common Properties, Build Events
• In "Post-build Event Command Line" enter:
  ilmerge /out:$(TargetDir)YOURAPPNAME.exe $(TargetPath) $(TargetDir)YOURDLLNAME.dll
• Then compile the Release version (not the debug version).
• In your "bin\Release" directory, you will find a YOURAPPNAME.exe which can be run on its own without the .dl

[Kayot]

Sweetness! I'll try it out now!

P.S. It worked!

[samandhi]

Great, hope that makes things easier for ya!