Geeks With Blogs
AzamSharp Some day I will know everything. I hope that day never comes.
First of all you should not refer from the Class Library Project to the Web Application Project actually it works the opposite way. It is always a good practice to put all your business logic code in a separate project called Class Library Project. This way it will be much easier to port the library to different venders. If you are putting all your business logic classes inside the App_Code folder of the Web Application then you have to transfer the whole application to the vender when you only needed to transfer the business logic. Anyway, If you have make this mistake and trying to make a reference from a Class Library Project to the Web Application Project then Visual Studio would not show you the project name under the "Add Reference" dialog box. You need to manually add the App_Code.dll of the Web Application to your Class Library project and then you will be able to use the classes defined in the App_Code folder. Once again if you just started the project then I highly recommend using a separate project for all the business logic. Posted on Thursday, April 13, 2006 1:43 PM | Back to top


Comments on this post: Referencing from a Class Library Project to the Web Application Project (NOT A GOOD IDEA)

# re: Referencing from a Class Library Project to the Web Application Project (NOT A GOOD IDEA)
Requesting Gravatar...
The bad thing is that you need to delete the assembly after making changes in the Web Application and so on. In other words just use a separate project for the Business Logic.
Left by AzamSharp on Apr 13, 2006 1:55 PM

Your comment:
 (will show your gravatar)


Copyright © Mohammad Azam | Powered by: GeeksWithBlogs.net