Hi all,

I have a console app, written in .Net 2.0, that I need to customize
its exception logging capability. I need to output the exception log
to a text file on a specific directory determined during run time. The
log content needs to be customized as well so that probably only the
root exception message is being captured.

I thought that would have been easy to do using the Enterprise
Library. I am probably doing it wrong but it seems like I have to
customize the ExceptionHandler, TextFormatter,
LoggingExceptionHandlerData, ... etc.

I would like to know the general steps to accomplish this (i.e. which
classes to override, what to change in the configuration file from a
basic log to file configuration).

Any help will be greatly appreciated. I have been spinning the wheels
for a lot longer than I have expected already.

I created a custom installer for my web service project. It simply copies
the web.config file from the setup.exe location into the webservice
directory. It seems to be working fine. When the uninstall is run all files
are removed. So it works.

Question: Why is the installstate file in the web service directory? Is
this normal? It is removed when the uninstall is run.

Question: my installer dll (i.e. myinstall.dll) is copied to the \bin
directory. It is only needed during installation. Is there a way to get rid
of it after installation? Will this cause problems? It is removed when the
uninstall is run.

Not sure if the right people would be reading this newsgroup, but a
suggestion on future versions of the LINQ editor for dbml. It would be nice
to be able to put comments into the designer's gui interface, possibly saved
as xml comments so they can be used for code generation.

Hi,
I'm facing a problem that could be completely resolved using .policy
files, but I could not use GAC in my application.

Basically the app should follow the "Smart Client" guidelines. All the
application plug-ins (implemented as .NET assemblies) should be placed
in a common folder shared among different workstations using remote
folders. So I cannot use the GAC facilities.

Until the plug-ins are implemented as single assembly, all is working
fine. I'm parsing the remote "plugin" folder and load all assemblies
using Assembly.LoadFrom method. I'm using a single AppDomain.

The problem is coming up now that we need to write several multi-
assembly plugins. We basically need to write one or more common core
assemblies (as "infrastructure" for these plugins) that will be
referred by each plugin.
The core assemblies should be versioned and shipped bundled in each
plugin package.

I need to declare backward compatiblity in the core assemblies to:
a) avoid to have multiple version of core assemblies loaded in memory;
b) to efficiently implement an inter-plugin communication layer.