Integrating Prototype and ASP.Net to create the next generation of web applications
November 11th, 2008 . by Loris
- SQL Server: you can use the command:
DBCC SHOWCONTIG (@TABLENAME) to display paging statistics about a table (MSDN article)
- C#: Use
ConfigurationManager.GetSection() to read any section of your web.config or app.config (from my StackOverflow question)
- You can use only one SQL query per
OleDbCommand! The OleDb provider does not support chaining SQL Queries with ";"
- ASP.Net’s ListBox control does not support the
<optgroup> tag!
- In SQL Server CE, you cannot
SELECT TOP n. The syntax is SELECT TOP(n), but can only be used starting from version 3.5 (StackOverflow) .
- 64bit madness: If you’re referencing a COM assembly in your .Net application, you should compile it for 32 bit machines, or it will fail silently (but putting a vague error message in the event log) when run on a 64bit edition of Windows.
The same applies if you’re referencing a ComVisible .Net assembly in your VB6 application (don’t ask :)).
If you’re on ASP.net, it gets even nastier.
- You can change a .net application to always run in 32 bit without recompiling it, using the
CorFlags utility from the .net SDK (via Simon Green’s blog).
Posted in findings |
Leave a Reply