Separated DLLs for user controls

[A.M]

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

 

[A Lonely Programmer]

Yes, 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

 

[Marina]

I think 1 project = 1 DLL. Place them in separate projects if you want
multiple dll's.

 

[Steven Cheng[MSFT]]

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