Separate Project DLLs

Dear Group
Apologies for this simple question. Would be grateful if you share your
opinion on this.
I've written a web application, compiling all classes into one project
DLL. Now I wonder if there are performance / resource advantages if I
compile some classes into separate DLLs and reference them instead. Any
articles, information on this? Advantages, Divantages? Will it slow
down the application if it has to reference a DLL?
Thanks very much for your help & efforts!
MartinPerformance isn't a factor...Divantage? You have 2+ dlls floating around
which might make it harder to maintain (assuming you are shipping a product,
which you likely aren't). Advantages? Better organization, reuse, less
bloat...
There's really no reason not to...but you shouldn't just do it for the sake
of it...hopefully there's some reasoning behind why they don't belong
together...
Karl
MY ASP.Net tutorials
http://www.openmymind.net/ - New and Improved (yes, the popup is annoying)
http://www.openmymind.net/faq.aspx - unofficial newsgroup FAQ (more to
come!)
<theintrepidfox@.hotmail.com> wrote in message
news:1112238300.593113.237330@.f14g2000cwb.googlegroups.com...
> Dear Group
> Apologies for this simple question. Would be grateful if you share your
> opinion on this.
> I've written a web application, compiling all classes into one project
> DLL. Now I wonder if there are performance / resource advantages if I
> compile some classes into separate DLLs and reference them instead. Any
> articles, information on this? Advantages, Divantages? Will it slow
> down the application if it has to reference a DLL?
> Thanks very much for your help & efforts!
> Martin
>
It is not a matter of performance. It is a matter of your system design. For
example, if you organize your application in presentation, business and data
access layers, you might have all forms in one project, business classes in
another project and data access classes in another project. 3 projects, 3
dlls.
Eliyahu
<theintrepidfox@.hotmail.com> wrote in message
news:1112238300.593113.237330@.f14g2000cwb.googlegroups.com...
> Dear Group
> Apologies for this simple question. Would be grateful if you share your
> opinion on this.
> I've written a web application, compiling all classes into one project
> DLL. Now I wonder if there are performance / resource advantages if I
> compile some classes into separate DLLs and reference them instead. Any
> articles, information on this? Advantages, Divantages? Will it slow
> down the application if it has to reference a DLL?
> Thanks very much for your help & efforts!
> Martin
>

Separate Project DLLs

Dear Group

Apologies for this simple question. Would be grateful if you share your
opinion on this.

I've written a web application, compiling all classes into one project
DLL. Now I wonder if there are performance / resource advantages if I
compile some classes into separate DLLs and reference them instead. Any
articles, information on this? Advantages, Disadvantages? Will it slow
down the application if it has to reference a DLL?

Thanks very much for your help & efforts!

MartinPerformance isn't a factor...Disadvantage? You have 2+ dlls floating around
which might make it harder to maintain (assuming you are shipping a product,
which you likely aren't). Advantages? Better organization, reuse, less
bloat...

There's really no reason not to...but you shouldn't just do it for the sake
of it...hopefully there's some reasoning behind why they don't belong
together...

Karl

--
MY ASP.Net tutorials
http://www.openmymind.net/ - New and Improved (yes, the popup is annoying)
http://www.openmymind.net/faq.aspx - unofficial newsgroup FAQ (more to
come!)

<theintrepidfox@.hotmail.com> wrote in message
news:1112238300.593113.237330@.f14g2000cwb.googlegr oups.com...
> Dear Group
> Apologies for this simple question. Would be grateful if you share your
> opinion on this.
> I've written a web application, compiling all classes into one project
> DLL. Now I wonder if there are performance / resource advantages if I
> compile some classes into separate DLLs and reference them instead. Any
> articles, information on this? Advantages, Disadvantages? Will it slow
> down the application if it has to reference a DLL?
> Thanks very much for your help & efforts!
> Martin
It is not a matter of performance. It is a matter of your system design. For
example, if you organize your application in presentation, business and data
access layers, you might have all forms in one project, business classes in
another project and data access classes in another project. 3 projects, 3
dlls.

Eliyahu

<theintrepidfox@.hotmail.com> wrote in message
news:1112238300.593113.237330@.f14g2000cwb.googlegr oups.com...
> Dear Group
> Apologies for this simple question. Would be grateful if you share your
> opinion on this.
> I've written a web application, compiling all classes into one project
> DLL. Now I wonder if there are performance / resource advantages if I
> compile some classes into separate DLLs and reference them instead. Any
> articles, information on this? Advantages, Disadvantages? Will it slow
> down the application if it has to reference a DLL?
> Thanks very much for your help & efforts!
> Martin

Separated DLLs for user controls

Hi,

By default VS.NET generates just one DLL contains all code behinds and
userconrols.
Is it possible to have VS.NET partitione them in their own assemblies for
granular security?

Thanks,
AliYes, you can do it a few ways

1. grab the control inside the current project and compile it using the
command line compiler, specifying the \out parameter
2. Create the control in its own project then reference it back into the
original project

"A.M" <IHateSpam@.sapm123.com> wrote in message
news:%23w0S0kZ9DHA.2524@.TK2MSFTNGP11.phx.gbl...
> Hi,
> By default VS.NET generates just one DLL contains all code behinds and
> userconrols.
> Is it possible to have VS.NET partitione them in their own assemblies for
> granular security?
> Thanks,
> Ali
I think 1 project = 1 DLL. Place them in separate projects if you want
multiple dll's.

"A.M" <IHateSpam@.sapm123.com> wrote in message
news:%23w0S0kZ9DHA.2524@.TK2MSFTNGP11.phx.gbl...
> Hi,
> By default VS.NET generates just one DLL contains all code behinds and
> userconrols.
> Is it possible to have VS.NET partitione them in their own assemblies for
> granular security?
> Thanks,
> Ali
Hi Ali,

Thanks for posting in the community!
Based on my understanding, you're wondering whether its ok to make all the
compoenent classes such as page class , usercontrol classes and other
components classes separately in different dll assemblies and which are
used in the same web application , yes?

I've review the other messages and I think A Lonely Programmer has provided
the informative suggestion, you can manually compile some of the components
classes in different dlls or even make some certain separate projects for
each dll. Then reference them in the main ASP.NET web application project.
For example:
Project A:
make page classes in dllA

ProjectB:
make Control classes in dllB

ProjectC
make other non-UI components in dllC

Main ASP.NET Project?
add all the above assebmlies as referenced and use
the classes in them.

How do you think so. Please check out those suggestions, if you have any
further questions, please feel free to post here.

Regards,

Steven Cheng
Microsoft Online Support

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

Get Preview at ASP.NET whidbey
http://msdn.microsoft.com/asp.net/whidbey/default.aspx

Separated DLLs for user controls

Hi,

By default VS.NET generates just one DLL contains all code behinds and
userconrols.
Is it possible to have VS.NET partitione them in their own assemblies for
granular security?

Thanks,
AliYes, you can do it a few ways

1. grab the control inside the current project and compile it using the
command line compiler, specifying the \out parameter
2. Create the control in its own project then reference it back into the
original project

"A.M" <IHateSpam@.sapm123.com> wrote in message
news:%23w0S0kZ9DHA.2524@.TK2MSFTNGP11.phx.gbl...
> Hi,
> By default VS.NET generates just one DLL contains all code behinds and
> userconrols.
> Is it possible to have VS.NET partitione them in their own assemblies for
> granular security?
> Thanks,
> Ali
I think 1 project = 1 DLL. Place them in separate projects if you want
multiple dll's.

"A.M" <IHateSpam@.sapm123.com> wrote in message
news:%23w0S0kZ9DHA.2524@.TK2MSFTNGP11.phx.gbl...
> Hi,
> By default VS.NET generates just one DLL contains all code behinds and
> userconrols.
> Is it possible to have VS.NET partitione them in their own assemblies for
> granular security?
> Thanks,
> Ali
Hi Ali,

Thanks for posting in the community!
Based on my understanding, you're wondering whether its ok to make all the
compoenent classes such as page class , usercontrol classes and other
components classes separately in different dll assemblies and which are
used in the same web application , yes?

I've review the other messages and I think A Lonely Programmer has provided
the informative suggestion, you can manually compile some of the components
classes in different dlls or even make some certain separate projects for
each dll. Then reference them in the main ASP.NET web application project.
For example:
Project A:
make page classes in dllA

ProjectB:
make Control classes in dllB

ProjectC
make other non-UI components in dllC

Main ASP.NET Project?
add all the above assebmlies as referenced and use
the classes in them.

How do you think so. Please check out those suggestions, if you have any
further questions, please feel free to post here.

Regards,

Steven Cheng
Microsoft Online Support

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

Get Preview at ASP.NET whidbey
http://msdn.microsoft.com/asp.net/whidbey/default.aspx

seperate bthe dll from a project working on multiple dlls

Hi ya,

i am working on a project which includes dll's of many projects

Now i want to seperate my app , because whenever a change is made in any of the included project , i have to recompile my project.

so can anyone suggest me ....how to seperate my application.

Thanks

one Solution file for One Project file is probably the best way to do it.

But maybe i dont understand you properly.

if you have one project, and you reference say, 5 .dll files from other projects. When those projects change, all you have to do is re-compile them, your project that references those ones should not need to be re-compilled, just the new .dll should overwrite the old one.

Creating a Solution with Project Dependancies can also simplify the process, that way if you need to mod a .dll your referencing, you already have the project in your solution.

HTH,

mcm