Comments on: Productive weekend http://twwilliams.com/blog/2006/02/19/productive-weekend/ Discovering and learning Wed, 03 Dec 2008 22:55:56 +0000 http://wordpress.org/?v=2.6.1 By: alex http://twwilliams.com/blog/2006/02/19/productive-weekend/#comment-8320 alex Fri, 13 Apr 2007 21:04:49 +0000 http://twwilliams.com/blog/2006/02/19/productive-weekend/#comment-8320 hi nice site. hi nice site.

]]> By: Scott Hanselman http://twwilliams.com/blog/2006/02/19/productive-weekend/#comment-17 Scott Hanselman Fri, 24 Feb 2006 08:38:16 +0000 http://twwilliams.com/blog/2006/02/19/productive-weekend/#comment-17 Ya, I've been working with Richard. His problem is some new tightening of security in 2.0 along with the JIT dialog being configured for developer, not runtime. I very much suspect the same problem for you. Ya, I’ve been working with Richard. His problem is some new tightening of security in 2.0 along with the JIT dialog being configured for developer, not runtime. I very much suspect the same problem for you.

]]> By: Tommy Williams http://twwilliams.com/blog/2006/02/19/productive-weekend/#comment-14 Tommy Williams Thu, 23 Feb 2006 14:37:03 +0000 http://twwilliams.com/blog/2006/02/19/productive-weekend/#comment-14 I was having a problem before switching to Whidbey -- in fact, it was the hung threads that prompted me to switch over in the first place. I'm pretty sure I remember Richard saying that he's running it under .NET 2.0. I was having a problem before switching to Whidbey — in fact, it was the hung threads that prompted me to switch over in the first place. I’m pretty sure I remember Richard saying that he’s running it under .NET 2.0.

]]> By: Scott Hanselman http://twwilliams.com/blog/2006/02/19/productive-weekend/#comment-13 Scott Hanselman Thu, 23 Feb 2006 07:36:06 +0000 http://twwilliams.com/blog/2006/02/19/productive-weekend/#comment-13 Ya, I just saw that. Are you both running DasBlog under .NET 2.0? Ya, I just saw that. Are you both running DasBlog under .NET 2.0?

]]> By: Tommy Williams http://twwilliams.com/blog/2006/02/19/productive-weekend/#comment-12 Tommy Williams Thu, 23 Feb 2006 05:10:16 +0000 http://twwilliams.com/blog/2006/02/19/productive-weekend/#comment-12 Here's the strange thing: I'm not the only one reporting the problem with dialog boxes popping up with dasBlog. Richard Tallent is saying the same thing: <a href="http://www.tallent.us/blog/CommentView.aspx?guid=b0b95dcf-7fb5-4788-bcb9-5269db0df294" title="Need New Blogging Software" rel="nofollow">Need New Blogging Software</a> Here’s the strange thing: I’m not the only one reporting the problem with dialog boxes popping up with dasBlog. Richard Tallent is saying the same thing: Need New Blogging Software

]]> By: Scott Hanselman http://twwilliams.com/blog/2006/02/19/productive-weekend/#comment-11 Scott Hanselman Thu, 23 Feb 2006 05:05:18 +0000 http://twwilliams.com/blog/2006/02/19/productive-weekend/#comment-11 Oops...I messed up the tags in that comment. Sorry. I meant to link <a href="http://www.hanselman.com/blog/HowToTurnOffdisableTheNETJITDebuggingDialog.aspx" rel="nofollow">here</a> Oops…I messed up the tags in that comment. Sorry.

I meant to link here

]]> By: Scott Hanselman http://twwilliams.com/blog/2006/02/19/productive-weekend/#comment-10 Scott Hanselman Thu, 23 Feb 2006 05:03:25 +0000 http://twwilliams.com/blog/2006/02/19/productive-weekend/#comment-10 That's really odd. It's physically not possible for DasBlog to "throw a dialog" so I suspect your ISP didn't have their JIT Debugger settings correct - . As far as error handling in DasBlog, we have a global error handler that dumps the complete call stack to the logs. We don't have a custom thread pool, we just use the ASP.NET one. If the JIT Debugger is incorrectly configured and a dialog pops up then ALL threads wait. That's an IIS Debugging thing, again, not DasBlog. For what it's worth, we have extensive SPAM controls in place now. I get about 30,000 legit hits a day and block over 10,000 spam attempts. Either way, I'm sorry you had a bad experience! It sucks. That’s really odd. It’s physically not possible for DasBlog to “throw a dialog” so I suspect your ISP didn’t have their JIT Debugger settings correct - .

As far as error handling in DasBlog, we have a global error handler that dumps the complete call stack to the logs. We don’t have a custom thread pool, we just use the ASP.NET one.

If the JIT Debugger is incorrectly configured and a dialog pops up then ALL threads wait. That’s an IIS Debugging thing, again, not DasBlog.

For what it’s worth, we have extensive SPAM controls in place now. I get about 30,000 legit hits a day and block over 10,000 spam attempts.

Either way, I’m sorry you had a bad experience! It sucks.

]]> By: Tommy Williams http://twwilliams.com/blog/2006/02/19/productive-weekend/#comment-9 Tommy Williams Thu, 23 Feb 2006 04:53:57 +0000 http://twwilliams.com/blog/2006/02/19/productive-weekend/#comment-9 No, I didn't file a bug. I don't think I know enough about the problem to file a reasonable bug -- just what I've been able to piece together after many server restart requests. It was on a hosted site, so I only had FTP access. Basically, though, it was just enough of a push to send me back to the comfortable (for me) world of command-line-hosted sites. I love being able to ssh to the site and to control the Web server by editing .htaccess files. It's what I "grew up" with. I've been fascinated by Wordpress's plug-in model since I first heard about it and the broad community of people writing these plug-ins is encouraging. No, I didn’t file a bug. I don’t think I know enough about the problem to file a reasonable bug — just what I’ve been able to piece together after many server restart requests. It was on a hosted site, so I only had FTP access.

Basically, though, it was just enough of a push to send me back to the comfortable (for me) world of command-line-hosted sites. I love being able to ssh to the site and to control the Web server by editing .htaccess files. It’s what I “grew up” with.

I’ve been fascinated by Wordpress’s plug-in model since I first heard about it and the broad community of people writing these plug-ins is encouraging.

]]> By: Omar Shahine http://twwilliams.com/blog/2006/02/19/productive-weekend/#comment-8 Omar Shahine Thu, 23 Feb 2006 04:45:44 +0000 http://twwilliams.com/blog/2006/02/19/productive-weekend/#comment-8 Did you file a bug? We've been fixing a whole slew of bugs latley. Or were there other reasons you switched? Did you file a bug? We’ve been fixing a whole slew of bugs latley. Or were there other reasons you switched?

]]> By: Tommy Williams http://twwilliams.com/blog/2006/02/19/productive-weekend/#comment-3 Tommy Williams Mon, 20 Feb 2006 17:32:03 +0000 http://twwilliams.com/blog/2006/02/19/productive-weekend/#comment-3 PHP hacking isn't new to me. I was quite adept back in the days before I started working at Microsoft. I was hired here, in fact, for my experience with Apache, Perl, and FreeBSD. Of course, that was PHP3.... It felt very nice to put together some RewriteRules again. PHP hacking isn’t new to me. I was quite adept back in the days before I started working at Microsoft. I was hired here, in fact, for my experience with Apache, Perl, and FreeBSD. Of course, that was PHP3….

It felt very nice to put together some RewriteRules again.

]]> By: Pat http://twwilliams.com/blog/2006/02/19/productive-weekend/#comment-2 Pat Mon, 20 Feb 2006 15:54:04 +0000 http://twwilliams.com/blog/2006/02/19/productive-weekend/#comment-2 Welcome to PHP-hacking hell my friend. But yeah, I was wonder wth was going on, with your bold resolutions for the new year and all ;-) Welcome to PHP-hacking hell my friend. But yeah, I was wonder wth was going on, with your bold resolutions for the new year and all ;-)

]]>