Tuesday, May 24, 2005

Gent: Tuesday

Went for a very long walk around Gent.

Very interesting place. There are the famous towers of three cathedrals plus many more churches across the city. Lots of really neat alleyways and streets. Many of the buildings have remarkable faces of intricate wood, stove and iron work. Very impressive.

Gent: Tuesday morning

Lovely morning in Gent. Took a couple quick cameraphone pics from the hotel terrace:

The roundabout on the hotel street, a trolly and the trains overhead.

The other direction on the hotel's street.

Monday, May 23, 2005

Arrived in Belgium

I got into Gent, Belgium this morning for a one week visit for the European user group conference I'm attending and presenting at for work. The express flight was a little late getting to Newark, NJ so I had to rush to make the connection. Then, of course, we sat at the gate for at least 30 minutes then took a good while to get off the ground. Didn't leave there till an hour after the planned pushback. So we arrived late but it didn't really matter because we didn't have anything scheduled for when we got here.

Somehow I left home without the data cable for the camera I brought so I can't get any good pictures online till after I get home. But I have my camera phone (with infrared transfer) so I could at least get something.

View from the hotel window. The building next door blocks the side of the train station overpass that leads into the main square of Gent.

I walked into the train station and around almost every corner is some stand or shop that sells "Warme Waffles". The whole place smelled of them which made me very hungry. However, I can't eat until dinner later on with a contact of ours here. I'm definately going to have to see about getting a waffle for dessert (apparently that's how it works).

Saturday, May 21, 2005

Added old posts.

I added posts from my old blog (there weren't many). It was reasonably painless apart from trying to figure out what the real times where that posts were made. The blog pluggin I was using was saving the times wrong. But they didn't seem to be consistantly wrong so I had to do a little estimating or just make them up. Oh well. They're here now, so I just have to figure out if I'll publish directly to my site or have my site pull the feed and show the results. I suppose the latter would be better.

GeekDork.Blog = New Blogger()

I broke down a got a new blog. I had tried a blog pluggin on my site, but it just wasn't working out the way I had hoped. So I decided to give Blogger a try. I was about to start looking into importing previous blog posts but just now noticed that I can change the date and time of new posts. So I should be able to put in my old posts without much difficultly. Good thing I don't have hundreds of them! Hopefully this bog will work out better than the old one.

Monday, May 16, 2005

ASP.NET Application reset behavior

In the March 2005 asp.netPRO magazine, there is an article by Dino Esposito discussing accessing compile-time code programmatically. He explains how code files are generated from the parsed markup files and then get compiled into temporary assemblies in the ASP.NET temp folder(s). Although he makes a very brief mention of how to actually access this code programmatically, he mostly writes about how ASP.NET works under the hood. Towards the end of the article he notes something that I found very interesting. He writes:
"Each ASP.NET application is allowed a maximum number of page recompiles (with 15 as the default) before the whole application is restarted. ...If the lates compilation exceeds the threshold, the AppDomain is unloaded and the application is restarted. Bear in mind that the atomic unit of code you can unlad in the CLR is the AppDomain, not the assembly. Put another way, you can't unload a single assembly without unloading the whole AppDomain."

I develop with the "attach when you need to" versus the "hit play/F5 and lauch I.E. every time" technique. I find this to be much more productive and saves the hastle of having to truly restart my application every time. Granted, this introduces some problems because I'm not starting clean every single time but I find that the occassional inconvenience is far outweighed by the time savings of avoiding a the full recompile-load IE-attach sequence.

When I make file changes that do not require recompiling I go thru many change-save-refresh cycles. I have noticed that most of the time after I refresh there is only a slight delay (sometimes hardly noticable) on the first refresh after a change. I knew that ASP.NET is refreshing its cache of my page but beyond that I was not aware of what was actually going on. Occasionally, the application will seem to hang up, but then return and behave as if I had restarted completely (I'll end up at the login page if I'm in a authenticated application). Based on Esposito's explanation I now understand that I've reached that recompile threshold and my entire application has been restarted. This explains the behavior I've experienced and wondered about.