Third Party Control

I am trying to implement the SmartScroller control (free control from http://www.strengthtechnologies.com/) into my WebApp. It is supposed to retain scroll position after a postback. I'm having difficulty adding it to my project however. When I try to add the SmartScroller to my toolbox I get this message...

"There are no components in 'C:\Inetpub\wwwroot\webapp\bin\StrengthControls.Scrolling.dll' that can be placed on the toolbox.

I've also tried to register it manually...

<%@dotnet.itags.org. Register TagPrefix="ccl" Namespace="StrengthControls.Scrolling" Assembly="StrengthControls" %>

but I get a parser error: File or assembly name StrengthControls, or one of its dependencies, was not found.

I've included StrengthControls.Scrolling.dll in the bin directory of my webapp just like it says to do on the http://www.strengthtechnologies.com/ site so I have no clue why this isn't working. Any help would be much appreciated.Why not just using Smartnavigation property?
I've heard that SmartNavigation is unreliable and I've encountered strange problems when I've implemented it in the past.

Thread abort error - REVISITED

I'm periodically getting "Thread Abort Error" errors thown from my web
app. My app will throw like 5 of these and will work normally again.
I'm thinking it is because my worker process was recycling so it
aborted all the threads. My question is, How can I stop it?Don't put any code after Response.Redirect(). That's it. Those Thread
Abort Exceptions will go away.

If you have so much as a return statement after a
Response.Redirect(?,true);, you'll run the risk of seeing these
exceptions. Regardless of what you do, you shouldn't be sweating them.
They're completely harmless.

Jason Kester
Expat Software Consulting Services
http://www.expatsoftware.com/

--
Get your own Travel Blog, with itinerary maps and photos!
http://www.blogabond.com/

Thread abort error - REVISITED

I'm periodically getting "Thread Abort Error" errors thown from my web
app. My app will throw like 5 of these and will work normally again.
I'm thinking it is because my worker process was recycling so it
aborted all the threads. My question is, How can I stop it?Don't put any code after Response.Redirect(). That's it. Those Thread
Abort Exceptions will go away.
If you have so much as a return statement after a
Response.Redirect(?,true);, you'll run the risk of seeing these
exceptions. Regardless of what you do, you shouldn't be sweating them.
They're completely harmless.
Jason Kester
Expat Software Consulting Services
http://www.expatsoftware.com/
Get your own Travel Blog, with itinerary maps and photos!
http://www.blogabond.com/