Fwd: 7 new messages in 4 topics

Today's topics:
==============================================================================
TOPIC: Multitier application and Datagrid
http://groups.google.com/group/DotNetDevelopment/browse_thread/thread/c707b6a9e6186220?hl=en
==============================================================================

== 1 of 1 ==
Date: Thurs, May 8 2008 11:04 am
From: Cerebrus


One word - "ObjectDataSource".

On May 8, 6:09 pm, André Wagner <andre....@gmail.com> wrote:
> Hello,
>
> I'm trying to understand how can I write a application in three layers
> and use a datagrid on a object.
>
> For example, let's say I have a table on my database (COUNTRIES) with
> the fields ID and DESCRIPTION. And I have a class Country that would
> connect to this table:
>
> class Country
> {
>     public int ID { get; set; }
>     public string Description { get; set; }
>
> }
>
> Now, I know I can create a data source out of this object and connect
> it to a datagrid. But how then can I handle things updates, inserts
> and deletions in the datagrid?
>
> Thank you in advance,
>
> André




==============================================================================
TOPIC: ASP.net 2.0 need to grab file name from fileupload control to put in a
form on another page
http://groups.google.com/group/DotNetDevelopment/browse_thread/thread/0be5c7d0aea5048e?hl=en
==============================================================================

== 1 of 1 ==
Date: Thurs, May 8 2008 11:06 am
From: Cerebrus


Assuming you know how to retrieve the name and other properties of the
file selected through the FileUpload control, it boils down to a
problem of transferring information from one page to another. There
are about a thousand (okay, maybe a little less ! ;-) ) ways to do
this.

On May 8, 9:52 am, pauld <pauld...@hotmail.com> wrote:
> Hi-
> I need to put the name of a file  that a user has uploaded into a text
> field on a form on another page for insertion (along with a bunch of
> other form fields) into a database. Is there an easy way to do this?
> I'm sure there is but I got the end of semester brain death....
>
> All i need is the "photoname.png" or whatever- no path, no validation,
> no size limit.
>
> FTR- this is a fileupload control being implemented on a page built
> with Expression 1.o and VS2005 using asp.net 2.0 and VB. It allows
> users to upload a photo whose file name is included with other db
> data.
>
> TIA-
> Paul




==============================================================================
TOPIC: How to use both base() and this() in constructor?
http://groups.google.com/group/DotNetDevelopment/browse_thread/thread/0291e38413e9a36a?hl=en
==============================================================================

== 1 of 2 ==
Date: Thurs, May 8 2008 11:14 am
From: Glenn


That's why you use ":this()" so that your inherited class will call
your "no parameter" constructor to initialize all the variables for
your inherited class.  That constructor then calls base() to
initialize the base class' parameters.  That's why there's a
combination of this() and base() in the class constructors.

Where do you see three classes?

...Glenn

On May 7, 2:15 pm, Joshua Russo <joshua.rupp...@gmail.com> wrote:
> The example you give may work in some situations but it could get
> tricky, in that you may not want the same logic if you directly
> instantiate the base class. Even if the base class is abstract it may
> not have the properties you want to set in your child class and
> creating 3 classes seems to be a bit much.




== 2 of 2 ==
Date: Thurs, May 8 2008 11:32 am
From: "Crisatunity (blog.crisatunity.com)"


The concept to get yourself square on is that you can't call another
constructor of the same class in the body of a constructor.  That's
why you use the outside the body syntax as Glenn demonstrated.

On May 7, 1:15 pm, Joshua Russo <joshua.rupp...@gmail.com> wrote:
> That's cool, I've never used :this()
>
> The example you give may work in some situations but it could get
> tricky, in that you may not want the same logic if you directly
> instantiate the base class. Even if the base class is abstract it may
> not have the properties you want to set in your child class and
> creating 3 classes seems to be a bit much.
>
> On May 7, 12:48 pm, Glenn <ke4ktza...@gmail.com> wrote:
>
>
>
> > Better yet, see my previous message on this.
>
> > Using "public A(int ai):this()" accomplishes the same thing.
>
> > If class A is your base class, use "public A(int ai):base()".  This
> > insures that all inherited classes that construct with "base(int ai)"
> > will also execute "base()".  Put all of your initialization calls
> > there and you aren't duplicating your initialization calls.
>
> > ...Glenn
>
> > On May 7, 9:22 am, Joshua Russo <joshua.rupp...@gmail.com> wrote:
>
> > > So can you do the following?
> > > class A
> > > {
>
> > > public A()
> > > {
> > >   ...
>
> > > }
>
> > > public A(int ai)
> > > {
> > >   this(); // to trigger the constructor above?
> > >   ...
>
> > > }
> > > }- Hide quoted text -
>
> > > - Show quoted text -- Hide quoted text -
>
> - Show quoted text -




==============================================================================
TOPIC: Application architecture advice needed
http://groups.google.com/group/DotNetDevelopment/browse_thread/thread/ef960ec0a4e5b9de?hl=en
==============================================================================

== 1 of 3 ==
Date: Thurs, May 8 2008 11:44 am
From: "Crisatunity (blog.crisatunity.com)"


Distinctly not succinct.  More focus, perhaps more than one thread.
You are going to get either no response or wild-ass unfocused
responses to your blog-style posts.

On May 7, 8:13 pm, DevoRevolution <DevoRevolut...@gmail.com> wrote:
> You do have a point, my question was relatively broad and vague,
> partly because I didn't want to bias the responses in any particular
> direction.  Perhaps also I was a bit too quick to throw out the "f"
> word, my apologies.
>
> I do not expect you to write my application for me, and I have been
> performing a great deal of research, as well as consulting with
> professionals within my organization and within my circle of friends.
> I would comment that asking for general suggestions about topics to
> research, reference sources or commercial products that might help me
> meet my needs is a far cry from doing my job for me, and I probably
> should have presented my original question to more clearly request
> specifically that information.  Incidentally, I have worked for 3
> Fortune 500 companies for a total of about 10 years, just not
> doing .NET and n-tier architecture design.
>
> I think at this time we're leaning mostly towards a 4-tier solution
> using Javascript, ASP.NET, VB.NET and SQL Server.  Most of the
> applications we would be converting are relatively small Access 97
> databases, with data in either Access 97 or SQL Server back ends, many
> of which have import and export interfaces primarily using flat files,
> FTP and DTS.  The primary goal of my entire project is to make sure
> that our future architecture framework is consistent and easily
> maintainable across all applications, and I'm trying to do as much
> legwork as possible before we start coding to ensure that.
>
> To give you more details as to what we are working on, we want to try
> to incorporate as many of the following concepts as we can into the
> overall framework we use (this is the condensed version):
>
> 1.  Common code to handle logins, password changes, lockouts, auditing
> all login/logout activity, account creation, activation, deletion, and
> modification (and auditing thereof).
>
> 2.  Common code for auditing all edits on all fields on all databases
> - possibly using XML diffgrams.  Ideally this would be automatically
> built into the data access layer so that no additional code would need
> to be written except in unusual cases.  This would also lend itself to
> having automatic history reports showing edit history at different
> levels (field, record, parent record) which could be shared across
> applications.
>
> 3.  Common rules and methodology for handling interfaces with external
> programs - want to move away from DTS which is the tool we've used in
> the past.
>
> 4.  Common reporting interface with tools designed so that custom ad-
> hoc reporting can be more easily created for each application, as well
> as the ability for users to store and retrieve their own personal ad-
> hoc reports or publish them (given sufficient authority) so that other
> users can access.
>
> 5.  User communication tool both within the application and via email
> so that programs can generate messages as needed and convey responses
> back to the sender
>
> 6.  Relatively robust data dictionary so that data validation and
> calculation formulae can be stored and their changes tracked over
> time.  The idea would be to have the data access layer contain classes
> that understand how to use the data dictionary, so that the business
> layer could inherit the metadata for each of their data elements
> without having to individually code them for all fields in all
> databases.  In addition, the dictionary would define security levels
> for individual fields, so that SSN's for example would be hidden by
> default unless the user specifically requests to view them, and each
> viewing would be logged automatically in all applications.  Ideally
> this could be programmed to automatically configure custom web
> controls to handle validation (I was looking at PeterBlum's suite as
> one option).
>
> 7.  Common interface and practices for help within the application
> (tooltips, url's to further information, etc), as well as user and
> training manuals and technical documents.  Ideally the data dictionary
> could be used to automatically have this be presented in the user
> interface without needing much additional coding.
>
> 8.  Common error handling procedures and methodology which logs
> application details when errors occur as well as sending messages to
> admins/programmers as needed.
>
> I have already been designing a lot of these elements in my head for a
> few years before I even started this job - I was just hoping (and have
> to assume) that at least some of them existed in some prepackaged form
> by a vendor out there so that I don't have to reinvent the wheel.
>
> One of the databases we will be converting is used to track patient
> applications for charity care coverage.  Several dozen users enter
> patient demographics, and track details such as patient income,
> assets, and other coverages they might have, then render a decision
> based on several sets of complex criteria.  There are about 10
> interfaces (both import and export) with external systems, all
> currently via flat files and DTS, several of which automatically
> generate emails.  Users very frequently request ad-hoc reporting,
> which the system currently does not support at all (i.e. I write
> queries to give them the information they requested).



== 2 of 3 ==
Date: Thurs, May 8 2008 11:51 am
From: "Andrew Badera"


My numbers do not correspond to your numbers.

1. Get familiar with Microsoft Patterns & Practices. Get to know the
Provider patterns, particularly the MembershipProvider and RoleProvider. Get
to know the Logging and ExceptionHandling Application Blocks. Get to know
the Data Access Application Block.
2. Get to know Active Directory. It's easy.
3. Get to know both remoting and web services. Trust me, they, too, are
easy. This means getting to know serialization a bit as well, which can be a
bit kinky.

No, there's probably no prebuilt suite out there that is going to meet all
your needs in a cost-effective and low-headache fashion. Get through #1, #2,
#3 and I think most of your questions will be answered.

4. Spend time reading MSDN, this list, CodeProject, Coding Horror, Joel on
Software, Nielsen & Norman, CodePlex and CodeGallery and Google Code, the
CodePlex forums, Channel9.




On Wed, May 7, 2008 at 9:13 PM, DevoRevolution <DevoRevolution@gmail.com>
wrote:

>
> You do have a point, my question was relatively broad and vague,
> partly because I didn't want to bias the responses in any particular
> direction.  Perhaps also I was a bit too quick to throw out the "f"
> word, my apologies.
>
> I do not expect you to write my application for me, and I have been
> performing a great deal of research, as well as consulting with
> professionals within my organization and within my circle of friends.
> I would comment that asking for general suggestions about topics to
> research, reference sources or commercial products that might help me
> meet my needs is a far cry from doing my job for me, and I probably
> should have presented my original question to more clearly request
> specifically that information.  Incidentally, I have worked for 3
> Fortune 500 companies for a total of about 10 years, just not
> doing .NET and n-tier architecture design.
>
> I think at this time we're leaning mostly towards a 4-tier solution
> using Javascript, ASP.NET, VB.NET and SQL Server.  Most of the
> applications we would be converting are relatively small Access 97
> databases, with data in either Access 97 or SQL Server back ends, many
> of which have import and export interfaces primarily using flat files,
> FTP and DTS.  The primary goal of my entire project is to make sure
> that our future architecture framework is consistent and easily
> maintainable across all applications, and I'm trying to do as much
> legwork as possible before we start coding to ensure that.
>
> To give you more details as to what we are working on, we want to try
> to incorporate as many of the following concepts as we can into the
> overall framework we use (this is the condensed version):
>
> 1.  Common code to handle logins, password changes, lockouts, auditing
> all login/logout activity, account creation, activation, deletion, and
> modification (and auditing thereof).
>
> 2.  Common code for auditing all edits on all fields on all databases
> - possibly using XML diffgrams.  Ideally this would be automatically
> built into the data access layer so that no additional code would need
> to be written except in unusual cases.  This would also lend itself to
> having automatic history reports showing edit history at different
> levels (field, record, parent record) which could be shared across
> applications.
>
> 3.  Common rules and methodology for handling interfaces with external
> programs - want to move away from DTS which is the tool we've used in
> the past.
>
> 4.  Common reporting interface with tools designed so that custom ad-
> hoc reporting can be more easily created for each application, as well
> as the ability for users to store and retrieve their own personal ad-
> hoc reports or publish them (given sufficient authority) so that other
> users can access.
>
> 5.  User communication tool both within the application and via email
> so that programs can generate messages as needed and convey responses
> back to the sender
>
> 6.  Relatively robust data dictionary so that data validation and
> calculation formulae can be stored and their changes tracked over
> time.  The idea would be to have the data access layer contain classes
> that understand how to use the data dictionary, so that the business
> layer could inherit the metadata for each of their data elements
> without having to individually code them for all fields in all
> databases.  In addition, the dictionary would define security levels
> for individual fields, so that SSN's for example would be hidden by
> default unless the user specifically requests to view them, and each
> viewing would be logged automatically in all applications.  Ideally
> this could be programmed to automatically configure custom web
> controls to handle validation (I was looking at PeterBlum's suite as
> one option).
>
> 7.  Common interface and practices for help within the application
> (tooltips, url's to further information, etc), as well as user and
> training manuals and technical documents.  Ideally the data dictionary
> could be used to automatically have this be presented in the user
> interface without needing much additional coding.
>
> 8.  Common error handling procedures and methodology which logs
> application details when errors occur as well as sending messages to
> admins/programmers as needed.
>
> I have already been designing a lot of these elements in my head for a
> few years before I even started this job - I was just hoping (and have
> to assume) that at least some of them existed in some prepackaged form
> by a vendor out there so that I don't have to reinvent the wheel.
>
> One of the databases we will be converting is used to track patient
> applications for charity care coverage.  Several dozen users enter
> patient demographics, and track details such as patient income,
> assets, and other coverages they might have, then render a decision
> based on several sets of complex criteria.  There are about 10
> interfaces (both import and export) with external systems, all
> currently via flat files and DTS, several of which automatically
> generate emails.  Users very frequently request ad-hoc reporting,
> which the system currently does not support at all (i.e. I write
> queries to give them the information they requested).
>
> >
>


--
--
--Andy Badera
http://higherefficiency.net
http://flipbitsnotburgers.blogspot.com/
http://andrew.badera.us/
http://changeroundup.com/
andrew@badera.us
(518) 641-1280
Google me: http://www.google.com/search?q=andrew+badera




== 3 of 3 ==
Date: Thurs, May 8 2008 7:01 pm
From: "Charles A. Lopez"


Sounds like a good project.

On Mon, May 5, 2008 at 4:14 PM, DevoRevolution <DevoRevolution@gmail.com>
wrote:

>
> My group is taking over a large number (about 40) of old Access 97
> databases within a large healthcare organization, and will eventually
> rewrite them all using .NET and SQL Server.  However, our developers
> have limited experience in .NET and we are trying to determine the
> best technological solutions that will allow us to reuse code and
> rewrite most of these applications with common architecture for faster
> development and easier maintenance.
>
> The primary question we are dealing with is whether to use a compiled
> executable (VB.NET <http://vb.net/>) or web architecture (ASP.NET<http://asp.net/>and javascript with
> server components in VB.NET <http://vb.net/>), or some other architecture
> or variant.
> Another option is to create a common set of middle tier utilities (if
> that is possible) and decide for each application whether the GUI is
> better developed as a .exe or web app.  Our company is primarily a
> Microsoft shop, so please hold the MS vs the World Flame War - as
> valid as that issue may be, it doesn't help us out.
>
> Given recent advances in web application technologies (Ajax, etc), it
> appears that most normal application requirements (security, interface
> elements, responsiveness, etc.) can be met in either paradigm, though
> it appears that in web development, additional work is required to
> accomplish things that are automatic or simpler in a .exe.  However,
> executables can be problematic for installation and upgrades on locked-
> down windows images, and may have network security access issues as
> well.  In addition, there seems to be a general perception by users
> and managers that web applications are somehow better than
> traditional .exe's.
>
> The biggest question for us with this decision is development cycle
> time and maintainability - how does going from a VB.NET <http://vb.net/>compiled
> application to an ASP.NET <http://asp.net/> application affect those
> aspects of
> development?  Are there any useful articles we could read about
> programs developed in both and comparisons between them?
>
>
> The second issue is that we are hoping to find a widely used framework
> of some sort that would assist with or perform many of the functions
> we will need in all of these applications, such as data access and
> management (and do we use XML, LINQ, or ADO?), data validation, edit
> logs, data and application security, user account management,
> reporting, messaging, documentation, error handling and reporting, and
> external interfaces.  Ideally we would like to write (and maintain) as
> little code as possible.  If we can't find anything suitable, we will
> probably try to write one ourselves.
>
> We own a dedicated web server that currently has .NET 2.0 on it, but
> we can upgrade to 3.5 if needed, and a SQL Server 2000 dedicated
> server.  Our users are all on Windows 2000 or XP, but we need to plan
> for future Vista use as well.
>
> Thanks in advance for any advice
>
> >
>


--
Charles A. Lopez
charlesalopez@gmail.com

Bachelor of Arts - Computer Science
New York University
Computing Since 1980