debugging upgraded component in 
Author Message
 debugging upgraded component in


I am a newbie, so pardon my ignorance.  I have upgraded a
pre-existing vb6 component into and made some
necessary changes.  This component was meant to be used by
an asp page, so in the debugging properties of the
project I set the project start up as a uri.

In the prior version of Visual Studio, when I had a
component in the IDE and started the de{*filter*} which
launched IE and ran my asp script and I could debug my VB
component from there as long as I created the object

In Visual this isn't the case.  If I try to do
a dim MyComponent as new... I get this error:
Compiler Error Message: BC30002: Type 'componentname' is
not defined.

How is the asp or aspx supposed to know what component
should be called?  I'm sorry if this has already been
covered, but I can't seem to find an answer!

Tue, 16 Nov 2004 23:37:42 GMT  
 [ 1 post ] 

 Relevant Pages 

1. Upgrade from Visual Basic 6 webclasses to VB.NET/ASP.NET

2. Debug VB.NET DLL(Class Library) from ASP.NET page

3. ADO.NET with ASP.NET using VB.NET

4. Returning Dataset to ASP.NET from .NET Component / Business Object Serialization

5. OCX to NET components required for VB.NET??

6. User Defined Exceptions in component utilized by an ASP page

7. Problem passing VB COM+ ASP Request object to .NET component System.Web.HTTPRequest through COM interop

8. Survey on ASP/VS6.0 versus ASP.NET/VS.NET

9. Visual Basic.NET , ASP or ASP.NET

10. VB6/ASP vs .NET/ASP.NET development

11. REXEC from ASP.NET or VB.NET

12. and


Powered by phpBB® Forum Software