Deployment woes

Results 1 to 2 of 2

Thread: Deployment woes

  1. #1
    Join Date
    Dec 1969

    Default Deployment woes

    Hi All, <BR> I&#039;m trying to deploy a web forms app which references a COM component which references ADO, and am having nothing but trouble. I went through the Microsoft deployment walkthrough:, but once I install the app on another Windows 2000 server (using the MS generated setup.exe file), I get an error that the ClassFactory can&#039;t create a component the second I try to access my COM component in code. I thought maybe my COM component wasn&#039;t registered, but if I unregister it I get a different error message (Component not registered). <BR> I also tried just manually copying all the development files over to the new machine, set IIS to use that directory as an application, and registered the COM component manually, but to no avail. <BR> I should add that my app works great on the development machine, and I&#039;m positive my COM component is bulletproof. Any suggestions? Thanks in advance, <BR>-Ringo

  2. #2

    Default RE: Deployment woes

    Not sure, but when you added a reference to your COM component, VS probably create the runtime callable wrapper for you and it is not on the server.<BR><BR>Check thses pages, might help:<BR><BR><BR><BR>ht tp://

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts