I'm just curious how labor intensive it is to view PDFs in VB .NET, whether by purchasing a component or writing code.



Thanks

Ben, you are correct.  But it also depends on how much usage the interop will get.  If your entire application is hinged around it, then yeah, bad idea for sure   But just for a minor viewer it shoulnd't cause too many issues...if any.  One thing that .NET does really well is create an interop interface to the COM and Ax... classes.  The only downside that I see with using an ActiveX control is that you either have to distribute it, or in this case make sure Adobe Reader is installed.  But you are correct, certain ActiveX controls do notplay nice with .NET...but the more popular ones, such as this Adobe Acrobat control or the Flash ActiveX shouldn't cause too many issues.  I will agree with Ben, though, that if part of your application relies heavily on opening and viewing PDF documents, then this may cause some memory and interopability issues once the volume is increased.