RE: Registering a .NET assembly for COM interop access from an ASP page

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Hi Zoe,

I think you may try to use the regasm /codebase to register the .NET
assembly.
Also because the ASP page is executed in the exe file which is located in
the %systemroot%\system32\inetsrv, the bin directory is the directory which
stored the asp.net code behind page.

So far I think you may try to use the /codebase switch to register the .NET
assemblly.

Best regards,

Peter Huang
Microsoft Online Partner Support

Get Secure! - www.microsoft.com/security
This posting is provided "AS IS" with no warranties, and confers no rights.

.

Relevant Pages

  • Re: Registering a .NET assembly for COM interop access from an ASP page
    ... ASP page is executed in the exe file which is located in the ... So by "bin directory" do you mean the directory where the process ... So far I think you may try to use the /codebase switch to register the ...
    (microsoft.public.dotnet.framework.interop)
  • Re: Registering a .NET assembly for COM interop access from an ASP page
    ... the ASP page is executed in the exe file which is located in the ... So by "bin directory" do you mean the directory where the process ... will be looking for the .net assembly DLL, which is what I'm trying to ... code behind file is when the .NET assembly is called from an ASP page, ...
    (microsoft.public.dotnet.framework.interop)
  • Re: Register .NET Dll for classic asp
    ... COM interop" to true. ... component not usable in ASP"); ... Override Uninstall: ... what would I do to register them? ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: shoot-em-up
    ... >> 's only about 14ZU to register though. ... >It's an exe file. ... don't have permission to install it on a machine, ... reading a few pages from "The Tibetan Book of the Dead" ...
    (uk.rec.sheds)
  • Re: .Net Assembly from Classic ASP and VB6
    ... You went right with the "Register with COM Interop" option. ... This is, of course, one of the symptoms of "DLL Hell" that .NET ... I'm not sure about why your ASP page couldn't find your assembly after ...
    (microsoft.public.dotnet.framework.interop)