Does autocomplete work when in HTML mode (no code behind page) 1

[DSect]

Question:

If I make a simple ASPX page and type some VB in between <script> tags, the autocomplete feature seems to not work (where it shows the methods & properties of an object).

Does VS not autocomplete on a one-page .ASPX file as compared to how it works in something like a codebehind page?

Thanks!

 

[Isadore]

DSect: If you are in VS I would suppose the best approach would be to maintain your aspx.vb (code behind) as well as your aspx (html) pages separately -- my experience with VS is that the autocomplete materials are available when editing the aspx.vb code behind page (and html autocomplete in the aspx page).

My first question however is my point, if you are in VS, why not use both aspx and aspx.vb pages? Certainly it can be done (and is) but to take full advantage of VS I would split the two pages and keep them separate.

 

[DSect]

I have no prob using a sep. .VB page, as all of the things I've done so far made it easier..

But - In so many of the online examples for simple stuff (like a data read, view thru datagrid), they always do it in SCRIPT tags on the same page..

I'm sure it doesn't impact performance one bit, but I was wondering:
1. If autocomplete for VB worked when in HTML mode.
2. I was going to make a bunch of simple, one-page pages and it would be nice to have just one file per page.

No prob at all using the codebehind. I dig it.. It saves me so much frickin time..

I just love the autocomplete so that I know that I have an object ref'd correctlym, etc..

Thanks for your input!

 

[Isadore]

DSect: I'm in between laptops, just trying to get the new one up so haven't installed VS yet -- I spent the first 6 months in dot NET buidling all pages in NotePad (combining both script and html -- of course, works well, but no advantage as one would have in VS). The kingpins here at Tek-Tips would remind me often that I should avoid "spaghetti" programming; and I have -- sometimes taking the long road early on helps speed things up later -- you just can't have your cake and eat it too I suppose. Sure, many of the exmaples in textbooks are done in single aspx pages -- perhaps to avoid copywrite laws when duplicating VS details - not sure -- but also easier to demonstrate -- in effect, you just cut and paste the script out and presto, you're in code behind -- but organizing class structure, functions, etc, become much easier in the latter.

If you're page is simple, say a few minor subroutines, nothing wrong with it - indeed, one of the web sites I built is entirely made in notepad, you can take a look (and if you like I'll share any of the page's code with you, just drop a line. The NotePad site can be seen at:

http://frontpage.auburn.edu/icaae/index.aspx

The big payoff moving away from this was the consolidation of OLEDb routines, data drilling, etc...