newbi question

  • Thread starter Thread starter Amadelle
  • Start date Start date
A

Amadelle

Hi all and thanks in advance,

I have written a class library in C# (a set of cs classes) which I would
like to install on our production webserver. It is used by some of the
asp.net pages that I have written. Everything ofcourse works great on my
local system. I have the class library set up as a different project with a
different path from the website addresses. I can see when I change the
configuration manager settings to Release mode the build generates a dll in
the bin/Release folder. But I can not install this dll using the
traditional COM registerations that I am aware of. Can someone help me in
the right direction as to how get this class library installed on a
different server?

I appreciate your help in advance,

Amadelle
 
Amadelle said:
Hi all and thanks in advance,

I have written a class library in C# (a set of cs classes) which I would
like to install on our production webserver. It is used by some of the
asp.net pages that I have written. Everything ofcourse works great on my
local system. I have the class library set up as a different project with a
different path from the website addresses. I can see when I change the
configuration manager settings to Release mode the build generates a dll in
the bin/Release folder. But I can not install this dll using the
traditional COM registerations that I am aware of. Can someone help me in
the right direction as to how get this class library installed on a
different server?
Click to expand...

Just copy the dll from the bin-folder to the corresponding folder on
your server. No COM-registration is needed.

Cheers

Arne Janning
 
If your ASP.NET application works correctly, then you are probably
referencing your class library in the ASP.NET application.
There's two ways to do this. You can create a Web Setup project. This is
very useful if your ASP.NET application needs it's own virtual directory.
However, I've seen some folks offer advice that a Web Setup project is too
much hassle. (I disagree.)

I'm going to refer you to the documentation for web setup projects.

On the other hand, if you have a working ASP.NET site already on your
production server, then there's not a lot of reason to do a web setup
project, since the configuration is already done for you.

When you perform a build on your Web application, then all dlls that your
app depends on will be copied to the /bin/Release folder. Copy all of the
DLLs to a /bin folder under your web application. Copy the .ASPX files to
the web folder itself. That usually does it. If you go this way, you are
taking the deployment into your own hands, so make sure you are familiar
with the security settings that you should use... once again, I refer you to
the documentation.

I hope this helps,
--- Nick
 
Back
Top