A
alejandro.campos
Hello,
I'm developing a VS 2005 shared COM add-in for Excel. I've run into this
issue when deploying it into some machines. If that machine has the .NET
framework 2.0 everything is all right . If the machine has versions 3.0 or
3.5, I have to install version 2.0 and explicitly tell Excel to use it
instead of the other ones (copying this Excel.exe.config file to the
Microsoft Office directory); otherwise it won't load. Even if I have .NET 2.0
and 3.5 installed and I tell Excel to use .NET 3.5, the add-in won't load at
all.
Do you know why's that? Is it a requirement that the end user has .NET 2.0
when you develop the add-in with VS 2005 (that uses .NET 2.0). Are .NET
3.0/3.5 not backward compatible?
Thanks
I'm developing a VS 2005 shared COM add-in for Excel. I've run into this
issue when deploying it into some machines. If that machine has the .NET
framework 2.0 everything is all right . If the machine has versions 3.0 or
3.5, I have to install version 2.0 and explicitly tell Excel to use it
instead of the other ones (copying this Excel.exe.config file to the
Microsoft Office directory); otherwise it won't load. Even if I have .NET 2.0
and 3.5 installed and I tell Excel to use .NET 3.5, the add-in won't load at
all.
Do you know why's that? Is it a requirement that the end user has .NET 2.0
when you develop the add-in with VS 2005 (that uses .NET 2.0). Are .NET
3.0/3.5 not backward compatible?
Thanks