March 2004 Entries

Trying for a Visual Studio 2005 CTP "community change log"

So, as I suggested in a previous post, I'd like to use the VS2005 CTPs.  All of 'em.  However, I don't want to tear my hair out trying to figure out what version we should use because the stuff I'm working with is broken in the latest version.  I also don't want to have to try working with someting for a day only to figure out that it is newly broken, especially if someone else has already suffered through it. So, Without further ado, I give you the Visual Studio 2005 Community Tech Preview community running change log (VS2K5CTPCRCL). What Dave Bettin and I (and hopefully...

posted @ Tuesday, March 30, 2004 12:48 PM | Feedback (8)

Say goodbye to unsightly SourceSafe residue

Visual Source Safe.   I cringe whenever a client site is using it.  Let's face it, when VSS 6.0 came out it was an acceptable product for its time (what was that.. 6 years ago? 7?).  It was pretty good for VB6 developers working alone or in small teams.   But VS.NET isn't  VB6.  The methodologies of development are different... unfortunately VSS treats them as the same. One of the things I hate most about VSS is actually issues with VS.NET's SCC integration -- the crud that VS.NET puts inside project and solution files when using source control.  (Unfortunately, VSS's standalone client does the same thing for...

posted @ Saturday, March 27, 2004 3:38 PM | Feedback (0)

Go Get It.

You know you want it.  Go Get it. [Visual Studio 2005 CTP, that is]

posted @ Thursday, March 25, 2004 6:27 PM | Feedback (1)

.Net bugs - what do you do with 'em?

Okay, so I have found this bug (no, not this one) with ASP.NET 1.0 and 1.1.  What do I do with it?  It can be worked around, so there's no point in burning a call to PSS and looking for a hotfix... but then I don't see anything about it in the MS Knowledge Base.  I haven't seen anyone discussing it in the blogs, or on newsgroups -- even on the web.  So what do I do with it? It seems to be fixed in the PDC drop of Whidbey, but do they want to know about it? Do they already know about it? ...

posted @ Tuesday, March 23, 2004 1:42 AM | Feedback (0)

ASP.Net Bug: CheckChanged event firing incorrectly when checkbox held on a disabled datagrid row

Symptoms When a checkbox is housed in a datagrid's templatecolumn, that checkbox has the AutoPostBack property set to true, and the datagrid's row is disabled, the checkbox will fire its CheckChanged event on any subsequent postback even though the row's state did not change. More Information Steps to reproduce behavior Reproduction solution here.  Extract all files to a directory and set up that directory as a virtual directory in IIS named "DisableBugRepro". If you have a datagrid with the following column definition: <asp:TemplateColumn> <ItemTemplate> <asp:CheckBox AutoPostBack="True" OnCheckedChanged="CheckChanged" Runat="server" ID="chk" /> </ItemTemplate></asp:TemplateColumn> And you are: Setting the checkbox's checked propery in the DataGrid's ItemDataBound event Disabling a row Then on the next postback immediately...

posted @ Tuesday, March 23, 2004 1:41 AM | Feedback (1)

Solve the real problem, not the solution's problems (and a quick example with IMessageFilter)

There are many, many tools in the .net framework that are there to help solve specific problems that developers may need to overcome.  The big problem is knowing when they are there. For me, a great example of this is a problem that I used IMessageFilter on. I didn't realize how neat this feature in the Windows Forms framework is, until I had an "off the wall" request from a friend. They had this small application that they created, and they were doing frequent training on it. What they wanted to do was highlight each control (textbox, listbox, label, etc)...

posted @ Friday, March 05, 2004 10:05 PM | Feedback (3)