I'm trying to convert a site server 3.0 applicaton to

ASP+ and am having trouble instanciating several of

the objects in the global.asa file.  



I created a new dll with the same name

('Commerce.dll') by running it through tblimp.exe and

placed the new dll in

the /bin directory under the root of the website. It

still gives me the following error message:

You need to run tlbimp and regasm on your COM classic

DLL in order to use type 'Commerce.Dictionary'



Has anyone else run across this?

Hi,



This is a snap from the SDK.



----



The type library importer is responsible for converting the type definitions

found within a COM type library into equivalent definitions in a NGWS

runtime assembly. Conversions are done for an entire type library at one

time. You cannot use TlbImp to generate type information for a subset of the

types defined within a single type library. The output of TlbImp is an

assembly that contains NGWS runtime metadata for the types defined within

the original type library. This file can be examined with tools such as

metainfo.exe or ildasm.exe.



It's often useful to be able to strong name NGWS runtime assemblies (it's

impossible to make references to weak named assemblies from strong named

assemblies, for example). Therefore, TlbImp also include options for

supplying enough information to generate strongly named assemblies.



TlbImp has the following command line syntax:



TlbImp TlbFile [/out: file] [/silent][/unsafe][/originator: file] [/keyfile:

file][/keycontainer: name]



Where TlbFile can be the name of any file containing a COM type library.

This file can be a .tlb, .dll, .odl, .ocx, .exe file or any other file

format with a type library embedded as a resource. The file must be able to

be opened with using LoadTypeLib() API.



TlbImp only imports one type library at a time. On rare occasions, a single

file may contain multiple type libraries. In such cases, the specific type

library to be converted can be specified by append \res to the end of the

file name where res is the number of the resource containing the library

(i.e. "foo.exe\3")



Options:



/out: file - The name of the output file that the metadata definitions will

be written to. If the option is omitted, the metadata is written to a file

with the same name as the type library (not the file but the actual library

name within the file) defined within the input file with the .DLL extension.

If the output file is the same name as the input file and error is generated

to prevent overwriting the typelib.



/silent - Suppress all a console output.



/unsafe - Generates metadata that has runtime security checks suppressed.

Call any method defined exposed in this way may pose security risks. This

option should not be used unless the author is aware of the risk and

responsibilities of expose such code.



/keyfile: file - Signs the resulting assembly with a strong name using the

public/private key pair found in file. The key file should be in the

formatted generated by the SN utility.



/keycontainer: name - Signs the resulting assembly with a strong name using

the public/private key pair found in the key container called name.



/originator: file - Uses the originator key found in file to identity the

resulting assembly. The originator key is generated from the public/private

key pair supplied with the /keyfile or /keycontainer options if this option

is not supplied. This allows an alternate originator key to be supplied to

support developer key pair scenarios. The file is in the format generated by

SN the utility that is also part of the SDK.



The /keyfile and /keycontainer options both allow assemblies to be strongly

named. It only makes sense to supply one of them at a time.



Examples



TlbImp mytest.tlb



Generate a metadata DLL with the same name as the typelib found in

mytest.dll and with the .DLL extension.



TlbImp mytest.tlb /out: Mytest.dll



Generate a NGWS runtime metadata DLL with the name MyTest.dll.



----



I hope this will help you.



/Fredrik Normen







-----Original Message-----

From: Navid Nobakht [mailto:navidnobakht@y...]

Sent: den 9 oktober 2000 18:33

To: ASP+

Subject: [aspx] Site Server 3.0





I'm trying to convert a site server 3.0 applicaton to

ASP+ and am having trouble instanciating several of

the objects in the global.asa file.



I created a new dll with the same name

('Commerce.dll') by running it through tblimp.exe and

placed the new dll in

the /bin directory under the root of the website. It

still gives me the following error message:

You need to run tlbimp and regasm on your COM classic

DLL in order to use type 'Commerce.Dictionary'



Has anyone else run across this?





---