Server Activated ServicedComponent and Config Files

re: Server Activated ServicedComponent and Config Files

Paul — Mon, 29 Dec 2003 14:08:00 GMT

Hi Florin, this feature works only for winxp and win2k3. Do you know if exists something similar under win2k ?. Thanks.

re: Server Activated ServicedComponent and Config Files

Florin Lazar — Sat, 03 Jan 2004 02:19:00 GMT

Paul - Unfortunately Win2K doesn't support per app config files because Win2K doesn't have Application Root Directory.

re: Server Activated ServicedComponent and Config Files

Dante — Mon, 12 Apr 2004 14:01:00 GMT

Hi folrin, i've been trying this for some time and it just won't work, i have winXP prof, do i need to install service pack 2 for this to work? thanks

re: Server Activated ServicedComponent and Config Files

Florin Lazar — Wed, 14 Apr 2004 06:54:00 GMT

Dante, on XP you need at least COM+ QFE Rollup #6 (QXP 6) to be able to use this feature. You have two options: 1. Contact Microsoft Support to obtain the rollup or 2. Wait for SP2 for XP to be released.

re: Server Activated ServicedComponent and Config Files

Cibra — Tue, 18 May 2004 13:49:00 GMT

Under W2k3, the files can be renamed as <ServerApplicationName>.manifest and <ServerApplicationName>.config. Unfortunately this solution doesn't work under windows xp

Enterprise Services and app.config

Impersonation Failure — Mon, 31 May 2004 08:06:00 GMT

All out-of-process COM applications by default are executed using the %SystemRoot%\System32\dllhost.exe surrogate process. What this used to mean that calling System.Configuration.ConfigurationSettings.AppSettings[

re: Server Activated ServicedComponent and Config Files

Kash — Wed, 04 Aug 2004 11:16:00 GMT

Hi i have similar problems
I'm developing mmc SNAP-in in vb6 using snapin designer,
snain needs to interact with database ,
database interaction code is written in vb.net,

to use that .net assembly i register it for COM interoperability, And it successfully run in vb form project , And all config file settings successfdully obtained when runnin vb6 project exe.
Now i use that same vb.net assembly in snapin by registering for COM interoperability.
( Snapin creates .ocx file)
Now when i load snapin in mmc, it woun't find any config file, even though i renamed app.config as dllhost.exe.config
I'm using win2k
Any type of help highly appreciated

Exporting an Enterprise Service with a manifest

Hackward and Foreword — Thu, 13 Jan 2005 21:20:00 GMT

Exporting an Enterprise Service with a manifest

Hackward and Foreword — Thu, 13 Jan 2005 21:21:00 GMT

re: Server Activated ServicedComponent and Config Files

Oren — Tue, 26 Apr 2005 12:32:24 GMT

Hi there do you have any idea how to overcome the problem under the W2K environment any idea will be highly appreciated THNAKS

re: Server Activated ServicedComponent and Config Files

Roni Burd — Wed, 27 Apr 2005 19:03:40 GMT

For win2k I copied a code fragment that was suggested of ADVANCED DOTNET list.(I'm not sure from whom, and modified 4 lines of code)

I post the source code because so maybe it can be useful to others. Basically all you have to do is inherit for ServicedComponentEx.

Good luck!

[AttributeUsage(AttributeTargets.Class)]
public class ServicedComponentExProxyAttribute : ProxyAttribute, ICustomFactory
{
private ProxyAttribute _base;
private Type currentType;
static AppDomain appDomain = null;

public ServicedComponentExProxyAttribute()
{
_base = (ProxyAttribute)typeof(ServicedComponent).GetCustomAttributes(typeof(ProxyAttribute),false)[0];
}
public override MarshalByRefObject CreateInstance(Type serverType)
{
return _base.CreateInstance(serverType);
}
public override RealProxy CreateProxy(ObjRef objRef,Type serverType,object serverObject,Context serverContext)
{
return _base.CreateProxy(objRef,serverType,serverObject,serverContext);
}
Assembly ResolveHelper(object o, ResolveEventArgs rargs)
{
if ( currentType.Assembly.FullName == rargs.Name )
{
return Assembly.LoadFrom(currentType.Assembly.Location);
}
else
{
return null;
}
}
MarshalByRefObject ICustomFactory.CreateInstance(Type serverType)
{
if ( AppDomain.CurrentDomain.FriendlyName == "myappdomain" )
{
return ((ICustomFactory)_base).CreateInstance(serverType);
}
else
{
if ( appDomain == null )
{
System.AppDomainSetup appDomainSetup = new AppDomainSetup();
appDomainSetup.ApplicationBase =
Path.Combine(Path.GetPathRoot(serverType.Assembly.Location), Path.GetDirectoryName(serverType.Assembly.Location));
appDomainSetup.ApplicationName = "complus";
appDomainSetup.ConfigurationFile = serverType.Assembly.GetName().Name + ".exe.config";
appDomain = AppDomain.CreateDomain("myappdomain",null,appDomainSetup);
}
ResolveEventHandler reh = new ResolveEventHandler(this.ResolveHelper);
currentType = serverType;
AppDomain.CurrentDomain.AssemblyResolve += reh;
MarshalByRefObject mbr = (MarshalByRefObject)appDomain.CreateInstanceFromAndUnwrap(serverType.Assembly.Location,serverType.FullName);
AppDomain.CurrentDomain.AssemblyResolve -= reh;
currentType = null;
return mbr;
}
}
}
[ServicedComponentExProxyAttribute]
public class ServicedComponentEx : ServicedComponent
{
public ServicedComponentEx()
{}
}

Configuration file for .NET objects running under COM+ 1.5

Giulio Vian's WebLog — Wed, 27 Jul 2005 14:23:43 GMT

From http://blogs.msdn.com/florinlazar/archive/2003/12/04/41369.aspx:
setting the Application Root Directory...

re: How about using Transaction?

Sam — Tue, 02 Aug 2005 23:17:21 GMT

On XP/2003, application.manifest and application.config work well as long as the component is being called by a client without a transaction context.

If you want to call the same component from a client under a new transaction context (this is easy to do by the way), then the component does not seem to be able to access the app.config file anymore.

I have some code that illustrates my point if anybody is interested. I would appreciate any suggestions/workarounds to make this thing work.

re: Server Activated ServicedComponent and Config Files

Brian Russell — Wed, 17 Aug 2005 19:23:19 GMT

Or you could just call AppDomain.CurrentDomain.SetData("APP_CON- FIG_FILE", settingsFilePath);

...

Using Log4Net from a COM+ Application

George V. Reilly's Technical BLog — Tue, 29 Aug 2006 04:08:19 GMT

I spent far too much time on Friday trying to make log4net work in a COM+ application. Someone else had