G
GS
I am still a novice in vb .net 2. actually in vb.net period. please bear
with me.
Problem:
I often found myself refereeing to common utility like setStatus and logs on
the form, and the application title in some messages.
Question. how should I best avoid that ?
my kludge is using fully qualified name My.Forms.myformname.whatever
also, I found myself with some rather large sub(procedure) dealing with
specific spreadsheet. When I tried breaking it down I found myself faced
with either
- passing row and column numbers, and the performance hit of creating /
releasing extra com objects to deal with excel objects or
-used non cls compliant parameter passing
Your input will be much appreciated
Background Info :
I am dealing with an application that has a main form with a few tab pages.
I am trying to partition the code so I can have more manageable smaller
modules or classes.
I expect there will be in excess of 10,000 lines of the code in the version
1. in version 2 probably 20,000..
for the full blown version, I expect around 40,000. the application is
basically a tracking, analysis, and reporting system that also interfaces
with a number of external web No they are not soap based. some are heavily
dependent on jscript for formatting html. worse, the application also have
to load saved html pages, historical spreadsheets for extraction
The application is to extract information from a number of external
website, store result in database and format spreadsheets, charts for
reporting.
Ideally I would like classes or modules dealing with different object
..
with me.
Problem:
I often found myself refereeing to common utility like setStatus and logs on
the form, and the application title in some messages.
Question. how should I best avoid that ?
my kludge is using fully qualified name My.Forms.myformname.whatever
also, I found myself with some rather large sub(procedure) dealing with
specific spreadsheet. When I tried breaking it down I found myself faced
with either
- passing row and column numbers, and the performance hit of creating /
releasing extra com objects to deal with excel objects or
-used non cls compliant parameter passing
Your input will be much appreciated
Background Info :
I am dealing with an application that has a main form with a few tab pages.
I am trying to partition the code so I can have more manageable smaller
modules or classes.
I expect there will be in excess of 10,000 lines of the code in the version
1. in version 2 probably 20,000..
for the full blown version, I expect around 40,000. the application is
basically a tracking, analysis, and reporting system that also interfaces
with a number of external web No they are not soap based. some are heavily
dependent on jscript for formatting html. worse, the application also have
to load saved html pages, historical spreadsheets for extraction
The application is to extract information from a number of external
website, store result in database and format spreadsheets, charts for
reporting.
Ideally I would like classes or modules dealing with different object
..