How to handle warnings when Visual Studio references com

According to a comment in the mdsn article about tlbimp for 2.0, you can't fix this problem w/o running tlbimp yourself.

It was easy to reproduce your problem using vs. I also reproduced it running tlbimp manually from a vs comment prompt:

Tlbimp c: \ winnt \ system32 \ activeds. TLB/out: InterOP. activeds. dllthe fix was to use the/silent Switch

Tlbimp c: \ winnt \ system32 \ activeds. TLB/silent/out: InterOP. activeds. dllas pointed out in the comment in the msdn article, the com reference becomes. net Assembly reference to the InterOP assembly you built yourself.

I'm not a vs expert, but I made this work by adding a prebuild to project:

"$ (Devenvdir )\.. \.. \ SDK \ V2.0 \ bin \ tlbimp "C: \ winnt \ system32 \ activeds. TLB/namespace: activeds/silent/out: "$ (projectdir) InterOP. activeds. DLL "built it once so I 'd have a DLL to add a reference with the Browse tab. added a reference to the InterOP. activeds. DLL in my project root and then built again. you may want to do this some other way, like with an external make file via a C ++ project. this is more of a POC.

Note a funny difference in msbuild vs, $ (devenvdir) has a trailing backslash but msbuild does not.

 

Refer:

Http://msdn.microsoft.com/en-us/library/tt0cf3sx%28VS.80%29.aspx

Http://stackoverflow.com/questions/269063/lots-of-build-warnings-when-com-objects-activeds-or-msxml2-are-referenced