Well first this is the wrong thread. You should be posting in the .NET forums. Secondly, .NET does not preserve any session information across application domains. In so far as components you have 2 options.
1)Create a Class library with all the functionality, compile it and you now have a DLL that you can move from application to application. This is a more difficult way if you intend for your component to handle the interface as you will have to write functions to output HTML and such. If you are just using it for functionality, this is the best way. (This also requires a certain knowledge of your keywords, private, public, static, etc)
2)User Controls. Like the first option I use these extenstively because they are, essentially, components. I code them once and then can drag and drop them onto pages when I need to reuse their functionality.
I should point out that in Visual Studio you can add a reference to any component you wish so a Component in application directory A can be reference by an application in directory B but, behind the scenes what happens is, Visual Studio copies that reference to your bin directory of your current web app.
hth
-------------------------
I will only tell you how to do it, not do it for you.
Unless, of course, you want to hire me to do work for you.
^^Thats my signature
|
