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

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

TB, in the MySQL website, there's a mySql ADO.NET provider. Meaning that you
can use it to access mySql natively from .Net. You can still use the OleDb
or ODBC providers too if you want.
Check it out: http://www.mysql.com/products/connector/net/

- Sergio


"TB" <tbpostbox-googlegroups@xxxxxxxxx> wrote in message
news:eaWTn63bFHA.3492@xxxxxxxxxxxxxxxxxxxxxxx
> Thank your very much for bothering to answer this "old newbie".
>
> I will follow your advice. Particularly I will desect some of the sample
> projects on www.asp.net to learn how code-behind truly works. Actually it
> sounds like an interesting concept, but I supose (without knowing anything
> yet) that there are several degrees of code-behind depending on how
> puritanic you are or how much time you have left to finish a job. I guess
> that it also difficult for .NET developers to resist the temptation to get
> dirty and throw in a bit of inline code here and there just to get a
project
> out of the door.
>
> I will also take a serious look at the book you suggest.
>
> Another question, now that I got you "on the line": Is it possible to make
> VS.NET work perfectly / natively / transparently with MySQL?
>
> TB
>
>
> "Jeffrey Todd" <Me@xxxxxxxxxxxxx> wrote in message
> news:eM04AAsbFHA.1040@xxxxxxxxxxxxxxxxxxxxxxx
> > 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: question about playlist
    ... I have a dynamic playlist, playlist_1.asx, created by a php script from a ... the mysql table contain information about: ... movie near to the playing movie, and when change the movie, contextually ... Change the information in the *database* table, or in the HTML table? ...
    (microsoft.public.windowsmedia.server)
  • Re: HTML pages are faster then php?
    ... Lamp Lists wrote: ... as far as I know html page will download faster then the same page made with php getting the same info from mysql, ... let's pretend we are building php/mysq based website of one football team. ...
    (php.general)
  • Re: Strange MySQL Problem...
    ... Whatever you 'print' in your CGI script is part of the Response, ... If the response is an HTML page, the Content-Type should say text/html, NOT image/jpeg. ... One doesn't "upload an image into mysql": one uploads an image, and some script on the server saves the image into mysql database. ...
    (comp.lang.python)
  • Development Tools
    ... I recently finished a project which involved HTML, Javascript and PHP along ... The only development tool was FrontPage. ... this is not a diatribe against this development tool or Microsoft. ... Javascript and PHP along with MySQL was only partially ...
    (alt.php)