Hi there,

Can someone briefly take a look here:

http://msdn2.microsoft.com/en-us/library/4eeya3de(VS.80).aspx

And search for "Possible Error Using VSLangProj Assemblies with EnvDTE Assembly".

I don't currently get this error on my development machine but I don't fully understand all the details either. Can someone briefly confirm whether I should really add the fix mentioned here to my existing "App.Config" file (which isn't a new version of this file as recommended in the article but the existing file generated by VS when my project was first created). If so, does anyone know whether this fix might actually create any problems with the next version of EnvDTE. This would be the version that follows 8.0.x.x as described in the artilce which I'm guessing is already available in VS 2008. In any case, I want to make sure this "fix" isn't going to break anything later. Thanks very much.

Do you perhaps have vs 2003 installed on your system? I think it might find
it from there rather than the correct location, if I understand the message.

"JohnS" wrote:

> Hi there,
>
> Can someone briefly take a look here:
>
> http://msdn2.microsoft.com/en-us/library/4eeya3de(VS.80).aspx
>
> And search for "Possible Error Using VSLangProj Assemblies with EnvDTE Assembly".
>
> I don't currently get this error on my development machine but I don't fully understand all the details either. Can someone briefly confirm whether I should really add the fix mentioned here to my existing "App.Config" file (which isn't a new version of this file as recommended in the article but the existing file generated by VS when my project was first created). If so, does anyone know whether this fix might actually create any problems with the next version of EnvDTE. This would be the version that follows 8.0.x.x as described in the artilce which I'm guessing is already available in VS 2008. In any case, I want to make sure this "fix" isn't going to break anything later. Thanks very much

> Do you perhaps have vs 2003 installed on your system? I think it might
> find
> it from there rather than the correct location, if I understand the
> message.

Thanks for the feedback. VS 2005 is installed on my own machine and the
program targets that version or higher. To be honest I'm not too familiar
with these config files but it's been on my TODO list for about a year now.
I'll be reading up on it sooner or later. Presumably these files need to be
shipped with my app but it's this version issue I'm concerned with. I don't
want the problem to surface on a client's machine. Any insight you can
provide is appreciated. Thanks.

> Thanks for the feedback. VS 2005 is installed on my own machine and the
> program targets that version or higher. To be honest I'm not too familiar
> with these config files but it's been on my TODO list for about a year
> now. I'll be reading up on it sooner or later. Presumably these files need
> to be shipped with my app but it's this version issue I'm concerned with.
> I don't want the problem to surface on a client's machine. Any insight you
> can provide is appreciated. Thanks.

Just to clarify (if it's not already obvious) that my app is a VS AddIn so
it will be running under VS on client machines (2005 or higher)

I think that you may have misunderstood my question. I believe you will have
a problem if your environment has vs 2003 and vs 2005, even if you build with
2005. Have a look at this thread and you may understand.
http://forums.microsoft.com/MSDN/Sho...89003&SiteID=1


"JohnS" wrote:

> > Do you perhaps have vs 2003 installed on your system? I think it might
> > find
> > it from there rather than the correct location, if I understand the
> > message.
>
> Thanks for the feedback. VS 2005 is installed on my own machine and the
> program targets that version or higher. To be honest I'm not too familiar
> with these config files but it's been on my TODO list for about a year now.
> I'll be reading up on it sooner or later. Presumably these files need to be
> shipped with my app but it's this version issue I'm concerned with. I don't
> want the problem to surface on a client's machine. Any insight you can
> provide is appreciated. Thanks.
>
>
>