migration issue tracker starter kit

tufillaro — Thu, 14 Feb 2008 19:17:29 GMT

This is not a commercial announce and I don't promote myself for consulting or similar jobs.
It's possible migrate issue tracker starter kit from
Microsoft visual 2002 to 2003 to 2005 to 2008?
Consequently
it's possible migrate it from
asp.net version 1.x to 2.0 ?
In my experience the answer is
yes
so i confirm that everyone can make it (if I was able to do it...)

What I have done
I used the C# version and this has an heavy impact
Not is the same thing make it by the visual basic version
Some things are very easy by VB (single statement without term line, automatic correction etc.)
other are very complex (manage event custom, pointer, formally OO etc.)

this the state of art

ASP NET 3.5
64 bit

VISTA 64 BIT AND WINDOWS SERVER 2003 R2 SP2 64 BIT
IIS 7.0 and IIS 6.0
SQL Server 2005 64 bit SP2
Oracle 8.x, 9.x, 10,x (this version 64 bit)
DB2 (32 bit version / 64 Version)
MySql 5.x in fedora 8.x 32/64 bit
Microsoft access (not 2007 version)
the engines db are easy (?) extensible by the instrumentation of
Microsoft data access block that together asp.net 2.0 drives
- the elimination of collection (substitute by List<class>)
- the elimination of management connection garanteed by
asp.net structure of web.config and the advanced features of
microsoft data application block that makes possible the complete indipendence
of the Business layer
So in this version you have not a
accessdatalayer class
oracledatalayer class
sqldatalayer class
db2dtalayer class
but only 2 (two) file class for BLL layer
and the functions that manage the call to the data layer don't need to change
(the files remain the same one forever)

No limit in memory and resource terms (application limits = operating system limits)
Change from user/role management to new membership architecture (2.0)
Management of user profile by new Microsoft Profile
Login change password etc all managed by asp.net membership

Use of the masterpage paradigma (no separately managed header, footer, placeholder an so on)
menu asp.net
gridview (no datagrid)
objectsource
wizard asp.net 2.0 for creating new project
use of on fly compilation (asp net directory with source file no DLL)
Change from style css to skin
bridge (use linked) with time tracker application
Heavy elimination of several pages and metadata code
Heavy elimination of code ( 30 % respect to the start )
in microsoft sql server (data layer) use of some new functionality
in oracle 10.x use of specifically asp net 2.0 features

these are the new features

memebership and role asp.net 2.0 with external / internal management

profile (language, cosmetic look, extensible etc.)

translation in five national languages at now, more in future, using the new asp.net 2.0
semi-integrated localization by resource files (no modify in the code)
(you can change only by clicking a flag and this goes into your exclusive profile and not for all users)

e-mail integrated (you can use the system for exchange information using new db tables and store procedure
and you can choose if you send mail internal and/or external)

Site map navigation (quick change scenario without using 'must' path)

change db engine on fly (without recompiling , without edit web config)

memo and use of hyperlink direct (not in a comment)

extension for attachments (from into an issue into separately document so you can search it)

encrypting data db (direct in microsoft sql server, indirect for the others)

realize a .vsi (starter kit) of the structure and the application so you can use it
to generate similar application in the first stage
with profile (main profile) you can easy transorm (in minutes) in a totally look different application
and so you can concentrate your brain on the change of flow, business and adding new functionality.

and last but not least
in 64 bit version and R2 the different OS (very different) integrates some of
the Microsoft data application block in system registered DLL as well as
the properly OS DLL
so you can use it, if you want, without copying them in application bin folder.
together the other system DLL (R2 specific) the application can live using
less less less code in it (with using the code in system DLL)
So you can use the same DLLS (one time) for all the other web application (using them)
This has a great impact on the IIS subsystem
consequently
you can tune web application tuning the system
, sql server(or your db engine), IIS : nothing other

you have not to worry after the first time : you will must not change
asp.net,
memebrship/role/profile db and policies
IIS
db DLLS
with delegating the management to system guys (mister, gringos)

and last
the black side

I tested all in virtual environment (a single dual-core VmWare server 1.4 64 bit with on board 1 AD DC, 1 cluster 2 node sql 3 nodes WLBS all R2 64 bit and 30 workstation
I tested it for 48 hours and for total 150000 transactions (several times)
the system (virtual max 3.75 gb ram for single server) works without growing in memory (and consequently without loss of performance)
no microprocessor impact growth
but
in several times the viewstate doesn't work correctly and also you can go from a page to another with not respecting the designed path)

It's needed an evolution in the request paradigm (call a page with parameter and managed internally)
This way, that introduces also a 'vulnus' in the system, is probably caused by the strong role of several type of caching
(system cache, network cache, db primary cache, micro first level cache, iis cache asp.net cache, etc.)
It's indirect confirmed by the empiric constatation : it is random
i.e. if you repeat the same application work flow
in the same situation (similar/alike because there is a change at less in the timestamp when you operate)
you have different results : sometime the application go to correct page other times no

PS:
I will not share the code neither the structure because I simply want to encourage other people to reach better results by demonstrating that it's possible

I spent three months (not continuosly, 12 hours every day) for all, I'm fifty years old and I have 25 years of several experience as system inegration, development,design
I can tell that was not a play neither easy neither quick
but the results sincerely repay all
Good work

Issue Tracker Starter Kit

migration issue tracker starter kit