Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>What you're describing sounds like an example of the aphorism, "You can write FORTRAN in any language."</p> <p>A massive class full of static methods is often (not always) a sign that somebody just didn't "get" OOP, was stuck in a procedural-programming mindset and was trying to twist the language to do what he wanted.</p> <p>As a rule of thumb: If any method, static or instance, takes more than about 5 parameters, it's often a sign that the method is trying to do too many things at once, and is a good candidate for refactoring into one or more classes.</p> <p>Also, if the static methods are not really related, then they should <em>at least</em> be split up into classes that implement <em>related</em> functionality.</p> <p>I'm actually wondering why you'd have a "send e-mail" method at all, given that the <code>System.Net.Mail</code> namespace handles just about every case, and is configurable via the app.config/web.config file, so you don't need to pass it a server name or port. Is this perchance a "notification" method - something that individual pages are supposed to call out to in order to send one of several "standard" messages based on templates with various values filled in, and certain headers/footers automatically added? If so, there are a number of designs for this type of interaction that are much easier to work with than what you seem to have inherited. (i.e. <a href="http://msdn.microsoft.com/en-us/library/system.web.ui.webcontrols.maildefinition.aspx" rel="nofollow noreferrer">MailDefinition</a>)</p> <p><strong>Update:</strong> Now having seen your comment that this is being used for exception handling, I think that the most appropriate solution is an actual <em>exception handler</em>. There are a ton of resources on this. For ASP.NET WebForms, I actually took the one Jeff Atwood wrote years ago, ported it to C# and made a few changes (like ignoring 404 errors). There are a number of good links in <a href="https://stackoverflow.com/questions/55961/exception-handling-in-net-web-apps">this previous question</a>.</p> <p>My preference these days is just to treat exception handling (and subsequent e-mailing of exception reports) as a subset of logging. <a href="http://logging.apache.org/log4net/index.html" rel="nofollow noreferrer">log4net</a> has an <a href="http://logging.apache.org/log4net/release/sdk/log4net.Appender.SmtpAppender.html" rel="nofollow noreferrer">SmtpAppender</a> that's quite capable, and you can configure it to only be used for "fatal" errors (i.e. unhandled exceptions - in your handler, you just make a <code>LogFatal</code> call).</p> <p>The important thing, which you'll no doubt pick up from the SO link above and any referenced links, is that there are actually two anti-patterns here - the "miscellaneous" static class, and <em>catching exceptions that you don't know how to handle</em>. This is a poor practice in .NET - in most cases you should only catch application-specific exceptions that you can recover from, and let all other exceptions bubble up, installing a global exception handler if necessary.</p>
    singulars
    1. This table or related slice is empty.
    1. PODesign Perspective: Static Methods vs. Classes
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USCommunity
    1. USAaronaught
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PODesign Perspective: Static Methods vs. Classes
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COYou pretty much described what it is for - it is used as a way to notify the development team of any crashes. Basically, the method is called within any catch blocks (so, it's called relatively frequently). Past developers wanted to quickly be able to e-mail with only one line of code - hence the static method.
      singulars
      1. PO
      1. USJasCav
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload