T
talkingwall
Hi - I was hired to trouble shoot ASP 3.0 report performance for a
company in Scottsdale. When I got here I discovered that the classic
asp 3.0 reports are actually running in an IFrame embedded in a dot net
nuke ( http://www.dotnetnuke.com )page.
I cannot see any evidence where programming has been done to facilitate
co-managed sessions between .net and classic asp and I believe
something is required.
While I've been able to solve a couple of obvious problems, we still
have some reports that will not cooperate. Mainly, closing the browser
will often result in orphaned SPIDs on the SQL Server that are
executing a stored procedure. The call to the stored proc is ado 2.8
(not ado.net) via the ASP running in the IFrame.
Is there anyone here with the expertise that can tell me fairly
conclusively that running asp 3.0 inside a .net portal is going to
cause similar problems?
Many thanks
Mark
company in Scottsdale. When I got here I discovered that the classic
asp 3.0 reports are actually running in an IFrame embedded in a dot net
nuke ( http://www.dotnetnuke.com )page.
I cannot see any evidence where programming has been done to facilitate
co-managed sessions between .net and classic asp and I believe
something is required.
While I've been able to solve a couple of obvious problems, we still
have some reports that will not cooperate. Mainly, closing the browser
will often result in orphaned SPIDs on the SQL Server that are
executing a stored procedure. The call to the stored proc is ado 2.8
(not ado.net) via the ASP running in the IFrame.
Is there anyone here with the expertise that can tell me fairly
conclusively that running asp 3.0 inside a .net portal is going to
cause similar problems?
Many thanks
Mark