Re: an old geezer running visual studio for the first time



These 3 suggestions will hopefully help a lot:

1. Consider developing your aspx and ascx files in FrontPage, Dreamweaver,
Notepad, or whatever is your favorite HTML and/or CSS editor - and limit
your use of VS.NET to (1) all programming work (code-behind logic) and (2)
launching you application for testing purposes. VS.NET 2003 most definitely
NOT the place to write HTML - so no need for you to think about grid vs flow
layouts. Reason being that VS.NET 2003 will rewrite your HTML for you -
often with disastrous results. This link from a Microsoft insider explains:
http://blogs.msdn.com/MikhailArkhipov/archive/2004/05/16/132886.aspx
The upshot is that many of us use FrontPage or Dreamweaver for all
HTML-specific work (i.e., ASPX and ASCX file development) and use VS.NET
only for programming/code-behind work. The way I develop is that I keep a
copy of Dreamweaver running at all times along side VS.NET 2003 - and switch
between the two. One last point here is that VS.NET 2005 - due out in
November or so - is expected to no longer have the HTML rendering and
management issues that VS.NET 2003 has.

2. Get this book: Programming ASP.NET - by Dino Esposito - Microsoft Press.
It puts everything in context - IMHO ideal for your situation. It's not a
step-by-step tutorial, but it is more valuable because tells you how to
understand ASP.NET.

3. Familiarize yourself with the starter kits at the following link:
http://www.asp.net/Default.aspx?tabindex=8&tabid=47. I'd especially
recommend that you download and disect the Commerce starter kit. The starter
kits are complete ASP.NET Web applications and include all source code -
which is very readable and well-documented. The Commerce starter kit is one
of the simpler - so it would be a good starting point as it incorporates
many fundamentals.

-HTH

-JT



"TB" <tbpostbox-googlegroups@xxxxxxxxx> wrote in message
news:eTCWZ3qbFHA.2212@xxxxxxxxxxxxxxxxxxxxxxx
> Hi all:
>
> If you think that the following comments are absolute amateurish, then
> please bear with me, or simply skip this thread.
>
> A couple of months back I made the decision to initiate a gradual upgrade
> of my web programming skills from Classic ASP / VBS to ASP.NET / VB.NET.
>
> While the study of the language differences and all the new features in
> .NET has so far not been a traumatic experience, I am a bit shell-schocked
> after installing and running for the first time Visual Studio .Net (2003
> edition).
>
> Until now I have programmed everything in the old-fashioned way, i.e. with
> a bare minimum of tools: a simple editor for coding, a bit of Frontpage
> for page layout, and my browser to see the results when running the page
> against a local instance of IIS.
>
> I have done quite a bit web programming, developing anything from yellow
> pages to accounting programs.
>
> But when I ran VS.NET for the first time, I simply didn't know where to
> start.
>
> The program appears to be a sort of Swiss-knife approach to programming,
> eliminating the need for external apps. During the past couple of years I
> have developed my own little collection of helpers which I use during
> development.
>
> VS.NET creates files for "project mangement". My project management
> normally consists notes and diagrams. My reusable code (subs and
> functions) is kept in separate files, which I either reference to or
> cut/paste - depending on the situation.
>
> I normally use a GUI tool (Frontpage for example) to generate a page
> layout. In VS.NET I am met with the question whether I want the designed
> to be grid-based or flow-based.
>
> Finally, I discovered that VS.NET saves code and html in different files.
> I am used to keeping everything together, grouping functions, subs etc
> above the <head> tag, and then insert code snippets between <% %> tags.
> This approach seems to be frowned upon by VS.NET.
>
> Am I an old-fashioned guy? No, because I have made the desicion to move to
> .NET, although a bit late perhaps. But I would like to find a book, a
> tutorial, anything that can teach this old geezer to use a new toy which
> apparently could improve my productivity.
>
> Any advice / comments from people who may or may not have been through the
> same process would be most welcome.
>
> Thanks
>
> TB
>
>
>


.



Relevant Pages

  • Re: an old geezer running visual studio for the first time
    ... Consider developing your aspx and ascx files in FrontPage, Dreamweaver, ... > definitely NOT the place to write HTML - so no need for you to think about ... Familiarize yourself with the starter kits at the following link: ... >> I have done quite a bit web programming, ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Website creating software
    ... >> definitely not a MSFT lover, but FP is closing the gap fast to DWMX. ... > dhtml and css, but also some features with regular html. ... One could say that about FrontPage in the ... past, not really Dreamweaver,. ...
    (Debian-User)
  • Re: web development tools-Dreamweaver vs. Frontpage 2003
    ... packages for editing HTML. ... > To find the best Newsgroup for FrontPage support see: ... > |> you can't do in Dreamweaver, ... > |>> able edit the code created with Dreamweaver. ...
    (microsoft.public.frontpage.client)
  • Re: web development tools-Dreamweaver vs. Frontpage 2003
    ... just as DW "tools" don't do anything an experienced developer can't do w/ notepad if needed ... To find the best Newsgroup for FrontPage support see: ... |> you can't do in Dreamweaver, ... |> HTML is HTML. ...
    (microsoft.public.frontpage.client)
  • Re: web development tools-Dreamweaver vs. Frontpage 2003
    ... > you can't do in Dreamweaver, ... >> web site with drop-down menus and mouse-over effects, will Frontpage ... > HTML is HTML. ... But the bulk of a web site is ...
    (microsoft.public.frontpage.client)