Search results

You could do it the old way... just make a hidden form field with a value in it, then at the top of your code check for it. If it's blank, it's not a postback. If it's the value you placed in the form field, then it's a postback... because the definition of a postback is a form submit. -Dave

Don't worry about search engines... they'll figure it out. You can have a wacky URL for a product in your inventory and most search engines today will figure it out. They have to -- people don't write websites with search engines in mind! -Dave

In ASPX in-line script, use "~/count.dat" In VB code-behind, use Page.ResolveUrl("~/count.dat") -Dave

No, no, I agree totally... it was just a joke. Learning programming concepts is the key and, like you said, everything becomes simple syntax after that. Learn what you like, and like what you learn... -Dave

Okay. Well, since this is indexed, I'll provide a simple example just in case someone else wanted to know: ASPX code: File to upload: &nbsp; <input id="uploadedFile" type="file" name="uploadedFile" runat="server" size="50" class="newInput">&nbsp; <asp:RequiredFieldValidator...

You're better off writing an upload section to your website. It'll be prettier, you can verify the names of files, place them where you want to, etc... If you're using ASP.NET, I can give you a simple examlpe. -Dave

Many people in Europe, and the rest of the world, have seen us the way they do well before Bush came around. It's all cyclical... it goes around and around... people love us, hate us, love us, hate us... usually love us when they come over for free medical treatment to separate their conjoined...

If you know ASP well, you will fall in love with ASP.NET. It's too indepth to cover in this limited arena -- I would just recommend getting a couple of books and using it. In my mind, there is absolutely no reason to use classic ASP for any new projects you're starting. Once you start using...

Classic ASP, not ASP.NET? That's a shame... I think, if you were to begin a new project in ASP, it would certainly be in ASP.NET. -Dave

Yash, that is absolutely the funniest thing I've ever heard you say. Why don't we turn this into a positive thread...: Speaking of "under construction" notices, have you seen any good 404 pages I can model after? Once, I saw a 404 page that looked like the back of a milk container -- a...

Sounds like you want help with a homework assignment, am I right? Maybe you can supply a bit more information about what you need help on and we can point you in the right direction without giving away the answer.... -Dave

Woah! I didn't realize the price tag on that one! -Dave

Really? Gee, and I thought vulgarity would have won the outcast vote. -Dave

Edited by moderator: Let's Keep these forums friendly Censorship rocks.

You are quite the rule fellow, Alfred. These people are here to help -- you should assume their questions are a necessary aspect in answering your question. After all, you're the one who doesn't know how to accomplish this, not them. Maybe they need to know the name of your domain in order to...

Search for this problem in these forums... it should be fairly straight forward. Turn ON .Net services in HSphere for your domain. If you're using VS.Net, compile your application, copy *.aspx, web.config, global.asax, etc., and create a BIN directory off your root and put the project's DLL...

Looks like a lot of stuff that can readily be accomplished using native .Net code. However, you can just get their .Net version anyway and place their library in your own directory and you're done... no Com components to install and register. -Dave

Look in the paper and other job-hunting resources in your area. Comapre the jobs for .Net and CF. Learn the one with more jobs! ;) -Dave

It means you have an error but your web.config file has a setting which prevents the server from revealing the details of the error to any Joe User who might be using your website. Edit the web.config file located in the root of the directory and change the configuration option to OFF. -Dave...

Oh yeah, that's a common mistake -- make sure the FROM address is valid. Plenty of times there is a silly invalid character or something like that in the FROM field and people miss it. The SMTP server will choke on it. Good catch, Patrick. By the way -- did you catch the bug in the mail...