I
Icemokka
Hi,
In a month or so we start a new Project from scratch to replace our
Existing VB6 project.
There are several elements that are already fixed :
- will only use SQL Server ( minimum 2008 for filestream datatype )
- Minimum requirement is Windows XP ( so .Net 3.0/3.5 is possible )
- First Priority is a Client/Server app ( 2-tier only since always
using same DB-type, Engine-object & Userinterface )
Later on we would like to think about using a kind of .Net remoting
to allow WAN-connectivity ( Not fond of ASP.Net ). The engine-object
will be exposed to 3th party integrators.
- The language will be C#
It's a straightforward windows app that include
customers,suppliers,orders,invoices,projects,timesheets,....
For the moment we will use Crystal Reports IX for all reporting
demands.
But there are still some questions that stay open :
- Should I use the building blocks of MS ent Library?
- Should I consider ADO.Net for entities or should I create all code
myself ( since only 1 DB-type possible )
- Is it still to early to start with WPF, first release is for end
2009, begin 2010
- Is Infragistics ( has many .Net controls ) a good component builder,
are there other major componentbuilders worth mentioning?
Since i'm rather new to starting a fresh project, I could use some
help on this.
Except for the Database-structure, i'm not sure how to start.
Are there any resources available that can help my choose the right
setup for my new project?
Does anybody has any guidelines/recommandations/remarks/warnings for
me before we begin?
I know my questions are a bit general, but any info help is
welcome ...
Regards,
Sven Peeters
In a month or so we start a new Project from scratch to replace our
Existing VB6 project.
There are several elements that are already fixed :
- will only use SQL Server ( minimum 2008 for filestream datatype )
- Minimum requirement is Windows XP ( so .Net 3.0/3.5 is possible )
- First Priority is a Client/Server app ( 2-tier only since always
using same DB-type, Engine-object & Userinterface )
Later on we would like to think about using a kind of .Net remoting
to allow WAN-connectivity ( Not fond of ASP.Net ). The engine-object
will be exposed to 3th party integrators.
- The language will be C#
It's a straightforward windows app that include
customers,suppliers,orders,invoices,projects,timesheets,....
For the moment we will use Crystal Reports IX for all reporting
demands.
But there are still some questions that stay open :
- Should I use the building blocks of MS ent Library?
- Should I consider ADO.Net for entities or should I create all code
myself ( since only 1 DB-type possible )
- Is it still to early to start with WPF, first release is for end
2009, begin 2010
- Is Infragistics ( has many .Net controls ) a good component builder,
are there other major componentbuilders worth mentioning?
Since i'm rather new to starting a fresh project, I could use some
help on this.
Except for the Database-structure, i'm not sure how to start.
Are there any resources available that can help my choose the right
setup for my new project?
Does anybody has any guidelines/recommandations/remarks/warnings for
me before we begin?
I know my questions are a bit general, but any info help is
welcome ...
Regards,
Sven Peeters