Home All Groups Group Topic Archive Search About

creating components with visual studio .net 2005 and c# 2005 ??

Author
14 Sep 2006 9:05 PM
jason
Pardon Noob questions...

Why would somebody create a component using vs.net 2.0 and C# ? To use
it from non .net solutions or unmanged code?

dumb question, I'm finding these instructions for compiling c# into a
component dll from the command line..

csc  /r:  REFRENCE DLL /t  library /out DLLNAME.DLL Program name.cs

How, does one do this from Visual studio 2005 and C# 2.0 ?

Author
14 Sep 2006 11:55 PM
Cowboy (Gregory A. Beamer)
Not sure on your wording, but it sounds like you mean class libraries. The
main reason for creating class libraries is reuse of code. Compile into a
DLL and you can use across many projects.

Is this what you were asking about, or did I miss the point?

--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA

*************************************************
Think Outside the Box!
*************************************************
<ja***@cyberpine.com> wrote in message
Show quote
news:1158267933.611446.77570@h48g2000cwc.googlegroups.com...
> Pardon Noob questions...
>
> Why would somebody create a component using vs.net 2.0 and C# ? To use
> it from non .net solutions or unmanged code?
>
> dumb question, I'm finding these instructions for compiling c# into a
> component dll from the command line..
>
> csc  /r:  REFRENCE DLL /t  library /out DLLNAME.DLL Program name.cs
>
> How, does one do this from Visual studio 2005 and C# 2.0 ?
>
Author
15 Sep 2006 12:29 AM
jason
I guess it's wording I'm trying to work out. I guess I'm trying to draw
a distinction between creating a class library and creating a
component. Is there a difference? Was there a difference between 1.1
and 2.0?

Can compenents created with .NET be used by non .NET software like vb6
executables?

Thanks.

Cowboy (Gregory A.  Beamer) wrote:
Show quote
> Not sure on your wording, but it sounds like you mean class libraries. The
> main reason for creating class libraries is reuse of code. Compile into a
> DLL and you can use across many projects.
>
> Is this what you were asking about, or did I miss the point?
>
> --
> Gregory A. Beamer
> MVP; MCP: +I, SE, SD, DBA
>
> *************************************************
> Think Outside the Box!
> *************************************************
> <ja***@cyberpine.com> wrote in message
> news:1158267933.611446.77570@h48g2000cwc.googlegroups.com...
> > Pardon Noob questions...
> >
> > Why would somebody create a component using vs.net 2.0 and C# ? To use
> > it from non .net solutions or unmanged code?
> >
> > dumb question, I'm finding these instructions for compiling c# into a
> > component dll from the command line..
> >
> > csc  /r:  REFRENCE DLL /t  library /out DLLNAME.DLL Program name.cs
> >
> > How, does one do this from Visual studio 2005 and C# 2.0 ?
> >

AddThis Social Bookmark Button