com interop

pipecarou · Apr 28, 2012

i have an asp app that uses the SQLDMO object and i am trying to port it over to asp.net i'm having problems, though, including a reference to the dll in order to be able to instantiate corresponding objects for example, in researching COM interop for .net, i came across this article: http://www.aspzone.com/articles/john/dotNETInterop/ it certainly LOOKS easy enough! but when i tried to do as the article suggests (i.e., create a .net assembly from the existing com dll using tlbimp.exe), i end up with an assembly but it somehow isn't being recognized when i try to import it into my vb code for example, the assembly i created from the existing sqldmo.dll is sitting in the bin directory of my application root and is also called "sqldmo.dll" using ildasm.exe i confirmed that the namespace is "SQLDMO" and then used the following line to reference it in my code: Imports SQLDMO now, when i try to compile the vb file containing this reference, i get errors such as: error BC30466: The Namespace or type 'SQLDMO' for the Import 'SQLDMO' cannot be found. and of course, all of my attempts in the code to instantiate the objects of that namespace (such as: dim oS as SQLDMO.SQLServer) throw errors does anyone hane any ideas what i may be doing wrong? thank youhere's what i've found out so far about this problem: http://63.236.18.31/forum/asp.asp?M=283986&P=1&F=20 http://63.236.18.31/forum/asp.asp?M=284922&P=1&F=20when i was doing the compilation of my .vb file that uses the sqldmo object, i was forgetting to include in my command line: /r:binsqldmo.dll so now the namespace is recognized but i've got another problem which i will endeavor to conquerbefore getting into the meat of this post, i will outline my application somewhat... ? i converted sqldmo.dll into a .net assembly dll ? i changed my "legacy" vbscript functions which used sqldmo.dll into .net-compliant vb code ? i compiled the vb functions into a stand-alone assembly ? i built an asp.net front-end to utilize the new assembly now, the "other problem" mentioned in my previous post referred to various errors i was receiving due to calls similar to the following: oDB = oSvr.Databases(sDatabaseName) the errors were telling me that there was no default property for the "Databases" collection well, that problem was finally solved by doing: oDB = oSvr.Databases.Item(sDatabaseName) then, when i finally got the vb file compiled into a happy little assembly, i tried running the asp.net app when the app made calls to the principal functions in the assembly, i would get the following error: The exception Breakpoint. A breakpoint has been reached. An exception "Unhandled Win32 Exception" has occurred in MyApplicationName i didn't know what the heck that was supposed to mean - so i delved into all the developer forums i knew about and finally found out that using the sqldmo object in .net can be a little buggy here is a list of some com-interop/sqldmo problems reported: http://discuss.develop.com/archives/wa.exe?S2=dotnet&L=DOTNET&q=SQLDMO+&s=&f=&a=January+2001&b=July+2001 a solution is mentioned in one of those posts ( http://discuss.develop.com/archives/wa.exe?A2=ind0102C&L=DOTNET&P=R4767 ) and it worked for me - now my app runs just fine i just wanted to post this in case anyone else experienced this same sort of problem

com interop

pipecarou

New Member