READ FIRST PLEASE - new shim wizard

[David Thielen]

Hi;

Please ignore my earlier emails on the shim. I got it working (not
easy) and have a couple of questions now that I have it working:

1) http://msdn.microsoft.com/en-us/library/bb508939.aspx is out of
date, the code it tells you to comment out is no longer generated.

2) I uncheck the box for "same GUID/ProgId" and in MyAddInShim.rgs I
change every occurance of "MyAddIn.Connect" to "MyAddInShim.Connect".
Do I need to change anything else to keep MyAddIn.dll distinct from
MyAddInShim.dll? I do this so when debugging MyAddIn I do not need to
load the shim.

3) ManagedAggregator appears to be built identically every time the
shim wizard runs. Is this correct? I ask because we have 4 shims for
our 4 builds of our AddIn (2000, 2002, 2003, & 2007) and want to make
sure it's ok to use the same ManagedAggregator.dll for all 3.

??? - thanks - dave

david@[email protected]
Windward Reports -- http://www.WindwardReports.com
me -- http://dave.thielen.com

Cubicle Wars - http://www.windwardreports.com/film.htm

 

[Jialiang Ge [MSFT]]

Hello Dave

Although COM Shim Wizard
(http://msdn.microsoft.com/en-us/library/bb508939.aspx) is not a supported
tool ("This tool is produced by members of the Visual Studio Tools for
Office (VSTO) team, because we recognize that there are some customers who
cannot use VSTO. However, unlike VSTO, this is not a supported tool."), I'm
glad to share my findings with you on this thread.

====================================================
2) I uncheck the box for "same GUID/ProgId" and in MyAddInShim.rgs I
change every occurance of "MyAddIn.Connect" to "MyAddInShim.Connect".
Do I need to change anything else to keep MyAddIn.dll distinct from
MyAddInShim.dll? I do this so when debugging MyAddIn I do not need to
load the shim. 2) I uncheck the box for "same GUID/ProgId" and in
MyAddInShim.rgs I
change every occurance of "MyAddIn.Connect" to "MyAddInShim.Connect".
Do I need to change anything else to keep MyAddIn.dll distinct from
MyAddInShim.dll? I do this so when debugging MyAddIn I do not need to
load the shim.

Based on my reading of shim, there's no other places that you need to
change to keep MyAddIn.dll distinct from MyAddInShim.dll.

3) ManagedAggregator appears to be built identically every time the
shim wizard runs. Is this correct? I ask because we have 4 shims for
our 4 builds of our AddIn (2000, 2002, 2003, & 2007) and want to make
sure it's ok to use the same ManagedAggregator.dll for all 3.

I think so. I get this feeling by looking at the wizard package of
AddinShim:
C:\program files\Microsoft Visual Studio
9.0\VC\VCWizards\COMShims\AddinShim

Regards,
Jialiang Ge ([email protected], remove 'online.')
Microsoft Online Community Support

=================================================
Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
(e-mail address removed).

This posting is provided "AS IS" with no warranties, and confers no rights.
=================================================

 

[David Thielen]

thank you very much!

Hello Dave

Although COM Shim Wizard
(http://msdn.microsoft.com/en-us/library/bb508939.aspx) is not a supported
tool ("This tool is produced by members of the Visual Studio Tools for
Office (VSTO) team, because we recognize that there are some customers who
cannot use VSTO. However, unlike VSTO, this is not a supported tool."), I'm
glad to share my findings with you on this thread.

====================================================
2) I uncheck the box for "same GUID/ProgId" and in MyAddInShim.rgs I
change every occurance of "MyAddIn.Connect" to "MyAddInShim.Connect".
Do I need to change anything else to keep MyAddIn.dll distinct from
MyAddInShim.dll? I do this so when debugging MyAddIn I do not need to
load the shim. 2) I uncheck the box for "same GUID/ProgId" and in
MyAddInShim.rgs I
change every occurance of "MyAddIn.Connect" to "MyAddInShim.Connect".
Do I need to change anything else to keep MyAddIn.dll distinct from
MyAddInShim.dll? I do this so when debugging MyAddIn I do not need to
load the shim.

Based on my reading of shim, there's no other places that you need to
change to keep MyAddIn.dll distinct from MyAddInShim.dll.

3) ManagedAggregator appears to be built identically every time the
shim wizard runs. Is this correct? I ask because we have 4 shims for
our 4 builds of our AddIn (2000, 2002, 2003, & 2007) and want to make
sure it's ok to use the same ManagedAggregator.dll for all 3.

I think so. I get this feeling by looking at the wizard package of
AddinShim:
C:\program files\Microsoft Visual Studio
9.0\VC\VCWizards\COMShims\AddinShim

Regards,
Jialiang Ge ([email protected], remove 'online.')
Microsoft Online Community Support

=================================================
Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
(e-mail address removed).

This posting is provided "AS IS" with no warranties, and confers no rights.
=================================================

david@[email protected]
Windward Reports -- http://www.WindwardReports.com
me -- http://dave.thielen.com

Cubicle Wars - http://www.windwardreports.com/film.htm