<< Everything you need to start writing Windows Services | Select a number of rows based on a parameter using T-SQL >>

Setting ComVisible

Wednesday, 19 January 2005

Posted by Sébastien Lachance with Comments (0)

Today, I have tried FxCop from GotDotNet, and the first warning was about the assembly not marked with the ComVisible attribute. What this attribute does in fact is to limit access to components from Vb6. Here is how you can do that:

Step 1: Open AssemblyInfo (cs or vb extension) file.
Step 2: Add this [assembly: ComVisible(false)] or remove it if needed.)

So it's all. I hope this is a worthy advice.

Setting up a basic continuous integration server with TeamCity : How-to : Setting up a basic continuous integration server with TeamCity
Setting up a the build file for a new application : How I have setted up a new build file for an application.
Setting up a continuous integration server with CruiseControl.NET : How to set up a basic continuous integration server with CruiseControl.NET

blog comments powered by Disqus

About the author

Hi, my name is Sébastien Lachance and I am an independent agile software developer based in Beauceville, Quebec, Canada. I'm doing mostly web development but I enjoy writing any kind of software. I can give formation and I have experience working remotely. I am building my own product right now but I am ready to help you get yours done. If you would like to hire or contact me, use the contact form.

Resume

My resume on StackOverflow.com

Setting ComVisible

About the author

Resume

Connect

Categories