I'm receiving a "strong naming" error when I'm trying to compile my InputFormat code file. I did a little searching around and tried creating a keyfile using "sn -k keyfile". I then added the entry to my assemblyinfo.vb that refers to the keyfile. I stopped receiving the "strong name" error in from my...

Great post with the VB example! It's helped me verify a few things.

You can define an Enumeration or any variable with a keyword-like name by putting it into brackets [ ]. The code below works fine : Private Enum FieldTypes [Integer] = 1 Real = 2 [String] = 3 Timestamp = 4 End Enum Thanks for those posts that helped me. Xav

That's great! Mike, do you mind posting this sample to the Repository? It can be a great start for the users that want to query SQL tables....

I just called everything aString, anInteger, etc. And it seems to be working. Here's a COM Input plugin for IISW3C logs that LogParser outputs to SQL: [code] Imports System.Runtime.InteropServices Imports System.Collections Imports System Imports System.Data.SqlClient Imports System.IO Imports System...

You're right, it's broken.......isn't it possible to qualify the names, e.g. EnumerationName::Integer? In any case you can use the numeric values directly.......

It's impossible to write a COM Input plugin for VB.NET. To make the FieldType enum, you have to use "Integer" and "String," both of which are identifiers in VB.NET.

Glad to hear LP is helping you!!!! I'll send you a private message!

[QUOTE User="LogParser User : aMaDEUS"]Quote: This was on a Windows 2000, wasn't it? If so, yep, bug's been fixed! Thanks for pointing out the HTML readme problem....I'll get it fixed!!!!! Hey, what's the plugin about? Care to share? ;-)[/QUOTE] The plugin is used to read some of our proprietary logs...

This was on a Windows 2000, wasn't it? If so, yep, bug's been fixed! Thanks for pointing out the HTML readme problem....I'll get it fixed!!!!! Hey, what's the plugin about? Care to share? ;-)