VS.NET
and
Windows DNA Architecture
(Layers versus Towers)
Problem:
Windows DNA Layers and "Code Behind" eliminates "Spaghetti
Code", HOWEVER this introduces "Scattered Code"
Answer:
Use the "Code Behind" and "Self-Describing" techniques to
their fullest.
Build Towers, not Layers. However implement IDE changes below to still keep
the advantages of layers. NOTE: See Second Answer
also
Suggested IDE Changes:
Make Changes to IDE to visually indicate DNA components and separation,
while also including a COM Options Menu that updates Identical Objects created
on several different web pages to minimize maintenance.
(Question: How about if I have 2 .aspx pages that use the same business component?
Do I have to write the Code in both places? Sounds like lot of extra code to
write!)
Suggested IDE Code View with Enhanced
Collapsable Icons (with notes)
Suggested IDE Code View with Enhanced
Collapsable Icons (Clean view)
Master Undo Button as Opposed to
using Source Safe:
Just save a second copy of "changes to everything" for the "last
30, 60, or 90" days into another directory called "/undo" while
leaving everything else the same. And also have a History Files like the other
Graphics programs like in Fireworks and Dreamweaver. If I want to revert back
to the "old way". People have a lot more faith in a Undo button as
opposed to installing another application (it's about marketing.) Plus, hard
drive space is cheap anyway. Also have the option to Bookmark a History Entry
to know which Undo Step is the last Good One. And put the Date and Time for
Each Undo Step.
Second Answer:
Drill Down support from HTML code to C# and VB object code. This will help navigate
through the Spaghetti code explained in the First Answer
Chat Rooms built into VS.NET like
Diablo 2 Chat Rooms
One button on the default toolbar to open up a chat room that already preconfigured
to like mIRC or NetMeeting. This will speed the time to talk to other programmers
or even help telecommuters talk with others in their team or manager.
A Much Easier and more Intuitive
Solution Explorer for VS.NET:
Solution Explorer in VS.NET Beta 1 needs a lot of work on how it handles files
for a web site between your local copy and the Remote(or Server) Copy. It's
very difficult to understand and use, not to mention very confusing. SO, here
are my changes. Basically I am just adding the nice and easy to use feature
of Dreamweaver into Solution Explorer WITHOUT interfering with it's current
way of doing things, (which is a complete Nightmare by the way) These changes
ECHO one of Microsoft's Chief Goals of "Just Copy the Files over and it
runs". 1-25-2001
Please bear with me in the drawings and web pages as I am already having a hard time communicating these suggestions and the logical reasoning behind them, much less getting Microsoft to actually incorporate them to VS.NET
THIS entire site are only opinions and suggesting to the new VS.NET of which
I look forward to working with.