Sometimes it helps opening your dll in some dependency viewer [1]. Not
very likely, but your dll might be dependent of a non-exisisting or
inaccessible release build of some other dll.
[1] http://www.dependencywalker.com
===
This list is hosted by DevelopMentor® h
Thanks, but the assembly is definitely getting loaded.. I'm printing
trace info using its members, and fuslogvw has nothing bad to say about
it.
--Dan
-Original Message-
From: Unmoderated discussion of advanced .NET topics.
[mailto:[EMAIL PROTECTED] On Behalf Of Patrick Steele
Sent: Frid
Check the Assembly Binding Log Viewer to see if it logged a problem
locating your assembly (fuslogvw.ex). It stands for "Fusion Log
Viewer" because "fusion" is the name of the assembly binding engine.
Original Message
From: [EMAIL PROTECTED]
To: ADVANCED-DOTNET@DISCUSS.DEVELOP.COM
Subje
Hi all,
In my development project I'm loading a dll and instantiating a class in
it using Assembly.CreateInstance(classname), just fine. In the
installed release version however, the dll is getting loaded but the
same CreateInstance() returns null with no exception thrown.
I've tried swapping
Only if your context data object implements ILogicalThreadAffinative. Also
note that in some cases (remoting to an out of appdomain object), your
ILogicalThreadAffinative data in CallContext can be destroyed (removed from
the CallContext) if an error occurs in the remoting framework. This isn't
ver
Thanks for the replies. What I didn't want was to use System.Web so I
created my own Context using CallContext (similar to what HTTPContext does).
What I don't know is does CallContext travel if I call a COM+
(ServicedComponent) object?
-Original Message-
From: Unmoderated discussion of
> though you need to reference the web assembly by then.
> FWIW I suspect asp.net is using threadlocal storage for its context.
If you bother to reference the web assembly, you could use the static
methods CallContext.GetData and CallContext.SetData.
Reflector shows that HttpContext.Current is be
> The problem is, ASP.NET uses a thread pool so I'm no guaranteed to get the
> same thread each time I connect. I was wondering how HTTPContext works. If I
> put something in there with HTTPContext.Item is there a way to retrieve it
> later down the road (another DLL).
>
yes, it will, though you ne
You can use the static property HttpContext.Current.
--
Scott
http://www.OdeToCode.com/blogs/scott/
-Original Message-
From: Unmoderated discussion of advanced .NET topics.
[mailto:[EMAIL PROTECTED] On Behalf Of Roni Burd
Sent: Friday, April 01, 2005 9:37 AM
To: ADVANCED-DOTNET@DISCUSS.D
Hi, I've been wondering how could I pass and object from layer to layer with
threads. I need this in conjunction with ASP.NET. Here my problem:
I've been using NHibernate to manage my persistence. The issue is I need to
open and close a NH Session with each request (AKA session-per-request
patte
Graeme,
The comments following this article [1] on TheServerSide.NET appear to be
discussing exactly the same issue you are reporting, and it looks like it is
related to the use of an XmlSerializer by the logging block. More
importantly, someone seems to have provided a solution.
[1] Microsoft Pa
11 matches
Mail list logo
