royalhale

I created an add-in for Outlook 2003 using VS 2005. I built this add-in using VSTO SE as well as with the Shared-add-in template. This add-in places a button on the reply to and new email forms that can be used to send the email data to a webservice function that records it in the database and then calls the send function of Outlook.

Most of the time this works great no matter which build I use but we have 3 or 4 users who get the following error from McAfee VirusScan Enterprise 8.0.0 when attempting to send with the button no matter if it is the VSTO build or the other:

C:\Program Files\Microsoft Office\OFFICE11\OUTLOOK.EXE:Tongue Tiedend bo:heap

I had read some posts that stated there was a problem with McAfee and .Net add-ins that was supposed to be fixed with patch 6. We are up to patch 13 so I am assuming this is not the solution.

Has anyone else had a problem with this Disabling the buffer overflow protection, which is the source of the problem, is not an option. We attempted to exclude the dll from the list but this didn't help. We are now attempting to exclude the redemption dll which is used also.

Thanks

Royal



Re: Visual Studio Tools for Office outlook add-in causing bo:heap warning

Christin-MSFT

Hello Royal -

I reviewed your post with two of the architects on the VSTO team and we really have no idea what is going on to cause the MacAfee error.

Can you confirm that you use the VSTO Outlook Addin and not the Shared Addin They are actually two different project types that do very different things at runtime. The VSTO Outlook Addin requires the VSTO Runtime (VSTOR.exe) on the client computer and the Shared Addin does not.






Re: Visual Studio Tools for Office outlook add-in causing bo:heap warning

royalhale

I actually have 2 versions of the add-in. It doesn't matter which one I use. The users still get the warning. We started using the VSTO version and started getting the error so we uninstalled it and installed the shared version. We then attempted to exclude the dll's in Mcafee, 1 being the add-in dll and the other the redemption.dll, which the add-in uses. This seemed to work for awhile and then the warning returns.

Thanks

Royal





Re: Visual Studio Tools for Office outlook add-in causing bo:heap warning

Kulvinder

Any solution to this will be much appreciated.

Regards

Kulvinder Singh






Re: Visual Studio Tools for Office outlook add-in causing bo:heap warning

Christin-MSFT

I suggest that you try running your solution on a computer with Macafee and a debug version of your code. Then when the error happens, look to see what your code was doing. If the problem happens with both the Shared Addin and the VSTO Addin, then that tells me the problem is not caused by something in Visual Studio, because our code is completely different. The problem is either in Office or in your code somewhere, or perhaps in the system configuration. I do not have any more information to help you.




Re: Visual Studio Tools for Office outlook add-in causing bo:heap warning

Jahid

Hi all,

I have developed an add-in for outlook using shared add-in. Even I found that performance of my system is slow when outlook is running (when addin is working )and Mcafee is installed.

Is this a known problem Any inputs on this topic would be a great help.

Thanks,

Jahid






Re: Visual Studio Tools for Office outlook add-in causing bo:heap warning

Christin-MSFT

Jahid -

It is not a known problem at Microsoft, but you might want to ask Macafee. Every computer at Microsoft runs an antivirus scan product, and we have not noticed performance problems with Outlook and custom addin DLLs. We are not running Macafee, we are running eTrust Antivirus software.

Keep in mind that the Shared Addin uses a different technology than VSTO solutions. Though both solutions rely on COM interop and the Primary Interop Assemblies of Office.






Re: Visual Studio Tools for Office outlook add-in causing bo:heap warning

Andriy aka Dante

All,

We've faced the same issue with Outlook VSTO add-in causing McAfee VirusScan Enterprise 8.0.0 to display bo:heap warning.

We created an add-in for Outlook 2003/2007 using VSTO 2005 SE under VS 2005. This add-in synchronizes Outlook appointments with web based project management tool. We use web service for retrieving/updating appointments from web server.

As it was pointed above the issue is not related to what technology is used for creating Outlook add-in - VSTO or COM add-in. And our search is likely to confirm this observation.

We've ran our VSTO add-in through VS 2005 profiler and it looks like the reason bo:heap warning appears is because of the call to the web service client stub constructor - SoapHttpClientProtocol..ctor(). In our case just one call to this contructor allocates 10Mb of memory. Probably, this allocation is treated by the anti-virus software as a threat.

I hope it narrowed down the search a little bit, but still the issue is relevant - what allocates so much memory in just one call to the Framework constructor Any more ideas

Regards,
Andriy




Re: Visual Studio Tools for Office outlook add-in causing bo:heap warning

Kulvinder

Hi,

Can you please tell me how to run VSTO add-in using VS 2005 profiler specifically I mean do i need to install some special software to do this How to go ahead

Regards

Kulvinder Singh






Re: Visual Studio Tools for Office outlook add-in causing bo:heap warning

Andriy aka Dante

Hi,

I'm not sure whether Performance tools are shipped with each version of Visual Studio. On my machine I use Team Suite edition.

To run Performance tests using VS Team Suite here is what you need to do:

1. Tools > Performance Tools > Performance Wizard...
2. Choose 'Profile a dynamic link library (.DLL)' on the first step of the wizard.
3. On the second step: specify path to your VSTO add-in in the 'DLL Path' box. Specify path to Outlook.exe in the 'Executable path' box
4. Choose instrumentation profiling.
5. Click Finish and now you are good to launch performance session.

I hope in helps.

Regards,
Andriy




Re: Visual Studio Tools for Office outlook add-in causing bo:heap warning

Dave - MSFT

What happens when you exclude Redemption from your VSTO solution





Re: Visual Studio Tools for Office outlook add-in causing bo:heap warning

royalhale

We were finally able to resolve this issue by installing the newest version of the McAfee Enterprise software. All attempts at adding patches didn't work.

Thanks

Royal





Re: Visual Studio Tools for Office outlook add-in causing bo:heap warning

Bart Elia

We are chasing a similar issue (buffer overrun, McAfee, vsto, etc).

What version of McAfee did you upgrade to 8.5 from 8.0 Any help would be appreciated.





Re: Visual Studio Tools for Office outlook add-in causing bo:heap warning

royalhale

We upgraded to 8.5 on a couple of machines and all seems to be working. The machines with just the patches for 8.0 are still having the problem.