Problems with Chapter 3

saille · January 17th, 2007, 09:19 PM

I guess I can continue using Visual Web Developer 2005, by simply adding a Reference to the CustomEvents.dll from the sample code.

bobhagan · January 17th, 2007, 11:12 PM

Quote:

quote:Originally posted by saille
I am wondering if, like me, Steve is using Visual Web Developer 2005.
That would explain why he's having trouble with the Custom Events, since Visual Web Developer 2005 doesn't allow you to compile your code into assemblies.
I was hoping to use only Visual Web Developer 2005 to work through the book, but it looks like I may have to shell out for Visual Studio 2005, unless there's anonther way

I do not understand why Custom Events should have to be compled anyway - this seems like a workaround for a flaw in ASP.NET. Can anyone shed some light on that?

You can download the C# Express and if you want to make changes to the dll, compile from that. On the other hand, since customevents is already compiled, as below, you can simply reference it.

englere · January 18th, 2007, 07:43 PM

If you guys are looking at the web events, you might want to consider that the most important events are likely related to the DB being down. And trying to log that kind of problem in the DB is futile. I personally like logging to a file because that's also friendly to web hosting environments. But if you own the servers, then the Windows Event Log has merit and you can set up third party monitoring programs to send you a page if certain events occur (like the DB being down).

In the real world, a big percentage of serious problems are related to the DB. Sometimes it's a firewall problem between the web servers and DB servers, and sometimes it's a Windows, SQL Server, or hardware problem. But whatever the cause, if the DB is down you need to spring into action!

Eric