bugs
Topics discussing bugs in existing software.
In a previous post I reported an InvalidProgramException that occurs in a certain circumstance with unit tests involving accessors on a private generic method. It turns out that Bug #635093 reported through Microsoft Connect will not be fixed. The reason cited is that private accessors have been discontinued. And why have private accessors been discontinued? They don't have time is the reason listed in the blog post titled "Generation of Private Accessors (Publicize) and Code Generation for Visual...
There is a bug in the unit testing framework in Visual Studio 2010 with unit testing. The bug appears in a very special circumstance involving an internal generic type. The bug causes the following exception to be thrown: System.InvalidProgramExcept... JIT Compiler encountered an internal limitation. This occurs under the following circumstances: Type being tested is internal or private Method being tested is generic Method being tested has an out parameter Type accessor functionality used to access...
In my unit tests I'm consistently getting a MessageQueueException when testing an object that queues and receives back messages from a message queue (in this case it is private, but public is supported). The exception occurs with the first message that is processed through an empty queue and then I don't see it again. The odd thing about this exception is that the MessageQueueErrorCode does not match up with one of the enumeration values and the Message is a null value. The MessageQueueErrorCode...
I found another oddity that seems to be undocumented today. This one in SQL Server 2005. Apparently, you cannot start objects (at least stored procedures) with the word "Log". I have a table called ShipNoticeLog and a stored procedure called LogShipNotice. The table is the noun and the stored procedure is the action -- this is how I prefer to do the naming. My code quickly failed with the message, "Invalid object name 'LogShipNotice'..." I ended up solving my issue by renaming the stored procedure...
Whenever I run into a weird bug or workaround I like to do a short post about it. Doing so helps the community and it is also self-serving in case I run into it a year or so later after I've long forgot about it. Today is one of those times. My latest disk batch came for my MSDN subscription and I decided to upgrade Expression Blend and Web to version 2. Granted I haven't really used these tools too much, but I plan on doing so in the future. The installation of Blend went without a hitch, but Web...
Today has been one of those days to hate Microsoft Access. My company has dozens of Microsoft Access applications in the enterprise that do everything under the sun. Eventually those will be replaced by me, but in the meantime I have to deal with them. Today was one of those days. In fact today I had two circumstances to reinforce those feelings. The first came when I had to correct an ordering of results on a form that wasn't matching a report. The report was deemed correct, so I needed to view...
"Exception 80004005" has to be the worse error description I've seen. This is not the error number, it's the description. I received this error today when I was working on some legacy Visual Basic script in VisiWatch (an EAI application developed by SoftBrands). There is some sporadic information out there on this error. However, all of the guidance revolved around IIS code and suggested corruption, permissions, etc. Of course this guidance led me on a wild goose chase. After awhile I was able to...
I got the following error when I tried to install Office 2007 Professional this morning: The 2007 Microsoft Office system does not support upgrading from a prerelease version of the 2007 Microsoft Office system. You must first uninstall any prerelease versions of the 2007 Microsoft Office system products and associated technologies. Correct the issue(s) listed above and re-run setup. I had uninstalled all of the software except for Office 2003 Web Components which as it turns out needs to be uninstalled....
I've been racking my brain with an error for quite awhile now regarding adding a parameter to a collection for an ADO Command object. The scenario is that I have a SQL query called from Access against a SQL Server database that has one character parameter.
I'm at our Mexico user group this week and I had a heck of a day yesterday relating to System Restore. I've used System Restore in the past, but never had problems like this.
Full bugs Archive