Hallo Gert, * Am 14.11.2003 (17:41) schriebst Du: > I think I'm missing the problem here : why is '[assembly: > ComVisibleAttribute(false)]' wrong ?
The compiler doesn't reject ComVisibleAttribute set to false, but when looking at the compiled result, ComVisible is set to true (default), hence the class is visible for COM. The syntax (as described in the SDK documentation) is definitly [assembly: ComVisible(false)] for assembly wide setting and [ComVisible(false)] on a per function base. > The <asminfo> task is indeed incapable of locating the attribute type if you > don't specifiy its actual type name (meaning with the Attribute suffix), as > ComVisible itself is not the actual type name. > > Please help me understand your problem ... Here is a slight problem: There are attributes where the type name is different to the syntactic use in C#. Then you can't use asminfo to generate AssemblyInfo.cs. I need a set of these attributes (ComVisible is only one), for making my application compliant with Microsoft .NET Framework Design Guidelines. You might want to have a look at FxCop. This tool (by Microsoft) checks for the compliance. -sa -- sa at programmers-world dot com http://www.livingit.de Bookmarks online: http://www.mobile-bookmarks.info Soon available in english The Law, in its majestic equality, forbids the rich, as well as the poor, to sleep under the bridges, to beg in the streets, and to steal bread. -- Anatole France ------------------------------------------------------- This SF. Net email is sponsored by: GoToMyPC GoToMyPC is the fast, easy and secure way to access your computer from any Web browser or wireless device. Click here to Try it Free! https://www.gotomypc.com/tr/OSDN/AW/Q4_2003/t/g22lp?Target=mm/g22lp.tmpl _______________________________________________ Nant-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-users
