Last post Sep 22, 2010 02:22 PM by softie1997
Sep 22, 2010 10:08 AM|MBasliyal|LINK
I am using VS2008 and Office 2010 on my machine. My code needs a reference for Office interop assemblies for few reasons. Now When the solution was built, it was on Office 2007.
Now as the Ofice version has changed, the code has become unstable.
Is there any why to fix this?
Note: I want to exclude the installation of Office PIAs manually. Any Poineters?
Sep 22, 2010 12:00 PM|softie1997|LINK
I am confused. You updated the office assemblies and you are looking for a quick fix? Like any other assembly, there is no way to work around this other than adding the new reference, fixing the bugs, recompiling, and redistributing. The last part can
be accomplished using the PIAs, unless you have some other advanced functionality like VBA.
Help me understand what:
"any why" to fix this
Sep 22, 2010 01:23 PM|MBasliyal|LINK
The code has become 'unstable' means it ask me to refer new PIAs when I donot want to do this.
I am using office classes to modify the office functionalities. What if, tomorrow Microsoft comes with a new version of office?
Is there any way to fix this problem?
May be a wrapper which helps me to just update one project rather than the all my projects.
Sep 22, 2010 02:22 PM|softie1997|LINK
If the old binaries exist on the target machine there is no reason to "upgrade". The warnings I believe you are describing are there to let you know there is a newer version because at some point even the new ones will become deprecated!
Just mark your own interops as copy local and refer to those.