|
-
May 18th, 2006, 10:05 AM
#1
asp include files to asp.net
I'm trying to migrate an existing 3-tier application to asp.net 2.0 (with VB.net), and would like to know the best way to handle the existing include files. These include files mostly consist of just a handful of sub routines or functions per each include file. Do I just convert each of these into their own little class and put them in app_code (and put an imports statement on the page that wants to use that class's functions/subs)? ...or do I convert them to just plain Modules (declaring as Public Module instead of Public Class)? What is the most efficient way to do this?
Thanks
...also, why doesn't VS 2005 allow you to select a Module when adding an item to your project, like VS 2003 did?
Last edited by jaklotz; May 18th, 2006 at 10:33 AM.
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|