Prev: User Defined config section "You must implement a default accessor on System.Configuration.ConfigurationLockCollection because it inherits from ICollection."
Next: Is this a .net 4.0 bug
From: Rod on 26 Apr 2010 04:38 In VS2005 I have multi-project solution with mostly C# but one VB project to provide a COM wrapper. Two of the projects use an external set of DLLs to create a report, using report definition data taken from an SQL Server. One of the projects creates the report just fine, but the other project errors out when trying to do the same thing. I have checked that the projects are referencing the same versions of the all the DLLs and they appear to be identical. What could the cause of this problem?
From: Peter Duniho on 26 Apr 2010 19:26
Rod wrote: > In VS2005 I have multi-project solution with mostly C# but one VB project to > provide a COM wrapper. > > Two of the projects use an external set of DLLs to create a report, using > report definition data taken from an SQL Server. One of the projects > creates the report just fine, but the other project errors out when trying > to do the same thing. > > I have checked that the projects are referencing the same versions of the > all the DLLs and they appear to be identical. > > What could the cause of this problem? Any number of things. Your description is far too vague for anyone to be able to reliably suggest a specific cause or solution. _Maybe_ if you were specific about the exact error, the exact DLLs you're using, exactly _how_ you're trying to use them, etc. there's a _possibility_ that someone could help. But as things stand now the only choices are: � Your projects are not in fact winding up using the same DLLs, or � Your projects are using the same DLLs but not in the same way Only you would be able to investigate the specifics to determine which of those possibilities is the case, and what implications that has in terms of fixing the problem. Pete |