Hello Hermawih,
As Juan has mentioned, there is no need to regsiter .NET managed
assembly(as COM do). For ASP.NET application, those private (no
strong-named) assemblies can simply be put in "bin" sub dir while
strong-named assemblies can be put in GAC. And the problem in your
scenario is caused by some classes defined in App_Code class, so I don't
think this is related to your deploy steps.
BTW, there is a 'web deployment project' for ASP.NET 2.0 that can help make
application precompilation and deploy more convenient, you can try this to
see whether the problem still remains.
#Visual Studio 2005 Web Deployment Projects
http://msdn2.microsoft.com/en-us/asp.net/aa336619.aspx
and still as I mentioned previously, if possible, you can try creating a
simplified project(with just a necessary page and the class in App_code
dir) which can repro the problem. You can send it to me (through the email
in my signature by removing "online") so that I can test it locally.
Sincerely,
Steven Cheng
Microsoft MSDN Online Support Lead
This posting is provided "AS IS" with no warranties, and confers no rights.