<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://weblogs.asp.net/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Wrong constructor called in COM+: sneaky, sneaky bug</title><link>http://weblogs.asp.net/avnerk/archive/2007/08/30/wrong-constructor-called-in-com-sneaky-sneaky-bug.aspx</link><description>Here's another nasty one that tried to bite me today. Let's say I have the following classes: public class COMPlusClass : ServicedComponent { public COMPlusClass() { // Default initialization. } public COMPlusClass (string data) { // Parameterized initialization</description><dc:language>en</dc:language><generator>CommunityServer 2007 SP1 (Build: 20510.895)</generator><item><title>re: Wrong constructor called in COM+: sneaky, sneaky bug</title><link>http://weblogs.asp.net/avnerk/archive/2007/08/30/wrong-constructor-called-in-com-sneaky-sneaky-bug.aspx#3669860</link><pubDate>Thu, 30 Aug 2007 18:28:55 GMT</pubDate><guid isPermaLink="false">c06e2b9d-981a-45b4-a55f-ab0d8bbfdc1c:3669860</guid><dc:creator>Eric Wild</dc:creator><author>Eric Wild</author><description>&lt;p&gt;That one caught me a couple of years ago. When you think about it, it does makes sense. Unfortunately, it lets you get away with it until you go to deploy, then it is too late! &lt;/p&gt;
&lt;img src="http://weblogs.asp.net/aggbug.aspx?PostID=3669860" width="1" height="1"&gt;</description></item></channel></rss>