Tom Christian's Blog
-
ASP.NET Tip: Letting Microsoft know about your problems/requests
Not sure if everyone knows of the various options that there are for communicating with Microsoft so I wanted to let you know about some of them here.
-
Event Log message after installing .NET update – part 2
If you try to install a .NET update, MS07-040 for example, you may see an event log like:
-
The PDC this year…
Not sure how many people are planning on attending the PDC (Professional Developers Conference) this year, but it is going to be a fantastic conference.
-
Event Log message after installing .NET update
If you try to install a .NET update, MS08-052 for example, you may see an event log that looks like:
-
ASP.NET Tip: How to avoid creating a GC Hole
There are only a few things that can make a .NET process crash. The most common one is an Unhandled Exception getting raised. Another way that is can happen is by creating a GC Hole.
-
POP QUIZ: What’s wrong with this code – part 3
Imagine you are a developer and your boss comes to you complaining that your piece of code has been deemed to be taking up too much memory and causing problems for the application. You take a look at your code and you see the following, assume that stream is defined above this and is correct:
-
Who uses SOSEX and what for?
Another thing I am curious to know is if anyone is using SOSEX and what advantages it gives you for debugging. I have talked to the author of it and I think it has a lot of useful commands, just wanted to get everyone’s take on it.
-
ASP.NET Tips: Careful Use of Static's
Not sure how many people realize it, but when you start dealing with multiple users access a system (in this case a web server), you have to be very careful what you store in static's (global variables). This is because all the users will have access to this data and so if you create a page, you could allow them to see data that they shouldn't.
-
High Memory part 6 – Fragmentation revisited
-
How does maxconnection work for a System.Net.HttpWebRequest using a proxy?
When using a WebRequest, one important thing to keep in mind is how many connections are allowed to be made to the same server. The maxConnection setting will affect how many connections you can concurrently have to a given server. When you set up a proxy, System.Net sees the proxy as the server and so it will limit the number of concurrent connections to that instead of all the various servers.