No.
VS.NET 2005 has a feature which could be useful,
which is placing class files in the App_Code directory.
They get compiled automatically, and can be referenced
in aspx pages, but that's not quite the same.
The ability to compile assemblies from the command-line is
one of the most powerful features the .Net Framework offers.
It makes the job of creating classes, and referencing them in aspx pages, a snap.
After they're compiled, adding a reference to them in VS.NET
lets you access all the classes, methods and properties with full intellisense.
Juan T. Llibre, ASP.NET MVP
ASP.NET FAQ :
http://asp.net.do/faq/
ASPNETFAQ.COM :
http://www.aspnetfaq.com/
Foros de ASP.NET en Español :
http://asp.net.do/foros/
======================================
"Patrick.O.Ige" <pa********@optusnet.com.au> wrote in message
news:OM**************@TK2MSFTNGP10.phx.gbl...
Juan can VS.NET do this for you?
Patrick
"Juan T. Llibre" <no***********@nowhere.com> wrote in message
news:ed**************@TK2MSFTNGP11.phx.gbl... You have to know which assemblies you need to call.
Just add any required .net assemblies:
vbc /t:library /out:..\bin\SharedCode.dll SharedCode.vb /r:system.dll
/r:system.data.dll
etc.
If it's a pain in the butt, you're doing it the wrong way... ;-)
It's quite easy, actually.
Use the class browser to find out what's where.
Juan T. Llibre, ASP.NET MVP
ASP.NET FAQ : http://asp.net.do/faq/
ASPNETFAQ.COM : http://www.aspnetfaq.com/
Foros de ASP.NET en Español : http://asp.net.do/foros/
======================================
<an***********@yahoo.com> wrote in message
news:11*********************@g44g2000cwa.googlegro ups.com... > OK. thanks. But it's like pain in the butt for me to compile my VB
> code. When I tried doing that before, the system keeps saying that
> this library is missing, that dll file is not found.