Deploying ASP.NET Application with Enterprise Libraries

  • Thread starter Thread starter kirby.matt
  • Start date Start date
K

kirby.matt

When deploying an ASP.NET application which uses the Enterprise
Libraries, can I just deploy the application files, including the bin
folder which contains all of the application dll's and Enterprise
LIbrary dll's, and then run the InstallServices.bat file? Are there any
other steps involved or is it that easy? Thanks.

Matt
 
Read in blogs/info below, and you'll figure out how to deploy with~out the
InstallServices.bat.



Common Build Properties were changed from Default:

http://blogs.msdn.com/tomholl/archive/2005/02/18/376187.aspx?Pending=true


If you are deploying to an environment where the instrumentation cannot be
used,
it's pretty easy to disable it, but you will need to recompile the code.
Luckily all the instrumentation code is wrapped around conditional
compilation directives,
so you won't need to edit any source files directly.
Just go into the Project Properties dialog for the Common project,
and under Configuration Properties\Build,
find the Conditional Compilation Properties property
and remove ;USEWMI;USEEVENTLOG;USEPERFORMANCECOUNTER (or
any combination of these that you don't want).
Once you recompile, the relevant instrumentation code will be disabled.
Of course, it is still possible to configure the Logging &
Instrumentation Application Block to use WMI or Event Log,
so make sure you also choose appropriate settings for your environment
if you are using that block.



http://channel9.msdn.com/wiki/default.aspx/Channel9.EnterpriseLibraryFAQ
Open up the EnterpriseLibrary.sln and modify the Configuration
Properties\Build\Conditional Constants
of the EnterpriseLibrary.Common project.
Remove the USEWMI;USEEVENTLOG;USEPERFORMANCECOUNTER constants.
By removing these constants,
all of the internal Enterprise Library instrumentation will be disabled.
Recompile.
 
Back
Top