Page 1 of 1

Does framework3.5 can affect the office 2007 framework ?

Posted: Tue Jan 03, 2012 11:04 pm
by hirenlad
Hello,

I have used Install Aware 2012 and I had create one windows setup with framework 3.5. Now when i install windows application it installed framework3.5 and also it's dependable framework like framework 3.0, framework 2.0. Now so far so good all frameworks installed successfully and also application run successfully.

Everything work fine with my setup, but in some machine have Office 2007 already installed then after installing my setup Office get corrupted.
and i have found below error message.

"There is not enough memory or disk space to complete the operation."

I think office 2007 have also used frameworks, so that my setup can get upgrade the office 2007 framework.
Does framework 3.5 and it's dependable framework can affect the office 2007 framework ?
How can i fixed this issue?

Regards
HireN Lad

Re: Does framework3.5 can affect the office 2007 framework ?

Posted: Wed Jan 04, 2012 9:12 pm
by giaviv
Could you confirm that low disk space is not ACTUALLY the cause of the issue?

Re: Does framework3.5 can affect the office 2007 framework ?

Posted: Thu Jan 05, 2012 12:10 am
by hirenlad
Hi giaviv, Thanks for reply..

There is more space in our C: drive and other drive also. When i install my windows setup then after my office 2007 get corrupted. We had faced this issue 3 to 4 times on different different machines.
We had also describe this issue on Microsoft forum. They were told me to get technical Isupport from nstall Aware 2012. Please refer this link

http://social.msdn.microsoft.com/Forums ... 88aeed8140

Please read my post from above link.

When we create setup in Application Runtime option with Microsoft framework 3.5, default Microsoft XML parser 6.0 get selected. Which i unchecked before building my setup. Is it happen this issue through XML parser 6.0 ?

Regards
HireN Lad

Re: Does framework3.5 can affect the office 2007 framework ?

Posted: Fri Jan 06, 2012 4:01 pm
by giaviv
Since the framework checks-out as installed by IA (we're shelling to the native MS setups anyways), this is very unlikely to be a IA issue. IA apparently did install .NET correctly by MS's own statement.

Please try the same sequence on a clean virtual machine - does this reproduce?