On the file enumeration issue... In my parsing code, I used a particularly cheesy trick. I just wrote a routine that recursively goes through folder and emits a list of all files with a particular extension. This has some particular advantages for this situation (although there are some potential drawbacks). Let me toss out some stuff for comment about this approach.

+ The code is relatively easy to use. It's only a few lines which can be understood and adapted easily. For example, you can set it to look at backed up FLMM files by looking for files ending in ".ini.flmmbak". You can enumerate the files used by a mod without installation by specifying the parent data folder of the mod.

+ It is modular
This is really just a generic file enumerator; it can be plugged into any other FL tool, and even used for odd specialized uses I don't know about - for example, enumerating all SUR and CMP files. It can also be adapted for sub-scoping - for example, we can just blip through the \Equipment or \Ships folder, or let the user pick a subfolder to do scoped analysis.

+ Not "super-efficient"
I think it's good enough, but it does have to list all files first, which can take a second or two. The result is over a thousand pieces of data, of 55 to 120 or more characters length. That's pretty trivial on modern PCs, though, and in my opinion the easy organization and understanding of what it does is well worth a few extra milliseconds of processing time.

You have no idea how much I want to buy you a beer right now! Absolutely wonderful program! My mod is now totally bug free, wooohoooo!

Nemo me impune lacessit.

Hmm, i've been thinking. What if you took the handy dandy FLspit script? Just plug it in to your program (i did that in VB6 and it worked. Haven't tried with vb.net, which i assume your using. GO VISUAL BASIC! ) Use it to produce a log file, and the cross reference the log file errors and warnings with your scanning. In this way it is possible to double-check your FLscan work. Plus it'd be a handy option to hit a button and have that text file pop up

And on another matter, has anyone thought of making a huge freelancer editing program? Where instead of you wrestling with 5 or so different programs you could just use 1 effecient one that integrated all of them seamlessly.

Just a thought


FL:CE Mod Team Leader

The installer is asking me for .net framework v1.1.4322 even though I've got v2.0 installed. Is the version I've got missing something or is the installer having trouble finding the .net framework in the registry?

Like many things Microsoft, v1 is completely separate from v2, and not completely compatible. If you only have .Net 2, you will need to get .Net 1 as well.

Then v2 is probably incompatible with v1, meaning the rest of the programs that use v2 won't work. =/



Edited by - Denier-of-Soup on 1/30/2007 11:25:07 AM

that is most likely the case, but they do coexist on the same machine without any issues.

Hmm, thanks for the heads-up. I'd forgotten about this problem. If you've got version 2.0 then you'll have no problems running v1.1 programs. FLScan will work perfectly on anything later than v1.1, including v2.0.

The issue is simply with the installer, which due to a pretty massive oversight by Microsoft doesn't check as far as v2. The installer will check for a version of the framework greater than 1.1, so it'll look for 1.1, 1.2, ... , 1.n, but won't then look for version 2.x.

If you're still having trouble then all you need to do is copy the program files onto your computer and they should run fine. If needed I'll send you the files manually.

Could FLScan read FLMM scripts? If i wrote: <dat file="...\...\....ini" metod="apend">, would it detect the error?

I will try it out.

why ask a rhetorical question on a forum? no - FLMM reads INI files - it can check your activated mod and tell you if it has errors, but it could not tell you what XML file they came from (this you should be able to locate quickly, unless your XML is a mishmashed mess)

i think a better question is, does the mod monitor track XML file changes?

Ok, thanks Cold_Void.

I have another question:
My FLScan isn't running, i have Net Framework SDK and Framework 1.1 installed and it isn't working, it comes up: "Do you wish to debug with JIT Debugger, press cancel" so i do and then it comes up with this: "JIT Debugger cannot be found. Click Retry to Try Again or OK to Terminate", what do i do?

Please help,
Dudeofthed!

i've never seen your specific problem so i can only think to ask if you've got .net 1.1.4322 (right click on the install package in explorer for direct confirmation of version info) and have SP2 XP - that's my setup basically.

@CV
FLScan will happily work without SP2. That's not a requirement for Net Framework 1.1.

@Dudeofthed
I'd go with what CV suggests and make sure your version number is right as there were a few different ones.

Member of the HAVEN ADMINS community
http://talonstrike.co.uk/HavenAdmin/index.php

Gizmo Studios - Home to the Galactica mod series
http://gizmostudios.proboards38.com/index.cgi

Nah, any other .NET Framework files do not work either.

This is the exact error message displayed, and what i do:
1) I click on FLScan.exe. Error Received:
Application has generated an exception that could not be handled.

Process id=0xb0c (2828), Thread id=0x3e0 (992).

Click OK to terminate the application.
Click CANCEL to debug the application.

[b2) I click CANCEL to debug. Error Received was:
Registered JIT debugger is not available. An attempt to launch a JIT debugger with the following command resulted in an error of 0x2 (2). Please check computer settings.

cordbg.exe !a 0xb0c

Click on Retry to have the process wait while attaching a debugger manually.
Click on Cancel to abort the JIT debug request.

3) I click on Retry and nothing happens.

It worked at least 1 year ago when i used it, but since i had to repair my computer it has gone all screwed. Of course, i had it removed before i did the repair.