Per the workaround that Microsoft posted on the Connect issue I filed for this, it’s a known issue and there won’t be any solution for it, at least in the current release:
The reason for failing to add a new
service item: When adding a new item
and updating the configuration file,
the system will try to load
configuration file, so it will try to
search and load the assembly of the
cusom extension in this config file.
Only in the cases that the assembly is
GACed or is located in the same path
as vs exe (Program Files\Microsoft
Visual Studio 9.0\Common7\IDE), the
system can find it. Otherwise, the
error dialog will pop up and “add a
new item” will fail.I understand your pain points.
Unfortunately we cannot take this
change in current release. We will
investigate it in later releases and
try to provide a better solution
then,such as providing a browse dialog
to enable customers to specify the
path, or better error message to
indicate some work around solution,
etc…Can you try the work around in current
stage: GAC your custom extension
assembly or copy it to “Program
Files\Microsoft Visual Studio
9.0\Common7\IDE”?We will provide the readme to help
other customers who may run into the
same issue.
Unfortunately, it appears I’m out of luck on this one.