Jump to content
Xtreme .Net Talk

Derek Stone

*Gurus*
  • Posts

    1910
  • Joined

  • Last visited

Everything posted by Derek Stone

  1. HTML doesn't support input masks, which means ASP.NET doesn't unless you code a custom JavaScript solution.
  2. You can't. The page can't magically query a database without knowing values that haven't been entered at the time the page is compiled. You'll need to enter the values and then post back, querying the database then.
  3. Whether or not spreading your control over a few files is the right or wrong way of doing things from a consolidation standpoint, you're going to find out that your control is far less customizable and scalable if you place it into a sole assembly. Regardless, things to look into if you plan on consolidating: Page.RegisterClientScriptBlock() WebControl.ApplyStyle() WebControl.MergeStyle()
  4. Visual Studio .NET has many built-in debugging capabilities: breakpoints, the Debug object, the Trace object, etc. Consult the .NET SDK Documentation for help on debugging. It's far too extensive of a topic to discuss here.
  5. http://www.asp.net/IEWebControls/Download.aspx?tabindex=0&tabid=1
  6. Web services don't have user interfaces. You'll need to debug your application using an alternative method.
  7. It all depends on what RDBMS you want to use. There's Microsoft SQL Server, MSDE (free version of Microsoft SQL Server), Oracle, Microsoft Access, MySQL and many others. You'll need to pick one that you have or can make available prior to us being able to help you.
  8. You can interop with a .NET assembly via COM using a CCW (COM-callable wrapper), however you can not create a standard DLL unless you use C++, whether managed or unmanaged.
  9. I just recently wet-sanded one of my '79 Mazda RX-7's. It's certainly cheaper to do it by hand, but quite a bit more work. Now I just need to flare out the rear fenders and slap on a base coat before winter hits.
  10. Web Services aren't going to be very flexible when it comes to general access to the database server. Web methods are best used for specific tasks, and really weren't intended for use as general re-route proxies to the underlying data. If you're limiting yourself to specific tasks (adding/removing customers, shipments, etc.) then Web services are exactly what you're looking for, but I couldn't imagine developing a database application without direct access to the database server for testing, security and ease-of-development.
  11. Get NAnt and schedule one of its build scripts using the Windows Task Scheduler.
  12. Because having two properties that do the same thing is just dumb. Things change. Either brace the changes that are in fact beneficial, wether they appear to be or not, or switch back to Visual Basic 6. The fact that the Text property is now unified across controls as opposed to Visual Basic 6, which used both Text and Caption properties, makes a number of tasks a bit easier on the developer. I mean really... how much work would it take to execute a find/replace on ".Caption". Come on now...
  13. Configuring IPSec and port-forwarding on the database server and internal router would be far more appropriate. You're going to need to set up port-forwarding to enable Web services over TCP/IP anyway, so I see no point in taking a round-about solution to an otherwise simple problem.
  14. They changed things because of a little known concept called inheritance.
  15. That's a browser problem, not an ASP.NET problem. I believe if you add a nosave attribute to the input field several of the major browsers will not cache the passwords. Generally speaking though, you should simply fire anyone that uses a password manager. Period.
  16. It will act like a session, since that's what that attribute describes. And yes, it will consume a small portion of memory for each user. If you want to use cookies use cookies, not sessions.
  17. There is no direct support for this in ADO.NET. Either use ADO or upgrade to a more robust database.
  18. This is a known issue with .NET 1.0 and Internet Explorer. I don't remember if .NET 1.1 includes a fix. You'll have to check and see.
  19. Well, you need to use either a cookie or a session hash located in the URI's query string or path info. There aren't any other alternatives. Amazon.com uses the session hash method which I find to be a more compatible solution to cookies, although harder to work with from a development standpoint.
  20. Sessions will not work if cookies are disabled on the client unless the session configuration (in web.config) has the attribute "cookieless" set to true. Generally speaking, that isn't an advisable solution. And yes, it's fine to use session variables on a site with 100 concurrent users. Just be wise as to what you store in each user's session. Keep the data as compact as possible.
  21. Is CreateFile() returning a valid handle? Check that for starters.
  22. No, since the page doesn't exist anymore (for all intents and purposes) in an object format. You'll need to pass the form collection data manually or use the Server.Transfer method to redirect the ASP.NET worker process to render "webpage2" with the query string and form collection of "webpage1". This means that "webpage1" will never be rendered, although the client will assume it was since the worker process essentially replaced the compilation of the requested page with the compilation of a page designated by the developer.
  23. Glad to see you got it. I honestly didn't have a damn clue as to exactly what you wanted. Oh well. :)
  24. Start a thread, pass it a delegate and have it return when the DataSet has been loaded.
×
×
  • Create New...