Hello, This may sound overly optimistic. I'm building a website where I do expect really heavy traffic, images, and even some video. What software bundle do you recommend for this kind of use? -Hosting your site with Windows, ASP.Net, MS SQL Server ? -LAMP? -Others...? I have little expertise in servers, so your insight is much appreciated
Homero Rivera
Posts
-
Building a website, expect a lot of traffic, images, etc. What software bundle to use? -
ALERT, some dumbass fortune-teller is bombing the Q&ANo hard feelings if that is not an available feature for me yet.
-
ALERT, some dumbass fortune-teller is bombing the Q&AALERT, some dumbass fortune-teller is bombing the Q&A section. Anybody on site?
-
BUG: Just answered question and didn't get my 10 ptsNEVERMIND, THE 10 JUST GOT DELAYED, THANKS! BUG: just answered a question and didn't get my 10. Thanks, you don't really have to reimburse me those 10, just work it out please.
-
C# Code generation .net 4.5The truth is you can compile C# programs on CommandPrompt (aka DOS). And with .NET Framework you can create text files with any extension including cs (for C#). And also with .NET Framework you can issue CommandPrompt commands. So, in theory you can make a C# program that creates c# programs and also that runs them.
-
Submit changes from a form back to a databaseNo, that will not help. In fact, it will prevent you from submiting the data on the first attempt if it is enclosed by the if "(!IsPostBack".
-
Submit changes from a form back to a databaseI hope this helps: A page will be a postback if a user submits something (either by click or any other mechanism) and you use the same page C# / VB after what triggered the submision. Therefore, using a button on a form will cause it to be a postback, and the if (!IsPostback... will enter into effect, preventing you to get to the desired code. If you want to prevent a user from clicking the same button or triggering the same mechanism, at the end of your code you can disable the button with something as Button1.Enabled = false; which is the most common I've seen. That way, the user won't be able to make a second change with that particular button.